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.
Note
Community interest groups have now moved from Yammer to Microsoft Viva Engage. To join a Viva Engage community and take part in the latest discussions, fill out the Request access to Finance and Operations Viva Engage Community form and choose the community you want to join.
The Electronic reporting (ER) tool lets you define electronic format structures and then describe how to fill those structures by using data and algorithms that exist in the application. For more information, see Create Electronic reporting (ER) configurations. To specify the data flow for retrieving finance and operations data and using it to generate an electronic document, complete the following steps:
- Bind configured data sources to elements of the designed domain-specific data model. The model structure and selected data sources might be part of a complex hierarchical structure. Because of this complexity, final bindings can be quite large and contain many elements of different types, such as relations, tables, and methods. The bindings can become less readable and quite complex to review and understand, especially for non-owners.
- Bind data model elements with format components to define what data populates from the data model to the generated format’s output.
To improve the usability of ER mapping designers, the relative path feature was released. By default, the relative path representation option is turned on for any new instance of the application where ER design experience is enabled (Microsoft Dynamics 365 Finance, Microsoft Regulatory Configuration Service). The relative path parameter enables users to keep using the full path when working with this presentation of ER bindings.
When you turn on the relative path usage parameter, a single @ character replaces the path to the parent item in the binding of the current model element. The entire binding path becomes shorter, which makes the entire mapping more obvious and easier to understand. In most cases, no additional scrolling is required in the ER designer to view all the bindings of the data model.
When you start designing a new ER expression, you need to enter only one character to define a binding to a field of the parent item.
When you decide to change the data source of the parent model item, with absolute path usage, you have to manually rebind this model item, as well as all nested items, to a new data source. When you turn on relative path usage and select a new data source to bind to a parent item, you are offered an option to automatically rebind all nested elements of this parent item with one click.
If you confirm rebinding of nested items, the new parent item is placed to the path of each nested item containing the existing parent item. This feature doesn't break the backward compatibility of the ER framework. All previously designed ER configurations work with this new feature, and no upgrades or conversions are required.
Note
All changes that are introduced by mass modification of bindings of nested elements in model mappings are correctly saved in a configuration delta (trace of changes). This process allows customers to rebase their derived version of model mappings to any new base version of it that is modified by using this new feature.