Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
You can validate each configured Electronic reporting (ER) format and model mapping at design time. During this validation, a consistency check runs to help prevent runtime problems, such as execution errors and performance degradation. For every problem that the check finds, it provides the path of a problematic element. For some problems, an automatic fix is available.
By default, the validation automatically runs in the following cases for an ER configuration that contains the previously mentioned ER components:
- You import a new version of an ER configuration into your instance of Microsoft Dynamics 365 Finance.
- You change the status of the editable ER configuration from Draft to Completed.
- You rebase an editable ER configuration by applying a new base version.
Starting in version 10.0.49, enhanced validation management lets you validate multiple completed configuration versions in a single operation, run that validation in the background as a batch job, and review the results later through a persistent validation history.
Note
Enhanced validation management is a feature that you turn on in Feature management.
- Go to Workspaces > Feature management.
- In the list, find and select Enhanced validation management for Electronic Reporting configurations.
- Select Enable now.
Validate a single configuration version
To validate one version of a configuration, follow these steps:
- Go to Organization administration > Electronic reporting > Configurations.
- In the configurations tree in the left pane, select the desired ER configuration that contains the ER format or ER model mapping component.
- On the Versions FastTab, select the version of the selected ER configuration.
- On the Versions FastTab or on Action Pane (if Enhanced validation management for Electronic Reporting configurations feature is disabled), select Validate.
The system validates the selected version and reports any errors or warnings.
Note
When the Enhanced validation management for Electronic Reporting configurations feature is disabled, the Validate button is available on Action Pane and validates the selected version of the selected configuration.
When the Enhanced validation management for Electronic Reporting configurations feature is enabled, the Validate button is available on the Versions FastTab and validates the selected version of the selected configuration.
Validate multiple configurations
Note
This function is available starting in version 10.0.49 when the Enhanced validation management for Electronic Reporting configurations feature is enabled.
When you turn on the feature, the Action Pane on the Configuration repository page includes a Validation menu that you can use to validate several configurations at once.
Go to Organization administration > Electronic reporting > Configurations.
On the Action Pane, select Validation > Validate configurations.
In the Configuration validation dialog box, select the completed configuration versions that you want to validate.
Choose how to run the validation:
- To run validation immediately in interactive mode, start the validation and confirm when prompted. Interactive validation can take some time, depending on how many configurations you select.
- To run validation in the background, schedule it as a batch job by using the Batch button. When the job is queued, a notification confirms that the ER configuration validation job is added to the batch queue.
Tip
Run validation as a batch job when you select many configurations or large configurations, so that the work doesn't block your interactive session.
Only completed configuration versions are available for validation.
Validate ER format in the Designer
- Go to Organization administration > Electronic reporting > Configurations.
- In the configurations tree in the left pane, select the desired ER configuration that contains the ER format component.
- On the Versions FastTab, select the version of the selected ER configuration.
- On the Action Pane, select Designer.
- On the Format designer page, on the Action Pane, select Validate.
Validate ER model mapping in the Designer
- Go to Organization administration > Electronic reporting > Configurations.
- In the configurations tree in the left pane, select the ER configuration that contains the ER model mapping component.
- On the Versions FastTab, select the version of the selected ER configuration.
- On the Action Pane, select Designer.
- On the Model to datasource mapping page, on the Action Pane, select Designer.
- On the Model mapping designer page, on the Action Pane, select Validate.
Skip the validation when importing the configuration
To skip the validation when importing the configuration, follow these steps:
- Go to Organization administration > Electronic reporting > Configurations.
- On the Configurations page, on the Action Pane, on the Configurations tab, in the Advanced settings group, select User parameters.
- Set the Validate the configuration after importing option to No.
Skip the validation when you change or rebase the version's status
To skip the validation when you change or rebase the version's status, follow these steps:
- Go to Organization administration > Electronic reporting > Configurations.
- On the Configurations page, on the Action Pane, on the Configurations tab, in the Advanced settings group, select User parameters.
- Set the Skip validation at configuration's status change and rebase option to Yes.
ER uses the following categories to group consistency check inspections:
- Executability – Inspections that detect critical issues that might occur at runtime. These issues are mostly at an Error level.
- Performance – Inspections that detect issues that might cause inefficient execution of configured ER components. These issues are mostly at a Warning level.
- Data integrity – Inspections that detect issues that might cause data loss or runtime issues. These issues are mostly at a Warning level.
Additional resources
Use JOIN data sources to get data from multiple application tables in ER model mappings
Trace the execution of ER formats to troubleshoot performance issues