Dynamics 365 Customer Insights - Data

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.

Add the ability to customize the layout of the Customer Profile page (move sections like Activity Timeline and Info) and let users rename activities name, currently it shows only source table names!

Today, there is no satisfactory solution for a datascientist to extract text from old word files ( binary doc and not docx ).

This is a big problem. We have millions of documents in this format, and it's very difficult to extract text from them.

- the word API only works under windows

- Openoffice doesn't handle parallelism very well.

- Antiword supports very few formats.

- Tikka is a java implementation that works well but remains limited. 

However, the Doc binary format specification has been published:

https://learn.microsoft.com/en-us/openspecs/office_file_formats/ms-doc/ccd7b486-7881-484c-a137-51170af7cc22

The funny thing is that even tools like Microsoft/MarkitDown don't support the doc format. You have to use openoffice. 

What we want is a command-line program, written in a compiled language (C++ / Rust), to extract a text file from a doc format. 

extract-doc file.doc > file.txt 

The format specification has been published in open access: 

https://learn.microsoft.com/en-us/openspecs/office_file_formats/ms-doc/ccd7b486-7881-484c-a137-51170af7cc22

If you can't do it, we can do it ourselves in a collaboration with Microsoft. But It has to be done. This is an essential need in the age of LLMs.

"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.

AI Clippy. The paperclip help dude from early 2000’s, bring him back!

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

It would be very good if there was a built in report showing the last x full system refreshes and how long these processes take. It is possible to build this yourself with the diagnostics data but it will not contain the dependencies as described in this excellent article by Fast Track SA Ashwini Puranik: https://community.dynamics.com/blogs/post/?postid=84fbbaaf-262b-f011-8c4e-7c1e5218b899

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.

Description:

Currently, in Customer Insights - Data, there is no consolidated view to check which segments are being exported. Users have to manually click through each export individually to verify the included segments, which is inefficient—especially for organizations managing a large number of exports.

Problem statement:

• No centralized view to see which segments are included in exports.
• Users must manually check each export, which is time-consuming and impractical when managing multiple exports (e.g., 100+).
• Lack of visibility makes it difficult to track and manage segment exports efficiently.

Proposed solution:

Introduce a unified export overview where users can:

1. See a list of all exports along with the segments they include.
2. Filter or search by segment names to quickly find relevant exports.
3. Optionally, export this overview for reporting and tracking purposes.