Inventory on-hand fields description

Below is the description of fields available on Inventory “On-hand” form. The value of “On-hand”  fields are impacted when user performs any inventory posting in the system, The reason why I wanted to create this sheet is to easily recall the purpose of these fields when any transaction is done. So just to make things easy and simple below sheet can be helpful:

In case if you have any query or concern, please feel free to reach me at my personal email - daxmanish@outlook.com

Enjoy J

Synchronize Entity list in D365 F&O

Synchronize Entity list in D365 F&O between user Interface and Development environment

Problem statement: When a D365 F&O developer develops a new entity or customize any standard entity for integration purpose, but those changes are not reflected on front end (D365 F&O User interface).

Reason for issue: This issue arise because changes are not refreshed for newly developed/ customized entities between development environment and D365 F&O User interface.

Solution approach:

Using “Refresh entity list” option provided in standard D365 F&O, All available entities can be synced between development environment and UI.

Below are the steps to refresh entity list:

1. Access “Data management” work space using below path:

         Path: Go to “System administration > Data management”.

     

             

   2. Click “Framework parameters” in “Data management”:

3. On the “Data import/export framework parameters” select “Entity settings” tab and press “refresh entity list”.

Above steps will resolve sync issue for entities between dev environment and UI.

In case if you face any issue, please feel free to reach me at my personal email - daxmanish@outlook.com

Enjoy J

Deploy D365 F&O environment on azure

Prerequisite:

·         Verify that you have an Azure subscription, and that you are a co-administrator on it.

·         Verify that you have access to an LCS (Life Cycle Servics) project and permissions to deploy an environment.

·         Verify that you’ve connected your Azure subscription to your LCS project by using the information in the AzureResource Manager onboarding topic.

Steps to deploy D365 environment:

1.       Select a project on LCS and press + (Plus) icon in Environment tab, Select application and relevant platform version from the provided drop down list as shown below:

2.    Select environment topology:

·         For Finance and Operations, select the most recent Azure Resource Manager (ARM) topology, in my F&O Development case it is “DevTest”.

     3. To create Development environment let’s select the highlighted one. For Test and build environment, select the first one topology from available options shown in below screenshot:

     4.   As mentioned in the prerequisite above, it is assumed Azure subscription is attached with the selected LCS project,  system will ask to select Azure connector now:

    5.   Give unique environment name in Azure subscription, this will help to identify environment. Click on "Advance settings" button to check environment configuration details on “Deployment settings” window:

     6.     Environment resource configuration and versions can be checked and modified in “Deployment settings” window:

Select the size of the virtual machine (VM). All the sizes for VMs that are enabled for ARM end with v2. You must use D* v2 sizes for Finance and Operations workloads. MS recommends D12v2.

     7. Once click on “Next” button in “Deploy environment” window, confirm message box is popped up  with “Deploy” and “Cancel” options.

Click “Deploy” button and relax… your environment will be deployed on cloud.

 Final price list can also be calculated in azure price list link.

     8.  Once the deployment is completed, Environment will be visible in “Environments” section of LCS.

    9.  To get access and other details of the environment, select the “Demo” environment all information can be found “Manage environment” page.

In case if you face any issue, please feel free to reach me at my personal email - daxmanish@outlook.com

Enjoy J

Models management - Dynamics 365 F&O

Dynamics 365 F&O is completely changed from the previous versions of AX. Now customization is managed using models and Packages, managing the models is pretty simple and handy if you know the relevant commands.

Below are few commands which can be helpful for you to play with models and could be very useful while customizing the AX related tasks:

So to use models,  first and foremost open Command prompt as "Administrator"

Now time to place command as per the requirement:

          Export Model:

To take backup of your model in development Environment, use the ModelUtil.exe tool and the -export directive.

ModelUtil.exe -export -metadatastorepath=[path of the metadata store where model should be imported] -file=[full path of the file to import]

Example:

K:\AosService\PackagesLocalDirectory\Bin\ModelUtil.exe -import -metadatastorepath=K:\AosService\PackagesLocalDirectory  -file=J:\Manish\ModelBackup\RSys-Manish.axmodel

      Delete Model:

To delete a model file in AX Environment, use the ModelUtil.exe tool and the -delete directive.

ModelUtil.exe -delete -metadatastorepath=[path of the metadata store] -modelname=[name of the model to delete]

Example:

K:\AosService\PackagesLocalDirectory\Bin\ModelUtil.exe -delete -metadatastorepath=K:\AosService\PackagesLocalDirectory  -modelname=”RSys”

Import Model:

To install a model file in development Environment, use the ModelUtil.exe tool and the -import directive.

ModelUtil.exe -import -metadatastorepath=[path of the metadata store where model should be imported] -file=[full path of the file to import]

Example:

K:\AosService\PackagesLocalDirectory\Bin\ModelUtil.exe -import -metadatastorepath=K:\AosService\PackagesLocalDirectory  -file=J:\Manish\ModelBackup\RSys-Manish.axmodel

       Replace Model:

If the model already exists, you need to replace it using the "-replace" switch:

Example:

K:\AosService\PackagesLocalDirectory\Bin\ModelUtil.exe -replace -metadatastorepath=K:\AosService\PackagesLocalDirectory  -file= Manish\ModelBackup\RSys-Manish.axmodel

Post the above actions don't forget to build and compile the application  ;)

After updating the model it may also be necessary to synchronize the database as well.

In case if you face any issue, please feel free to reach me at my personal email - daxmanish@outlook.com

Enjoy J