-
Replace a hyperlink with different text
The account URL cannot currently be replaced with any other characters. For example, by using the string "Click here", it becomes an omitted link and leads to ease of viewing of the view.
For users using the Sales Hub app, the visibility of the view is easier for administrators to design. Therefore, if this feature is implemented, it will be very beneficial for users who use this app.
-
Change the default view of user entities in bulk
Currently, "Manage users in Dynamics 365" sets the default view of the user entity with a pin. However, because each user must change the default settings, it takes time to display the same view to all users.
Being able to change default settings in bulk makes design easier for administrators. Therefore, if this feature is implemented, it will be very beneficial for users who use this app.
-
Feature to check the sort order in personal view
The user can set multiple sort orders for the personal view by pressing shift.
However, there is no way to check the priority of multiple settings.
This feature is very useful because it allows users to see the contents of the view more efficiently.
-
Ability to link to Outlook when a user changes the owner of an appointment in D365
When a user changes the owner of an event in D365, Outlook creates a new appointment and retains the past owner's appointment. Therefore, it is necessary to delete unnecessary appointments, which leads to unnecessary trouble. When changes to the owner of an appointment are reflected in Outlook, users are relieved of scheduling complexity. This feature is very useful because it allows you to view the user's work more efficiently.
-
About launching browsers other than those set as default tabs
The browser is used separately depending on the system.
The default tab set in personal options is set to start with Microsoft Edge, but I usually use it with Chrome.
With this setting, opening CRM in chrome freezes the browser.
Even if you use a browser other than the default tab, if the browser does not freeze, the user's convenience will increase.
-
Get AzureAD user information directly in model-driven apps
In order to acquire AzureAD user information in a model-driven application, settings such as acquisition with WebAPI and registration as a stub user are required, and direct acquisition is not possible.
If direct acquisition becomes possible, user information from AzureAD can be incorporated directly into the model-driven app form, and can be associated with external user records.
This feature makes it easier for administrators to design and improves convenience for users without being distracted by unnecessary data.
-
Track emails from shared mailboxes using Dynamics 365 APP for outlook
Shared mailboxes cannot be tracked using Dynamics 365 App for Outlook.
You can track emails sent to mailboxes for which the user has delegate permissions, but not from shared mailboxes.
Therefore, having this feature will increase convenience for many users.
-
Duplicate unique name for subgrid name can be set in legacy UI.
It is possible to set duplicate unique names for subgrids in the legacy UI.
If the unique name is duplicated, the record display will be unintended, so please add a function to prevent duplication.
By setting this function, customers can prevent unintended duplication and prevent unexpected records from being displayed.
-
Allow tracking of group addresses
Currently record tracking between dynamics365 and outlook does not support group email addresses.
Some companies need to track emails sent by customers to group emails. There are also times when tracking records in group mail is needed within a company. Enabling this feature will improve user convenience.
-
Checking the usage capacity for each user
Currently, Dataverse capacity is pooled across tenants, and there is no way to view capacity usage per user.
Due to the nature of the default environment used by all users, many customers will
1. Set the capacity that can be used throughout the company
2. Charge the user who caused the overage fee
Above he considers two options.
However, the current functionality does not allow his second option, so he has no choice but to choose the first option.
Capacity management will become even more convenient if you can check Dataverse usage for each user.