Dynamics 365 Sales

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.

Improvement request to how Dynamic Marketing List member list is generated and stored in database

Current behavior:

Dynamic Marketing List member list is generated each time we navigate to Marketing List > Members tab via a fetch query.

This does not generate relationship between target audience records (Contact / Account / Lead) and Marketing List.

When clicking on audience record > Related > Marketing list, the view only displays audience inclusion for Static list, not Dynamic list.

Enhancement request:

We'd like to have the Dynamic list generate a relationship between the records, so that we can view the audience's participant via Related view.

Business Impact:

This will greatly improve data readability for users.

Current behavior (by design): In Dynamics 365, the Mailbox setting "Delete Emails after Processing" cannot be changed to "Yes" from the Mailbox UI screen. This field is read-only by design, even when:

• Creating a new mailbox record (the option is not available at creation time)
• Setting the mailbox to Inactive → Active again
• Editing the mailbox through the standard form

Currently, the only workaround is to create a Business Rule on the Mailbox table to force-update the field value, which is not intuitive for end users and administrators.

Requested improvement: Please allow users (with appropriate privileges) to directly toggle the "Delete Emails after Processing" field between Yes / No from the Mailbox configuration UI, without requiring workarounds such as Business Rules or backend modifications.

Business value / Why it matters:

• Many customers integrate Exchange Online with Dynamics 365 and want emails to be removed from Exchange Online once synced to Dynamics 365 (for storage, compliance, or data governance reasons).
• Currently, admins must rely on workarounds (Business Rules) which:
• Are not discoverable for typical admins
• Increase configuration complexity
• Are difficult to maintain and troubleshoot
• Making this setting directly editable in the UI would significantly improve the usability and administrative experience of Dynamics 365.

Customer impact: This feedback has been raised by enterprise customers in Japan (e.g., OKI Software) and would benefit all organizations using Server-Side Synchronization with Exchange Online.

Currently, sharing links within the same environment and database creates unnecessary friction in daily collaboration. Even when all users involved are part of the same team and have identical access rights, they often cannot open shared links directly if these are tied to a specific App ID or app context.

This is particularly problematic in collaborative workflows, where link sharing is intended to simplify communication and speed up processes. Instead, it introduces confusion and additional steps, as colleagues are unable to reliably open shared record, even though they are already authorised and working in the same environment.

From a security perspective, this limitation does not seem necessary. Access is already properly controlled through existing role- and permission-based security mechanisms. If a user does not have access to a record, the system correctly prevents it. However, if a user does have the required permissions, the link should open seamlessly regardless of the originating app or App ID.

A more flexible and user-friendly approach would therefore make much more sense:

• Allow app-independent record links without embedding a fixed App ID
• Or automatically redirect users to the correct app based on their permissions
• Or provide a universal link format that dynamically resolves the correct context for each user

This would significantly improve usability and collaboration within teams, reduce unnecessary friction in daily workflows, and increase the practical value of the sharing functionality, while fully maintaining the existing security model.

This request is related to Dataverse Excel import behavior and is not specific to Dynamics 365 Sales.

When importing Excel data into Dataverse, values entered as numbers in Excel may be interpreted as numeric values during the import process, even when the destination column type is set to Single Line of Text.

As a result, thousand separators (commas) may be automatically applied (for example, "40561041" becomes "40,561,041"), which alters the original value.

This behavior creates operational challenges, especially in the following scenarios:

- Preparing large datasets manually in Excel

- Using the data for search or indexing purposes (e.g., Copilot Studio), where preserving the exact input value is required

Currently, the available workarounds include:

- Setting the Excel cells to Text format before entering data

or

- Manually adding an apostrophe (') before each value

However, these approaches require additional manual effort and are not practical when handling large volumes of data.

■ Request

We request the ability to preserve the original values exactly as entered in Excel when importing into Dataverse, without applying numeric formatting such as thousand separators (commas). 

Ideally, this should be provided as an option or configurable setting during the import process.

Currently in dashboard if a view is made which calculates something and is customized, Microsoft does not allow us to filter it via a date like quartely, weekly etc. So for customization via dates, should allow us to select that option like regular OOB dashboards.

Currently, each environment (Development, Test, Training, Production) requires a separate URL for access. This can be confusing for end users, especially in organizations that maintain multiple environments as part of their delivery lifecycle.

We propose the ability to access multiple environments through a single entry point URL, where users can then select the relevant environment as an “app” or via an environment switcher within the same interface.

This would provide a more intuitive and centralized user experience, similar to how users can switch between apps or workspaces in other Microsoft products.