You are implementing Dynamics 365 Customer Insights - Data as your company's Customer Data Platform.
The initial dataset tables contain contacts from Dynamics 365 Sales. Commerce customers, and service management platform incidents.
In your first unification run. you set Dynamics 365 as the primary table but only see eCommerce profiles that were able to be matched with Dynamics 365 contacts. You need to ensure that unmatched eCommerce customers are also added as a profile in Customer Insights - Data
Solution: Make eCommerce customers the primary table in the match step.
Does this meet the goal?
You are implementing Dynamics 365 Customer Insights - Data as your company's Customer Data Platform.
The initial dataset tables contain contacts from Dynamics 365 Sales. eCommerce customers, and service management platform incidents.
In your first unification run. you set Dynamics 365 as the primary table but only see eCommerce profiles that were able to be matched with Dynamics 365 contacts. You need to ensure that unmatched eCommerce customers are also added as a profile in Customer Insights - Data.
Solution: Enable Include all records when editing the table during the match step. Does this meet the goal?
Your team developed and integrated a batch inferencing pipeline to Dynamics 365 Customer Insights - Dat
a. This allows (or a new custom machine learning (ML) model to run and deliver new insights to the unified profiles' data.
You need to make sure the workflow runs automatically with every scheduled refresh.
What should the (earn do?
Online orders are ingested into Dynamics 365 Customer Insights - Data through real-time data ingestion. Departments like customer service can see the orders directly in the Customer Insights - Data timeline when it is added to the contact form in Dynamics 365.
A service representative notices an error with the total order amount that is measured in Customer Insights - Dat
a. While today's online orders are visible in the timeline, the amount fails to update.
The representative needs you to explain why this is happening.
What reason should you provide?
You ate taking over administrative responsibilities tor a Dynamics 365 Customer Insights - Data environment at your organisation, and you are reviewing the indexes set up for Customer profiles in the environment.
One of your users has asked you to make DateofBirth a searchable attribute. You navigate to the Search & filter index page and see that there is already an attribute with the name DateofBirth It has an x in the Included in search column.
You need to report your findings to the use*.
What should you tell the user?