What's New: Auto-Applying Templates in Integration with Dataverse (2024 release wave 2)
Auto-applying configuration templates in the Business Central integration with Dataverse (2024 release wave 2): rule-based filters and evaluation priorities set in integration table mappings choose which template applies to synchronized records, in both directions. Includes a demo creating a customer from Dataverse.
- Introduction to Auto-Apply Templates
- Integration Table Mappings Overview
- Conditional Template Application with Rules
- Demo: Creating Customer from Dataverse
- Results and Template Application Verification
- Feature Overview and Bidirectional Support
- Conclusion and Additional Resources
Overview
The video explains how, in 2024 release wave 2, configuration templates can be applied conditionally to data synchronized between Dataverse and Business Central. Instead of extending the integration solution, you configure the rules in the integration table mappings.
A drill-down from the integration table mapping opens new Configuration Template Setup pages. There you define filters a record must meet for a template to apply, and a priority that sets the evaluation order. The demo creates a customer from Dataverse and checks which template was applied, using a default template tied to a country code value. The video also covers that the feature works in both directions.
Key points
- Templates are applied conditionally to data synchronized between Dataverse and Business Central, based on rules, without extending integration solutions.
- Setup is done in the Integration Table Mappings, by drilling down to the Configuration Template Setup page.
- Filters define the conditions a record must satisfy for a template to be applied, for example a country code value.
- A priority field sets the order in which template filters are evaluated when a new record is created; the conditions are checked one by one.
- Both table configuration templates and integration table configuration templates are supported.
- Integration table configuration templates apply when a Business Central record is created in Dataverse, so the feature works bidirectionally.
Features
Every feature below: status not stated, demoed.
| Feature | At |
|---|---|
| Auto-Apply Templates in Integration with Dataverse | 0:06 |
| Configuration Template Setup Pages | 5:01 |
| Template Filter Conditions | 1:47 |
| Template Evaluation Priority | 2:47 |
AL objects mentioned
As heard in the captions. A name that matches one object page by exact type and name links to it; the others stay as named.
Not found in BC28-30: table “Integration Table Mappings”, page “Configuration Template Setup”.
Quotes
- 0:06 “in 2024 release wave two you can now conditionally apply uh configuration templates to the data that you synchronize between data ver and business”
- 0:26 “having this configurable rule-based and automated way uh to select the templates to apply when you synchronize data and when you create new records”
- 1:47 “when you have more more templates and they have some conditions or some rules on how these templates are applied you will see the”
- 1:47 “I have a sort of a default uh template that gets applied when a country code is set to uh us or it’s uh”
- 2:47 “once the new record gets created we will go uh one by one and see which of these uh which of these conditions are”
- 5:41 “there’s also integration table configuration templates which apply for when um business Central um record is actually created in data ver so it works”
Presenters (as heard): Ivan ktic.