Electronic reporting destinations
You can configure a destination for each Electronic reporting (ER) format configuration and its output component (a folder or a file). Users who are granted appropriate access rights can also modify destination settings at run time. This article explains ER destination management, the types of destinations that are supported, and security considerations.
Electronic reporting (ER) format configurations usually contain at least one output component: a file. Typically, configurations contain multiple file output components of different types (for example, XML, TXT, or XLSX) that are grouped into either a single folder or multiple folders. ER destination management lets you preconfigure what occurs when each component is run. By default, when a configuration is run, a dialog box appears that lets the user save or open the file. The same behavior is also used when you import an ER configuration and don't configure any specific destinations for it. After a destination is created for a main output component, that destination overrides the default behavior, and the folder or file is sent according to the destination's settings.
Availability and general prerequisites
The ER destinations functionality isn't available in the Microsoft Dynamics AX 7.0 (February 2016). Therefore, you must install Microsoft Dynamics 365 for Operations version 1611 (November 2016) to use all the functions that are described in this topic. Alternatively, you can install one of the following prerequisites. However, be aware that these alternative provide a more limited ER destination experience.
- Microsoft Dynamics AX application version 7.0.1 (May 2016)
- ER destination management application hotfix
You can set up destinations only for ER configurations that have been imported, and for the formats that are available on the Electronic reporting configurations page.
The ER destination management functionality is available at Organization administration > Electronic reporting. Here, you can override the default behavior for a configuration. Imported configurations aren't shown here until you click New and then, in the Reference field, select a configuration to create destination settings for.
After you've created a reference, you can create a file destination for each folder, or for a file.
Note: You can create one file destination for each output component of the same format, such as a folder or a file that is selected in the File Name field. You can then enable and disable individual destinations for the file destination in the Destination settings dialog box. The Settings button is used to control all the destinations for a selected file destination. In the Destination settings dialog box, you can control each destination separately by setting the Enabled option for it.
Various types of destinations are supported. You can disable or enable all types at the same time. In this way, you can either do nothing or send the component to all configured destinations. The following sections describe the destinations that are supported.
Set Enabled to Yes to send an output file by email. After this option is enabled, you can specify the email recipients, and edit the subject and body of the email message. You can set up constant texts for the email subject and body, or you can use ER formulas to dynamically create email texts. You can configure email addresses for ER in two ways. The configuration can be completed in the same way that the Print management feature in Finance and Operations completes it. Alternatively, you can resolve an email address by using a direct reference to the ER configuration through a formula.
Email address types
When you click Edit for the To or Cc field, the Email to dialog box appears. You can then select the type of email address to use.
If you select the Print Management email type, you can enter fixed email addresses in the To field. To use email addresses that aren't fixed, you must select the email source type for a file destination. The following values are supported: Customer, Vendor, Prospect, Contact, Competitor, Worker, Applicant, Prospective vendor, and Disallowed vendor. After you select an email source type, use the button next to the Email source account field to open the **Formula designer **form. You can use this form to attach a formula that represents the selected party account to the email destination.
Note that formulas are specific to the ER configuration. In the Formula field, enter a document-specific reference to a customer or vendor party type. Instead of typing, you can find the data source node that represents the customer or vendor account, and then click Add data source to update the formula. For example, if you use the ISO 20022 Credit Transfer configuration, the node that represents a vendor account is '$PaymentsForCoveringLetter'.Creditor.Identification.SourceID. Otherwise, enter any string value, such as DE-001, to save a formula.
In the Email to dialog box, click the recycle bin next to the Email source account field to permanently delete the formula for the email source account. Alternatively, open the formula designer to change a formula that was previously saved. To assign email addresses, click Edit to open the Assign email addresses dialog box.
Use this email type if the configuration that you use has a node in the data sources that represents an email address. You can use data sources and functions in the formula designer to get a correctly formatted email address.
Note: A Simple Mail Transfer Protocol (SMTP) server must be configured and available. You can specify your SMTP server in Finance and Operations, at System administration > Setup > Email > Email parameters.
You can use this option to send output to either a Microsoft SharePoint folder or Microsoft Azure Storage. Set Enabled to Yes to send output to a destination that is defined by the selected document type. Only document types where the group is set to File are available for selection. You define document types at Organization administration > Document management > Document types. The configuration for ER destinations is the same as the configuration for the document management system.
The location determines where the file is saved. After the Archive destination is enabled, the results of configuration execution can be saved in the Job archive. You can view the results at Organization administration > Electronic reporting > Electronic reporting archived jobs. Note: You can select a document type for the Job archive in Finance and Operations, at Organization administration > Workspaces > Electronic reporting > Electronic reporting parameters.
You can save a file in a designated SharePoint folder. You define the default SharePoint server at Organization administration > Document management > Document management parameters, on the SharePoint tab. After the SharePoint folder is configured, you can select it as the folder where the ER output will be saved for the document type.
When the document type location is set to Archive directory, you can save a file to Azure Storage.
If you set Enabled to Yes, an open or save dialog box appears when the configuration has finished running.
If you set Enabled to Yes, a preview of the output is created. You can view some file types, such as XML, TXT, or PDF, directly in a browser window. For other file types, such Microsoft Excel or Word, the Microsoft Office Online service is used.
Power BI destination
Set Enabled to Yes to use your ER configuration to arrange the transfer of data from your instance of Finance and Operations to Microsoft Power BI services. The transferred files are stored on a Microsoft SharePoint Server instance that must be configured for that purpose. For more information, see Use an Electronic reporting configuration to provide Power BI with data from Finance and Operations. Hint: To override the default behavior (that is, the dialog box for a configuration), you can create a destination reference and a file destination for the main output component, and then disable all the destinations.
Two types of privileges and duties are used for ER destinations. One type controls the ability to maintain the overall destinations that are configured for a legal entity (that is, it controls access to the Electronic reporting destinations page). The other type controls the ability of an application user to override, at run time, the destination settings that are configured by an ER developer or ER functional consultant.
|Role (AOT name)||Role name||Duty (AOT name)||Duty name|
|ERDeveloper||Electronic reporting developer||ERFormatDestinationConfigure||Configure electronic reporting format destination|
|ERFunctionalConsultant||Electronic reporting functional consultant||ERFormatDestinationConfigure||Configure electronic reporting format destination|
|PaymAccountsPayablePaymentsClerk||Accounts payable payments clerk||ERFormatDestinationRuntimeConfigure||Configure electronic reporting format destination during runtime|
|PaymAccountsReceivablePaymentsClerk||Accounts receivable payments clerk||ERFormatDestinationRuntimeConfigure||Configure electronic reporting format destination during runtime|
Note: Two privileges are used in the preceding duties. These privileges have the same names as the corresponding duties: ERFormatDestinationConfigure and ERFormatDestinationRuntimeConfigure.
Frequently asked questions
I have imported electronic configurations, and I see them on the Electronic reporting configurations page. But why don't I see them on the Electronic reporting destinations page?
Make sure that you click New and then select a configuration in the Reference field. On the Electronic reporting destinations page, you can see only configurations that destinations have been configured for.
Is there any way to define which Azure Storage account and Azure Blob storage are used?
No. The default Azure Blob storage that is defined and used for the document management system is used.
What is the purpose of the File destination in the destination settings? What does that setting do?
The File destination is used to control a dialog box. If you enable this destination, or if no destination is defined for a configuration, you see an open or save dialog box after an output file is created.
Can you give an example of the formula that refers to a vendor account that I can send email to?
The formula is specific to the ER configuration. For example, if you use the ISO 20022 Credit Transfer configuration, you can use '$PaymentsForCoveringLetter'.Creditor.Identification.SourceID or model.Payments.Creditor.Identification.SourceID to get an associated vendor account.
One of my format configurations contains multiple files that are group into one folder (for example, Folder1 contains File1, File2, and File3). How do I set up destinations so that Folder1.zip isn't created at all, File1 is sent by email, File2 is sent to SharePoint, and I can open File3 immediately after the configuration is run?
The prerequisite is that your format must be available in the ER configurations. If you have your format, open the Electronic reporting destination page, and create a new reference to this configuration. You must then have four file destinations, one for each output component. Create the first file destination, give it a name such as Folder, and select a file name that represents a folder in your configuration. Then click Settings, and make sure that all the destinations are disabled. For this file destination, the folder won't be created. By default, because of hierarchical dependencies between files and parent folders, the files will behave in the same way. In other words, they won't be sent anywhere. To override that default behavior, you must create three more file destinations, one for each file. In the destination settings for each, you must enable the destination that the file should be sent to.