Like
Share
ReportIntroduction
Part of a broader blog post series, this article will guide you through the creation of a Model Driven App (MDA) Quick View form of Dynamics 365 Customer Insights - Data (CI-D) customer profile attributes, which can then be easily embedded in another MDA form, such as the main Contact form used by Dynamics 365 Apps.
Fig. 1. - Two CI-D customer profile attributes surfaced in the main Contact form in Dynamics 365 Customer Insights - Journeys (CI-J).
This capability relies on CustomerId Backstamping being set up and operational between CI-D and Dataverse, so check the previous article in the series if you want to know more about this prerequisite.
Step-by-step Configuration
As CI-D customer profile attributes are directly available in the CustomerProfile table, and the Contact table has a lookup to it thanks to CustomerId Backstamping, it’s quite straightforward to surface those attributes in the Contact context. It won’t provide many customization options though.
In the maker portal, navigate to the CustomerProfile table, and from there create a new “Quick View” form that will contain one or more attributes you’ll want to surface in the Contact form:
Fig. 2. - CustomerProfile default forms as seen in the maker portal
Fig. 3. - New CustomerProfile “Quick View” form with chosen attributes - label is hidden for cleanness
Fig. 4. - Main Contact form is edited to add a Section with the previously created “Quick view” component
Managing Dependencies
As soon as you start using a CustomerProfile attribute in a Model-Driven App form, such as “Loyalty score” in the example shown in Fig. 3., then CI-D will prevent you from excluding this attribute from profile unification if you try to save the change.
You’ll need to remove the dependency first - in this case removing the attribute from the form - before being able to remove it from profile unification.
Fig. 5. - CI-D enforcing a dependency check on tentative attribute removal when used in a downstream Model-Driven App.
Exact dependency on this column can be found in Dataverse:
Fig. 6. - Navigating through the table columns to show their dependencies.
Fig. 7. - Example of the dependency existing due to column usage in a Quick View form.
*This post is locked for comments