Natsuko Sugawara

Currently, the feature to filter the date column of a view semiannually is not working; even if the Fisical Period Template is set to semiannually, the view will still be displayed in quarters. This feature would make Dynamics 365 more useful.

"Teams chats and Channels Integration" uses the Graph API to display search results, while Teams search uses the search functionality provided by Microsoft 365 to display search results. Therefore, even if you search for the same keywords, the search results for both will be different.

Since different search results are inconvenient, please consider making the search results for "Teams chats and Channels Integration" the same as those for Teams.

The Excel import display shows a creation date and an end date. The creation date is in date and time format, while the ending date is in date format. Having the end date also in date and time format makes Dynamics 365 more useful. Please consider implementing this.

There is no way to automatically reflect record items selected on the search screen to form items created in model-driven applications as a standard feature. Please consider providing this functionality as a function of the standard. Having this functionality available will make Dynamics 365 more convenient.

If you update a solution that is not on the top level layer, the updated solution will not be on the top level. As noted on the following page, for other solutions besides model-driven apps, forms, and sitemap components that use the "top wins" behavior, the solution on the top level layer determines the functionality of the component.

https://learn.microsoft.com/en-us/power-platform/alm/solution-layers-alm#top-wins-behavior

Therefore, it can be very inconvenient for an updated solution not to be at the top level. Please consider adding functionality to help this situation.

Updating a solution that is not on the top level layer does not make the updated solution top priority. For other solutions, except for model-driven apps, forms, and sitemap components that use "top wins" behavior, the solution at the top level determines the functionality of the component, as described in the following pages.

https://learn.microsoft.com/en-us/power-platform/alm/solution-layers-alm#top-wins-behavior

Therefore, it can be very inconvenient for an updated solution not to be at the top level. Please consider adding functionality to help this situation.

The current behavior is that if Table B is added to a subgrid of Table A, the user cannot write to Table B if the user has write permission for Table B only. To write to Table B in the subgrid, the user must have write permission for both Table A and Table B.

If we do not permit editing of Table A, but allow writing to Table B in the subgrid, this is currently not possible. This situation is very inconvenient and we would appreciate an early fix.

Standard Dynamics 365 is not covered by the NIST CSF, as indicated below. To address security risks, we recommend aligning with the NIST CSF. This addition will enhance the safety of using Dynamics 365.

https://learn.microsoft.com/en-us/compliance/regulatory/offering-nist-csf#microsoft-in-scope-cloud-platforms--services

Currently there is no way to hide the hierarchy icons shown in the view. Once this Idea is implemented, Dynamics 365 will be much more useful.

Currently, security roles given to users can be viewed on a per-environment basis. However, when there are many environments within a tenant, it is inefficient to check each environment individually. Please consider implementing a function to check security roles granted to users on a per-tenant basis.