This order is significant both for those who see the Customer Profile from the Web App and for those who receive a response from the Teams Bot
Why don`t taking advantage of the order that we assigns to the Customer Profile In the last "M" of the Unification process (with the "move up"and "move down" buttons)? . So that it respects this given order not only for the table (entity) but also for the Unified Profile, displayed in the app.
Thanks.
Comments
Hi Nils,
We found several issues with the Dataverse approach:
- For B2B, Measurements are not available in Dataverse
- CI tables in Dataverse are virtual, and we do not have relationships with Accounts and Contacts in order to use the information in Sales forms.
Could you comment on this points, pls?
Thanks and regards,
Agustín
Category: Customer Profile
Hi,
I understand the point you mentioned that, "this page is not aiming to be a main consumption place of CI".
I asume Power BI (MSFT ecosystem) is the indicated tool for powerfull visualizations, but the connector is in preview mode and only works in the Desktop.
Some estimated date for general available(?)
Regards
Category: Customer Profile
Thank your for this suggestion.
We have no plans to allow customization of the Customer's view in the Customer Insights' web app. I would like to explain why:
The Customers view in our app serves as a basic example of how data for single customer can be visualized. This page is not aiming to be a main consumption place of CI data for our users. We expect data created by Customer Insights to be used within your existing business application (like for example Dynamics 365 Customer Service). For this we rely on Dataverse with its connectors and API as the sustainable consumption service for our customers. This gives you flexibility in choosing how to solve your business users different consumption needs including role based access management and a fast way to building custom apps with Power Apps.
Category: Customer Profile
Scott Stabbert (administrator) on 8/9/2023 3:29:05 PM
Thanks for your suggestion.
This suggestions has a number of up votes, but its unclear what the value would be as the display of fields should not (typically) be tied to field order in the DB table itself.
Ordering columns based on the order in Merge is possible, but then would require columns order is changed when the merge field order changes.
If anyone can provide a scenario of where the display of fields cannot be managed in the presenation layer and how ordering columns would help, that would aid us in prioritizing this request.
Thanks,