Unified Developer experience for Finance & Operations – Install and configure local machine for Development

 

1.   Prerequisites

Below are the list of prerequisites for Unified developer experience.

    1.     Access to a provisioned developer-focused sandbox environment.   The user account you'll be using for development in the sandbox environment must be assigned the System Administrator role.

    2.     The development machine running Microsoft Windows must have Visual Studio 2019 installed along with the below list of Visual Studio components.

         3.  MS SQL Server Express 2019

         4.   7zip 

2.   Connect to your online environment.

     Follow the below step by step instructions to connect to online environment.

      1.      Install Power Platform extension for Visual Studio (What is Power Platform Tools for Visual Studio)

1.                      To install Power platform extension, go to Extensions menu>Manage extensions and choose               the Power Platform Tools and download. Close the Visual studio and install the Extension.

2. In the Tools menu, select Connect to Dataverse or Download FinOps assets. The former only downloads assets if not already downloaded once while the latter will download even if you had downloaded earlier.
3. Select the Show advanced option Login. Choose not to use the signed-in user if you need to use another account with a Visual Studio license. Enter the credentials as necessary to match your development user account.

      4. When presented with a dialog to select a solution, select “Default”, and then choose Done.

      5. You will be presented with a list of Dataverse organizations (databases deployed). Find the sandbox environment created for online development and connect to it.

3.   Download and install the finance and operations extension and metadata.

1.    After installing the Power Platform Tools extension and connecting to the online Dataverse sandbox environment, you'll be presented with a dialog to download the finance and operations Visual Studio extension and metadata.

        (Refer the below common issues section if the Popup didn’t appear)

2.    Configure settings using the Visual Studio setting Tools > Options > Power Platform Tools.

    

    3.     Install VSIX file from the below path.

4.   Extract system metadata.

         1.     Downloaded assets can be found in the following location:

    C:\Users\<User>\AppData\Local\Microsoft\Dynamics365\<ApplicationVersion>

Three files are downloaded and described below.

a)     System metadata is downloaded as PackagesLocalDirectory.zip.

b)     Backup of the cross-reference database as DYNAMICSXREFDB.bak

 

Unblock any of the three files that needs unblocking.

  2.  Create a new folder “AOSService” in C:\ and unpack the PackagesLocalDirectory.zip file as   PackagesLocalDirectory by using the 7zip utility.

3.          3.     Create a new sub folder “Custom” under C:\AOSService

5.   Configure the finance and operations extension.

1.               1. Start Visual Studio, and then select Continue without code from the dialog.

2. Navigate to Extensions > Dynamics 365 > Configure Metadata for the first time.
   If you do not see the Configure Metadata option, open Extensions > Dynamics 365 > Infolog and retry.

3. On the configuration form, select New and then create a new configuration as below.

  Select the Current check box to make the configuration active.

1.           Connect to the VSTS and map the C:\AOSService\Custom folder to Dev Branch as below.

4. Select Save. Once the updates are saved the below message will be displayed.

5. Once the configuration completes, navigate to View > Application Explorer. You should see the Application Explorer window open. You may have to restart Visual Studio first.

6.   Install ISV licenses.

    1.     Create new folder “__License” in the model where the licenses to be installed and then deploy the          models to online environment.  

        Place the license files under the __License folder

        For this operation, use the Extension > Dynamics 365 > Deploy > Deploy Models to Online                Environment menu item. The dialog that appears allows you to select the packages to deploy. In            this case, you need to select "MyTestModel."

        2.   Once the deployment is done perform the full build from Extension > Dynamics         365 >Synchronize database

        Once the sync is successful then the ISV licenses will be enabled in cloud environment

7. Common issues 

    The below are the list of common issues in preview version.

1.      Label ids are being displayed instead of labels.

The label Id’s are being displayed instead of labels like  @XXX1234.

To fix this problem, build the models along with the “Deploy to cloud online environment” option as below.

2.  The download assets option not popping up after connecting to the online Dataverse sandbox environment.

To fix this problem, disable the below check box from Toos>Options and Connect to Dataverse sandbox again

 

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

3. 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..

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.