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).
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).
Dynamics 365 for Operations (a.k.a. AX7) provides several endpoints for web service. In this blog post, I want to describe consuming a D365O custom web service in a C# application using the SOAP endpoint.
For a detailed description about service endpoints, you can read the official documentation at https://docs.microsoft.com/en-us/dynamics365/operations/dev-itpro/data-entities/services-home-page.
The main advantage of the SOAP protocol is its descriptive functionality through the WSDL language. SOAP endpoints provide detailed description about contracts and parameters to call each service method. Visual Studio has a great functionality that can read the service description and automatically generate proxy classes to access the service methods.
Let’s do an example of consuming a D365O web service in Visual Studio. Continue reading