ODATA actions in Data Entities provide a way to inject behaviors into the data model, or expose custom business logic from Dynamics 365 Finance & Operations. You can add actions by adding a method to the data entity and then decorating the method with specific attributes [SysODataActionAttribute]

I use this Odata actions mostly in automation job like after refreshing data from PROD to UAT, we need to enable users, assign company to users, enable batches … Or simply consume it in Power Automate.

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.

Example two: A new Forms response is submitted then Flow promts for an approval request before a new record is created in Vendors tableIn 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. To make the process more reliable, we will now add an approval step to the Flow.

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.