Dynamics 365 Customer Insights - Data

Unable to delete the data source in Customer Insights – Data

It will be great to have this option added.

You are creating a Lead Score model that sets a score based on email opens sent by Dynamics 365 Customer Experience.

Currently, if the personal information (contact information) that opened the email has multiple leads tied to it, they will all be scored the same with respect to the lead.

We believe it would be useful to have the ability to set a score for one lead only, depending on the criteria, when there are multiple leads in the personal information, so that a clear score can be measured.

"Combine a group of fields" detailed here : https://learn.microsoft.com/en-us/dynamics365/customer-insights/data/data-unification-merge-tables

Currently when you combine address fields into a group it still leaves the original fields in the unification output (the customer profile table).

This can be confusing as you end up with 2 addressline1, 2 addressline2 etc, one that isn't combine and one that is.

Please can the original field either allowed to be excluded or hidden from the result of the unification if the fields are used in a combined group.

Currently the "Combine a group of fields" has a 15 data source limit.

The group by provides a way of keeping together fields in unification, like address fields, that should not be treated as individual fields, The current limit means that you would need to pick which data sources not to combine and show in the end unification which is problematic.

Please can this be removed so it can match the number of data sources.

Based on the document Exclude bot interactions - Dynamics 365 Customer Insights from Microsoft, inflated open rates are a known occurrence due to the fact that bot protection does not apply to email opens. As a result, nonhuman traffic can artificially increase open rates, leading to misleading analytics.

I would like assistance in identifying a solution to prevent this issue from occurring in the future

In our case, we want to add an event registration form to our website, which means that people who are not yet in our contact database could register. They would fill out an event registration form, not a marketing form and therefore would not have consent for marketing communication. Without this prior consent, they would be unable to receive any emails, such as the event confirmation email.

Unfortunately, this approach doesn’t meet our current requirements. We need a solution that accommodates non-registered contacts in the system who still need to receive event-related emails.

While I have no issue using a marketing form (since it would include the DOI process), it does not have the event-specific fields, such as session summaries or speaker information. Additionally, I would not be able to integrate the marketing form into the event system, where registrations, check-ins, and other event-related actions are managed.

As it stands, according to the current logic, a new contact must register twice: first with the marketing form, then with the registration form and finally confirm the DOI email.

However, this issue could be resolved if the registration form had the same functionality as a marketing form, triggering the DOI process and sending the automated first DOI confirmation email.

We would appreciate any suggestions on how this process can be streamlined while still meeting the necessary requirements.

If you are creating a measure that shows the latest order based on several different tables ingested from several different systems, it is easy to create the latest order per customer per ingested table, but combining the latest order over several different tables, or just measures, is not possible. Either it has to be done by first putting these into activities and then doing "latest" on the activities, or running the calculations outside of CI-D, with for instance, Fabric.

Currently the ListAllSegments operations include almost everything about segment metadata, but it does not include the 'SegmentType' which indicates the segment is 'Static' or 'Dynamic'. Having this attribute as part of the same API can help any consumer system.

It takes a almost a minute to populate the list of tables, and to open up the Manage Table dialog, and then Save. Can you please optimise this performance.

A quick wins could be:

1) Do not automatically populate Synapse tables. In our environment we only use F&O tables

2) The method of saving a CSV of all our tables used in a file should be replaced/augmented with the ability to save the set of tables within the tool.

Currently, columns of type Choice ingested from Dataverse into Customer Insights Data display numeric values instead of readable labels. It would be very helpful to support ingesting Choice columns with their human-readable labels and values for better usability.