Ad sh

The intelligence feature has been implemented in the Dataverse search, but the Japanese spell check has not been implemented.

We would very much like to see the Japanese spell check function implemented.

When outputting data using an Excel template, the formatting of the first line of the main data sheet is applied to the entire sheet, but the formatting is not applied to another sheet connected to the main data sheet.

Therefore, it is necessary to apply formatting to the other sheet in advance, but if the amount of data to be output with formatting applied becomes large, performance will deteriorate and a timeout error will occur, making it unusable (extremely slow movement when there are more than about 30,000 items). The formatting of the first line should be reflected to the entire data sheet, even if it is not the main data sheet.

Once created, the type of calculated fields cannot be changed by default.

Each type has its own upper data limit, which causes arithmetic errors when creating graphs, etc. We would like to be able to change them accordingly.

The current behavior is that once an entity is created, when the user tries to edit it to an active entity, the checkbox is grayed out and cannot be checked, so it cannot be made an active entity.

Some people have voiced that if an entity that was originally intended to be created as an activity entity is created as a normal entity and cannot be re-edited, the efficiency of business operations will be reduced.

Therefore, we would like the checkboxes to be ungrayed out so that they can be edited as activity entities.

Currently, when sending mail from "Activities" - "E-Mail", there is no such thing as a mailer daemon implemented, such as no recipient when sending mail to a non-existent email address, and it is impossible to determine if the mail is really being sent.

To get rid of this problem, we would like Dynamics 365 to implement a function to detect if the email address does not exist.

Currently, there is no function to restore deleted records, which causes harm when accidentally deleted. The only temporary solution is to remove delete privileges for each user, and since no action can be taken for deleted records, we would like to see the function implemented.

There are fields in the e-mail entity such as To, CC, etc., and that one is a field called PartyList.

This type of field allows multiple references to user and customer records, but it is not possible to create a new field of this type.

The PartyList is a useful feature and we would very much appreciate it to be applicable to the fields you have created.

We would like to be able to control the following for each user: general user and administrator.

Example) Estimated (quote) entity

1. person in charge A creates quote A (state: draft)

2. Approval processing is performed (state: active)

3. When person in charge A displays Quote A, he/she cannot edit it because the status is active.

4. when a person other than person in charge A displays Quote A, the status part can be changed, and the status is returned to draft and can be changed. After the change, make it inactive again so that all users cannot change it.

I want to make it possible to realize 4. in business rules.

As an example, when a customer contact is registered in a sales case entity, the customer contact is automatically registered in the related parties field as well.

We would like to see such a functionality implemented that would allow us to create a "connection role" that would register a person in any field to another arbitrary field when the person registers in any field.

Currently, the Remote Assist app is not available in China.

We have a desire to use the application using Hololens, so we request that it be made available.