Kaisei Isobe

In order to prevent users from transitioning to the Power automate portal site during operations, we want to allow the administrator to hide the flow creation button and the flow display button that are displayed when the user clicks the [Flow] button on the ribbon menu.

We have also confirmed that it is not currently possible to edit in Xrmtoolbox.

If you can hide the two buttons to control the user's transition to the Power automate portal site, you can also prevent user confusion. Therefore, we would like to request the addition of a feature that makes it easier to hide the button in the future.

When you want to get SharePoint Online information through a connector through a model-driven app, the model-driven app and SharePoint Online must be in the same tenant due to the nature of the functionality of the current SharePoint Online integration.

If they are not in the same tenant, we will not be able to realize it, so we will ask for improvements so that we can do something in the future.

If you only want to translate what is displayed in the search field, you must also translate the original record as it is.

If you want to translate all the records from the reference, it will take a lot of time and effort if the number of records is large, so I would like you to improve the function so that only the content displayed in the search field can be translated with the standard function.

When enforcing internet permission settings for Power Platform services, the Power Platform service doesn't provide a JSON file with URL information.

However, in the case of Microsoft 365, a JSON file containing URL information is provided.

We look forward to the future development of JSON files that contain URL information in Power Platform services.

We want to back up only Dataverse tables, but if we do that, it will be a backup function for the entire environment.

We would like to see a feature that allows us to back up only tables in the future.

We are aware that there are currently some ASCII codes that do not allow us to register with Dynamics.

However, it is not clear what kind of characters cannot be registered, and it is unclear what kind of characters need to be converted during the data migration work.

Therefore, we would like to see a list of ASCII codes that are not available in Dynamics in the future.

We are linking screens with other systems, including data parameters.

The parameter needs to be encoded as SJIS, but it cannot be converted to anything other than UTF8.

Currently, there is no ability to convert to SJIS in the Dynamics 365 standard components.

We think it would be useful If the encoded feature to SJIS will be implemented in the future.

So we expect future implementations.

Currently, it is not possible to copy the environment to a different region within the same tenant.

If it is possible to copy the environment to a different region, the time and effort of recreating the environment again will be reduced, and we believe that it will be very convenient.

Therefore, we expect improvements in the feature of allowing us to copy environments to different regions.

In DeltaLake synchronization, an event occurred that stopped synchronization due to a failure on the Azure side, and the event was resolved.

However, in the future, we would like to respond by automating monitoring, but it is not possible for tenants to monitor automatically due to functional limitations.

Therefore, for the future, I would like you to add a function to the audit log that can detect when DeltaLake synchronization fails on the tenant side or the environment side.

When an email is sent from the Dynamics timeline, the process of sending the email is passed to the Exchange side, and if the Exchange limit is caught there, the email is returned to Dynamics.

However, at present, there is no way for Dynamics to detect the error when it is returned from the Exchange side.

we would like you to add a function that allows us to detect it on the Dynamics side as soon as the email is returned back to Dynamics.