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
We have come across the question while looking a Microsoft KB3182046. This adds extra functionality to the BACS supplier payments, such as the payment advice and attending note reports.
The payment formats are configured using the Global Electronic Reporting (GER) framework which is described here: https://ax.help.dynamics.com/en/wiki/general-electronic-reporting-ger/
When configuring a reporting (i.e. payment) format, one can either start from scratch or download the configuration that is provided by Microsoft – the latter being the most common when using any of the well-known formats. The LCS knowledge base article describes the change just as “Updated GER configurations are available for download in the LCS Shared asset library”. For a starter in the AX7 world like me, this was not enough. When trying out what I thought was right, I got it wrong for a couple of times, so I decided to document the steps to apply the configuration. These steps should apply not just to the specific BACS payment format, but any GER configurations that need updating. It would be nice if Microsoft would update their instructions to be more detailed.
1. In AX, go to Electronic reporting workspace
2. Under the configuration provider Microsoft, click Repositories to open the list of configured repositories
3. Select the repository with type LCS and click Open
Be patient – it may take a few minutes to load.
If you do not have the LCS repository in the list, use the Add button to create it. This is quite straightforward – just choose the type to be LCS.
4. From the list of reporting configurations on the left, find “Payment model”
Warning: DO NOT try to import the BACS (UK) configuration right away, start with the correct version of the payment model. Although importing the format will also import the parent model, it will use a WRONG version of the payment model, so it will not work and will fail with a very undescriptive error during payment generation: “Object reference not set to an instance of an object” when the parameter “Print payment advice” is turned on. This seems to be a bug in the core GER functionality and will be hopefully be fixed by Microsoft in the future.
5. From the list of payment model configuration versions on the right, find the version that corresponds to the fix
As mentioned above, it is important to use the model version that matches the payment format version.
In the current case, there is a new version of the model, with a reference to the KB article, that must be imported before the format itself.
6. Click “Import” above the versions grid on the lower right
This will import the chosen model version into GER configurations in AX.
When going back to the payment model on the left, you will see the “Exists” flag ticked on the chosen model. For some reason, it has also created a draft version 3, but this should not matter for now.
7. From the list of reporting configurations on the left, find the payment format – BACS (UK)
8. From the list of configuration versions on the right, find the version to import
The new version for the BACS format was there with a reference to the KB number.
6. Click Import on the version to load the configuration
7. Go to Electronic reporting > Configurations and verify that the new model and format configuration versions are present with status Completed
8. Configure your purchase ledger method of payment to use the correct GER configuration
9. All done.
Create a supplier payment journal and generate payments to test.