web
You’re offline. This is a read only version of the page.
close
  • How to check the status changes in Dynamics 365 Customer Service

    Currently, to check if the status of Dynamics 365 Customer Service has been changed, you can only check the audit log. Since the audit log cannot filter only the status changes or export to CSV or similar formats, the addition of those features or having fields where status changes can be verified would greatly enhance usability.

  • I want to enable automatic editing of column properties.

    I am creating numbering rules using auto numbers in a model-driven app in Power Apps, and I would like to reset the auto number value on a specific date.

    However, the standard functionality only allows manual resets, and there is no feature for automatic resetting.


    Adding an automatic reset feature within the model-driven app would improve usability for users.

    I would appreciate it if you could consider adding this as a future update.

  • The tenant's default capacity cannot be checked from the Power Platform Admin Center.

    In the old Power Platform Admin Center, you could verify the default Dataverse capacity, File capacity, and Log capacity assigned to the tenant. However, in the new Power Platform Admin Center, it is not possible to view the default allocated capacities.

     

    Since the items previously visible are no longer accessible, users may become confused. Therefore, we believe it is necessary to have a feature that allows capacity to be checked, similar to the old Power Platform Admin Center.

  • Regarding users who receive environment capacity exceeded notifications.

    Currently, notifications for exceeding the allocated environment capacity or reaching a specified threshold are only sent to tenant administrators and environment administrators.


    If the users who receive these notifications can be managed not only by tenant or environment administrators but also through specific security roles, and if there is a designated screen for selecting recipients, it would make managing the environment much easier.

  • The summarization feature within the Copilot in the Dynamics 365 Sales app is not functioning for fields that have been enabled.

    Although the summarization for the account table has been enabled via [App Settings] - [Copilot] - [Opportunity] in the Dynamics 365 Sales app, there are cases where the summarization of specified items works and cases where it does not.


    Since this feature relies on AI to generate summaries, users can only select items manually. Because some selected items are not being summarized, we request an update to ensure that summarization is always performed for the items selected by users.


    This will enable users to confidently review the summarized information and reduce the effort required to check multiple pieces of data.

     


  • Even if the security roles for Basic User and Environment Maker are revoked from the user in the default environment, they are quickly restored.

    Even if the security roles for Basic User and Environment Maker are revoked from the user in the default environment, they are quickly restored.

    I understand this is a limitation of the default environment's design, but it poses a significant challenge in controlling and managing users.


    This is because users can inadvertently create apps within the environment without intention.


    I hope that automatic role assignment in the default environment can be disabled, allowing for more flexible management options.

  • About importing an Excel file with Japanese input

    When an Excel file that contains Japanese input is imported into the app, the furigana is imported along with the values.


    Due to the way Excel behaves when entering Japanese, furigana data is automatically registered.


    As a result, when importing the Excel file into a Dynamics 365 app, furigana is entered following the specified value. This requires correcting the unnecessarily imported data each time, which significantly reduces productivity.


    Since this is a major issue for users who use Japanese, we would like measures such as optional settings and other workarounds to be provided regarding the behavior during data import.

  • Regarding Teams usage of model-driven apps

    Starting from May 1, the use of model-driven apps embedded in Teams will be restricted/controlled.

    As a result, we would like to request the addition of a feature that enables our internal admin users to identify which users are accessing model-driven apps from Teams.


    At present, it is not possible to determine this based on available logs or configuration settings, so it will be necessary to consider how to provide effective notifications to admin users.


    This request is being posted as a requirement specific to model-driven apps, but in the future, extending this capability to other services (such as canvas apps) and allowing the origin/source information to be identified would also be very effective for internal communication. It would help prevent unexpected interruption/stop of business operations.