Thursday, October 8, 2020

Apply platform updates to an On-Premises D365 F&O Dev environment

 Steps to apply platform updates to on-premises environment:

1. On the virtual machine (VM), download the zip file for the deployable package. Make sure that the zip file is stored in a non-user folder.

2. After you download the zip file, right-click it, and then select Properties. Then, in the Properties dialog box, on the General tab, select Unblock to unlock the files.

3. Extract the files.

4. In the folder where you extracted the deployable package, find and open the file that is named DefaultTopologyData.xml. You must specify the VM name and the installed components in this file. Replace the machine name with the computer name.

5.To specify the installed components, follow these steps:

  1. Open a Command Prompt window as an administrator.
  2. Go to the extracted folder and run the following command to see a list of all the components that are installed on the computer.

                              AXUpdateInstaller.exe list

  1. Update the DefaultTopologyData.xml file with the list of components as below.













6. Generate a runbook from the topology by running the following command

    AXUpdateInstaller.exe generate -runbookid=[runbookID] -topologyfile=[topologyFile] -servicemodelfile=[serviceModelFile] -runbookfile=[runbookFile]    

    Ex:AXUpdateInstaller.exe generate -runbookid="ServerName -runbook" -topologyfile="DefaultTopologyData.xml" -servicemodelfile="DefaultServiceModelData.xml" -runbookfile="ServerName-runbook.xml".




7. Import the runbook by running the following command

    AXUpdateInstaller.exe import -runbookfile="ServerName-runbook.xml"

8. Verify the runbook by using the below command

    AXUpdateInstaller.exe list

9. Run the runbook

    AXUpdateInstaller.exe execute -runbookid="ServerName -runbook"





 10. To execute any failed step, use the below command

AXUpdateInstaller.exe execute -runbookid="ServerName -runbook" -rerunstep=21

 

Microsoft documentation:

https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/migration-upgrade/upgrade-latest-platform-update

 

Trouble shooting:

1.               If any step failed with “timeout” then rerun the step manually.

 

https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/deployment/troubleshoot-on-prem

 


Merge code from Dev to Main branch

Steps to merge code from Dev to Main branch:

1.Create and map workspace for Main branch

a. Create a folder in K: drive 





b. Create new workspace in VS for Main branch








c. Map the newly created workspace to the folder








2. Merge code to Main branch:

a. Select the Dev workspace and Get latest version for Dev branch






b. Select the newly created workspace for Main branch and Get latest version for Main branch






c. List down the change set numbers which needs to be merged for the Jira either from Azure DevOps or  from Visual studio (From Team>Go to work item).

d. Right click on the DEV branch >Branching and Merging>Merge










e. Select option "Selected changesets" and click on Next.












f. Select the change set to merge and click on Next and Finish.

(if there are any conflicts, then system will ask to merge. Select "Merge changes in Merge tool" option. System will show the differences. Select the check box beside the change which you want to keep. Once you select the required changes to merge click on "Accept Merge".)

g. Go to Team Explorer>Pending Changes> Select the Main branch workspace as below.













h. Check in by providing work item and comments.













i. Repeat the steps d to h for remaining change sets. Once you are done with the merge change back the workspace to DEV to continue with development.

That's All..

Thursday, June 25, 2020

Fulll Build error in D365 Finance - "The name 'IConfigurationService' does not denote a class, a table, or an extended data type"

Some times we will get build error "The name 'IConfigurationService' does not denote a class, a table, or an extended data type" from the class ERSolutionGlobalRepositoryCache. This class belongs to model "ElectronicReporting". If we have the reference to this model also we will encounter this error.



To resolve this issue, first build the ElectronicReporting model alone. After successful ElectronicReporting model build, the full build will be successful.