Ai Morita (Japan Concentrix KK)

Currently, the ability to export the unified view has not been implemented. In model-driven apps, exporting is performed as a single operation that requires the use of tools like Power Automate. Therefore, introducing this feature would greatly enhance user convenience.

Currently, the ability to export a unified view from multiple screens has not been implemented. Implementing the feature to export a unified view directly within model-driven apps would greatly enhance user convenience.

There is no standard functionality that automatically enables auditing when new out‑of‑the‑box entities are added to an app.

The operation of manually enabling auditing each time results in additional effort and becomes a burden for customers.

If this capability were added, it would greatly improve usability for users.

At this time, there is no available way to implement this functionality. However, there have been previous community and Ideas submissions, indicating that this is a highly requested feature among many customers.

Since this directly impacts the end-user experience, enabling this capability would greatly improve usability for users.

Currently, when you download a Dataverse data import template, even if your environment contains more than 500 items (fields), not all items will be displayed in the template.

This functionality is not currently provided as a standard feature; therefore, creating a template that includes all fields requires the use of external tools.

Adding a feature to display all items (more than 500 fields) in the data import template will allow users to work without relying on external tools, thus improving user convenience.

In Dynamics 365's standard charting functionality, the order of the horizontal axis sometimes does not match the order of the data (the order on the grid or a meaningful order in business context).

Currently, this chart is not designed to match the column order, and the standard functionality does not provide a way to arbitrarily control the order.

However, if the order of important metrics, such as sales data, changes unintentionally, there is a concern that users may misinterpret data trends, potentially impacting decision-making.

Therefore, we would like you to consider providing the following flexible sorting functions for the horizontal axis of the chart:

• Option to match the sorting order of the grid or view

• Sort specification based on any column or condition

• Explicit control of ascending/descending order

These added features will improve the consistency of data visualization, allowing users to understand and analyze information more accurately. As a result, we expect this to lead to improved quality of business decisions and an enhanced user experience.

Currently, Azure Functions does not provide a standard capability to detect changes in Microsoft Dataverse tables directly, especially in scenarios where polling or outbound-only communication is required.

In many enterprise environments, strict network security policies prohibit inbound communication, making it difficult to adopt event-driven architectures such as Webhooks or Business Events (Dataverse → Azure Functions). As a result, users are unable to implement change detection scenarios using Azure Functions when inbound connectivity is restricted.

If Azure Functions (or Dataverse) could support a standard mechanism for detecting changes via outbound communication (for example, polling with change tracking or a lightweight delta API optimized for Functions), it would significantly improve usability in restricted network environments.

This enhancement would enable:

• Implementation of change detection in environments where inbound communication is not allowed
• Greater flexibility in designing secure, outbound-only integrations
• Simplification of architectures that currently require additional services (e.g., Logic Apps, Power Automate) as intermediaries
• Broader adoption of Azure Functions for enterprise integration scenarios with Dataverse

Currently, users must rely on workarounds or alternative services, which increases complexity and operational overhead. Providing this capability as a standard feature would greatly enhance developer experience and expand supported architecture patterns.