Earlier I discussed how to create a new type of Electronic Report in Dynamics 365 for Operations (AX7), which can be viewed here, Creating new Electronic Report. In this post, I want to look at how to modify the application so that a new Electronic Report can be run from a form using a menu item. Continue reading
Dynamics 365 for Operations (AX7) Electronic Reports are used for statutory or country specific document purposes. The Microsoft repository contains a lot of document types out of box, but sometimes we need to create custom document. Let’s look at the scenario when we need to create electronic report for Sales Packing Slip.
There are two ways of running an Electronic Report:
- From the Electronic Reporting module, by selecting a configuration and running it.
- From a menu item, by linking a service to a proper Electronic Reporting configuration.
Both of these methods need a properly configured model and configuration and in this post we’ll discuss how to do this. Continue reading
Let’s continue our journey looking at how Microsoft Flow can be used to build integrations for Microsoft Dynamics 365 for Operations (also known as AX7).
- Part 1 – how Microsoft Flow works in general and how it connects to AX7; example of creating records via OData
- Part 2 – introduction to the on-premises data gateway, to work with files on the local computer or a local network share; example of uploading local file data into AX7 via OData
This latest post gives examples of how to export data from Microsoft Dynamics 365 for Operations (AX7) into your local file system in JSON, XML, or CSV formats using Microsoft Flow. It assumes that the Microsoft Flow on-premises data gateway is already installed and configured – if not, refer to Part 2 of the series.
- Based on recurring schedule (trigger),
- Query all customer records from AX (action),
- Transform the data into required format (action),
- Write the data into a file in the local file system (action).