Max Nguyen

This post is our own opinion and does not necessarily reflect the opinion or view of our companies or Microsoft.

How to upgrade to Visual Studio 2017, .NET 4.7.2 for PU36/10.0.12 and higher

For the upcoming Dynamics 365 Finance Updates, Visual Studio 2017 and .NET runtime 4.7.2 required for PU36/10.0.12 or higher; New VMs deployed with PU36/10.0.12 or higher will have Visual Studio 2017 as well as .NET runtime 4.7.2 already installed. For your dev/test/build Tier1 VMs, Microsoft recommends just redeploying a new VM, and you will be all set! If you cannot deploy new VMs, please follow below steps to update .NET runtime, VS 2017 before installing PU36/10.

Dynamics 365 FinOps Data Integration using Microsoft Forms (Part 2)

1. Example two: A new Forms response is submitted then Flow promts for an approval request before a new record is created in Vendors table In the last example, we created a simple Flow to create a new Vendor Account from submitted Forms responses. The process was made as simple as it could be: When a new Forms response if submitted, a new Vendor Account will be created on D365FO client.

Dynamics 365 FinOps Data Integration using Microsoft Forms (Part 1)

With any D365FO users, Data Management workspace and Data Entities should have become one of the most used and well-known tools in the system. We all agree how powerful such integration framework is, especially when it comes to a large number of records that we would need to import into different tables. The classic method that we have been utilizing is to include all source data in a single (or multiple, much depending on the purpose and order of data integration) Excel sheet, trigger an import execution, pass any validation layers that present and ultimately have the data available on D365FO.

Database Sync after data type on field has been changed

You will got an error like this when doing Database Synchronization after changing the data type of the field on the table: InvalidOperationException: Table … : Converting Field ‘..’ of Type ‘..’ to ‘..’ is not support. Please drop the original field, sync the table and add new field with same name if needed. {:.error} Solution: Drop the table and delete references from SQLDictionary 1 2 3 4 5 6 7 8 9 10 DROPTABLEAXDB.

Getting onebox VHD Dynamics 365 finance and operations virtual machine

1. Download Dynamics 365 finance and operations VHD files Go to the LCS main page and select Shared asset library or go to Shared Asset Library. Select the asset type Downloadable VHD. Find the VHD you are looking for based on the desired Finance and Operation version. The VHD is divided into multiple file parts that you need to download. For example, the asset files that start with “VHD - 10.

Azure Storage Emulator 'Port conflict with existing application', Dynamics 365 finance and operations

The Microsoft Azure storage emulator is a tool that emulates the Azure Blob, Queue, and Table services for local development purposes. You can test your application against the storage services locally without creating an Azure subscription or incurring any costs. When you’re satisfied with how your application is working in the emulator, switch to using an Azure storage account in the cloud. In Dynamics 365 finance and operations onebox environment, we also use Microsoft Azure Storage Emulator for same purposes.

Dynamics 365 finance and operations ODATA consuming - Length cannot be less than zero

When you consume a custom data entity, you get an error errorSystem.ArgumentOutOfRangeException : Length cannot be less than zero” and it works fine for standard data entities. {:.error} The reason is the temporary XML file where the metadata stored which mismatches with the metadata from https://<yourenvironment>$metadata You can follow this post to understand how to create the XML file. If you try to regenerate the metadata by saving the file, the XML will be accumulated, and the error keeps happening.