-
Full untracking capability in Dynamics App for Outlook
We propose the ability to completely untrack email conversations.
Automatic tracking can be temporarily untracked, but tracking will start again because of the tracking association.
Our expectation is that we don't want the conversation to be tracked any more, so we would like to implement the ability to completely untrack it.
-
Ability to check the list of failed devices when push notification attempts fail a certain number of times
Currently, if you send a push notification from Dynamics 365 Customer Insights and the attempt fails, you can only check it from Analytics.
If a customer deletes an app or something and a certain number of attempts fail, it would be useful to be able to check the list in the Customer Insights app.
If you could see a list of failed devices, you could delete them all at once, so it would be even more useful.
-
Measure individual lead scores when there are multiple leads in a lead score model
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.
-
Add a custom entity to the system lookup field "PartyList"
Currently, you cannot add new entities to the system lookup field "PartyList" (outside of the Send Email field).
If you can add a new entity (e.g. Customer Information Table), it will be easier to manage recipients.
We would like to implement the ability to add new entities to the system lookup field "PartyList".
-
Create child table records for the subgrid at the same time when parent table records have not yet been registered
A customer is creating tables with a 1:N parent-child relationship.
A subgrid has been placed on the parent table's form so that data from the child table can be registered.
Currently, a record can't be created in the subgrid's child table until the parent record is created first.
We would like to implement a function that allows records to be added to the subgrid's child table at the same time when no records have been registered in the parent table.
Implementing a function that allows records to be created simultaneously will greatly improve work efficiency.
You’re offline. This is a read only version of the page.
