Scenario: We were using dev environment of Dynamics Finance and Operations with Application release version 10.0 platform update 24. Microsoft released a new version 10.0.5 with platform update 26.
Now we have two options to use the new version.
- Download new VM and moved the custom models to the newly created VM
- upgrade the current VM on the latest update
In first option we need to create and setup the testing data again to test the code.
2nd option everything will remain same and no extra effort needed other than the applying update.
Definitely we selected the 2nd option and below steps were performed to update the environment.
- Download the latest release package from the asset library to the local VM development environment
- Unzip the zip file to the local VM in C drive by creating a custom folder (folder should not be in the users folder directory). I created with below name FnO10.0.234.10001App
- Stop the following services (Batch, Data import and IIS)
- Close Visual studio instances
- open command prompt as administrator
- set the directory to your custom folder contains the unzip files
- Run the below command to check the list of components installed
- C:\FnO10.0.234.10001App>AxUpdateInstaller.exe list
- From the above command you will get all the components already installed
- update the DefaultTopologyData.xml file located in the update folder in my case located in below location
- FnO10.0.234.10001App -> DefaultTopologyData.xml
- Best way to update this file copy on another location edit like below and replace in the above folder
- Generate the run book thru command prompt using below command
- Actual command: AXUpdateInstaller.exe generate -runbookid=[runbookID] -topologyfile=[topologyFile] -servicemodelfile=[serviceModelFile] -runbookfile=[runbookFile]
- [runbookID]– A parameter that is specified by the developer who applies the deployable package.
- [topologyFile]– The path of the DefaultTopologyData.xml file.
- [serviceModelFile]– The path of the DefaultServiceModelData.xml file.
- [runbookFile]– The name of the runbook file to generate (for example, AOSRunbook.xml).
- Should be modify as below
- AXUpdateInstaller.exe generate -runbookid=”Dev-runbook” -topologyfile=”DefaultTopologyData.xml“ -servicemodelfile=”DefaultServiceModelData.xml” -runbookfile=”Dev-runbook.xml”
- Import the run thru command prompt using below command
- AXUpdateInstaller.exe import -runbookfile=”Dev-runbook.xml”
- Execute the runbook thru command prompt using below command
- AXUpdateInstaller.exe execute -runbookid=”Dev-runbook”
This step is the longest step involving many sub-steps performed during this step.
Some steps even takes 2,3 or may more hours. please make sure system will not logout neither shutdown.
if any step fails during this step use below command to rerun
For me its fails on 19 step
Wait till last step completed
- Verify the installation by running below command
- AXUpdateInstaller.exe list
You can check the version also by login to the dynamics browser about option.
Please leave comment in the comments section if you are facing any issue while updating. I will try to assist.
Scenario: Sometime we need to uninstall a deployable package from the UAT or Production environment.
Below are the steps that need to be performed to uninstall a package.
- Create a deployable package using visual studio or Build server
- Do not extract the deployable package that is in ZIP folder (If you extract the zip folder you will face issue invalid HotfixInstallationInfo.xml file)
- Just open the deployable package zip folder
- Go to Deployable package zip folder -> AOS service -> Scripts folder
- create a text file name ‘ModuleToRemove’
- Write the module name to be removed in the the ModuleToRemove file
- If you have multiple models to remove then write mode name per line as below
- Note: In multiple models removing write the models name in sequence as per dependency sequence
- Go back to main zip folder and find the file HotfixInstallationInfo.xml ,copy the file to some other location and edit the file like below
- Edit the file should be same as above.
- Copy and replace the HotfixInstallationInfo.xml file in the deployable folder
- upload the file in the asset library and apply the package to the UAT environment first if applied successfully then apply to the production environment.
Please leave comments if you are facing any issue.
Below are the steps to connect Power BI with Microsoft Dynamics 365 for Finance and Operations
- Download and install the Power BI Desktop
- Sign in with the Licensed account
- In Power BI desktop ribbon click on Get Data
- Select OData Feed
- Enter the URL of the environment
- URL should be look like this https://operations.dynamics.com/data
- Enter the credentials of the user account in AX/D365. Organizational account account should be better rest base upon the requirement.
- Once everything done , next step is downloading the tables based on the security rights and privileges of the user.
- Now you can select the table from the list and start working on it for your workspace.
Follow the steps to connect and do let us know if you are facing any issue.
Scenario: Sometime a requirement to change the report name in the email thru print management need to change dynamically.
Class name where changes need to be done.
Report name update in the email
check the report name in this method and update the file name as per requirement.
Report name update in the PDF and screen viewer
- check the report name
- check the conditions for file and screen viewer
- update the file name for file condition
- update the file name and caption for the report
For Dynamics 365 for finance and operations use the post events of both methods
Below are summary about the new update of Microsoft Dynamics Finance and Operations apps version 10.0.7
- Budget Register Entry Enhancements
- Ability to export records from the accounts payable invoice pool
- Ledger Settlements by User
- Forecast position reports(Public sector)
- Mark a Purchase agreement as closed
- Users can now mark a Purchase agreement as “Closed” to signal the agreement is no longer actively used, making it so users will not be able to create release orders from the purchase agreement.
- Delayed Tax calculation on journal
- Reverse Journal posting
- Stop workflow submission when there are unallocated charges on a vendor invoice
- Account group selection for Chinese voucher types
- Sort resource in the project by invoice proposal
- Run Settle and post sales tax in batch mode
- Tax engine GTE (only available for India
For more details visit Microsoft Documentation using below link
Whats changed in 10.0.7
Entity relationships are metadata. Entity relationships define the different ways of entity records can be associated to different entity records from other entities or the same entity. Entity relationships allows the query to retrieve data efficiently.
Types of Entity relationships:
There are two types of entity relationships
Many related entity records associated with a single entity record (1:N) ,a parent/child relation.
Many entity records are associated with many other entity records. A N to N( N:N) relation.
Entity relationship (1:N) do the following tasks, other than define the relations between the entities:
- If record deleted on the parent entity then the record associated in the child entities also deleted.
- When assign a record to a new owner, associated records also assign to the new owner.
- How the record and related records will be visible to the users.
Entities – Common Data Service – CDS
Data is stored in the Common Data Service database is defined as entity. Entity corresponds to a database table and each field within an entity represents a column in that table.
Common Data service, metadata(data about data), is a collection of entities. Entity metadata controls the kinds of records you can create and type of actions performed on them. When we create or edit the entities,fields relationships, we are editing this metadata.
Common data service comes with a number of standard entities that support the core business applications.We need to become familiar with the catalog of standard entities.
For minor changes we don’t need to create new custom entities:
- To change the field display name or label we don’t need to create custom entity.
- We cannot delete the standard entities but we can hide them by changing the security role assignment.
What is Common Data Service?
Entity Relationship – Common Data Service – CDS
Sometimes we need to delete the model and deployable package from the dev environments.
use Modelutil.exe to delete the model file from the packages local directory.
Package installation or deletion:
- Stop IIS (kill the IIS worker process from the task manager)
- Stop batch job DynamicsAXBatch job
- Delete the package folder located on C:\ or K:\AosService\PackagesLocalDirectory (make sure folder completely deleted)
- Open VS Dynamics -> Model Management -> Refresh models
Sometimes users facing below issue in generating the reports from Dynamics 365 for Finance and operations or Developers while deploying the reports
- Failure! Status check of Report Server –
- The remote server returned an error: (500) Internal Server Error – Report design not found
- Report design not found
Restart the below services by going on the services list window of the report server or from the LCS
- Restart the service report server
- Check and restart the Microsoft SQL Server instance service
Note: If the server is sandbox environment managed by Microsoft then go the Power BI (report server) VM and restart the above services
Common Data Service allow you securely store and manage data that is used in the Business Applications.
Data within common data service is stored within set of records called entities. An entity is a set of records used to store data, similar to how a table store data within the database.
Entities – Common Data Service