Dataverse Long Term Retention

Intercompany and Direct Delivery orders are significantly contributing to the growth of customer's database, leading to usage overruns beyond the threshold.

Currently, there is no functionality to archive or clean up these types of orders, which limits customer's ability to manage database size effectively.

To address this, a propose developing a feature that allows for the archiving or clean-up of Intercompany and Direct Delivery orders. This feature should include criteria for archiving orders, such as orders older than a certain date or orders that have been fully processed and closed alongside the Inventory archival and not being allowed for data archival with intercompany chain linked to sales orders.

Additionally, an automated process should be implemented to periodically archive orders based on the defined criteria, along with a manual archiving option for users. It is also essential to ensure that archived orders can be easily retrieved if necessary for auditing or reference purposes.

Furthermore, a clean-up function may be developed to remove unnecessary data from the database, reducing its size and improving performance.

Implementing this archiving and clean-up function will help manage database growth, improve system performance, and ensure compliance with data retention policies.

However, it is important to note that addressing this issue will require additional resources and an increase in system resource requirements.

The impact of this issue is particularly significant for retail operations, where efficient database management is crucial for smooth functioning.

I have encountered a situation where two solutions are entangled in a circular dependency. To resolve this, we need all the dependent components of a solution within the circle to exist in order to untangle them. However, I have deleted all the dependent components in both solutions in lower environment, making it impossible to untangle the two solutions. I believe many people face the same problem. Therefore, I suggest implementing a function to address this circular dependency issue. Thank you!

This is a simple request: we would like to be able to archive purchase orders and related tables please.

During the installation of the Long Term Data Retention application on Dataverse for Finance and Operations, the setup process validates the existence and status of supported tables. However, if a table is not present due to a disabled configuration key, the installation fails entirely.

For example, if the Retail or Call Center configuration key is disabled, the installation will be interrupted with an error such as:

Correlation ID: 2f6fd346-2449-4cda-96a7-365a53163f33

Error Details:

msdyn_ArchiveServiceAnchor: NotProvided

msdyn_SalesOrderArchiveTablesVirtualEntities: Import Failed

Error Code: 0

Description: Unable to complete updates to the Track Changes option for table 'MCRSalesTableBiEntity'.

Exception Details:

Change tracking cannot be enabled because the data source 'MCRSalesTable' in the data entity 'MCRSalesTableBiEntity' references the disabled table 'MCRSalesTable'. Please enable the configuration key 'MCRCallCenter' associated with the table.

Suggestion:

Enhance the installation logic of the Long Term Data Retention app to gracefully skip (or optionally log) entities referencing tables that are unavailable due to disabled configuration keys, rather than causing a full installation failure. This would make the application more robust and compatible with environments where certain features are intentionally turned off.

Benefits:

• Increases the flexibility of installation across various D365FO configurations
• Reduces setup errors and support tickets for standard installation scenarios
• Aligns with modular deployment best practices by supporting partially enabled configurations

I would like to propose a new feature for the Power Platform Admin Center that enables administrative users to export a comprehensive list of users within a selected environment, along with their:

• Security roles
• Associated licenses
• Environment access
• Other relevant user metadata (e.g., business unit, access mode, etc.)

This feature should include a customizable view, allowing administrators to:

• Select which columns they want to include (e.g., email, roles, license type, etc.)
• Apply filters to narrow down specific user groups
• Export the data into formats like CSV or Excel for audit or reporting purposes

Why this matters:

Today, gathering this type of information involves switching between multiple tools (Admin Center, Dynamics 365 settings, Azure AD, etc.), and often requires technical knowledge or custom scripts. Providing this functionality in a centralized, user-friendly interface would:

• Streamline administrative and audit tasks
• Improve security and compliance visibility
• Save time for administrators and IT teams
• Enhance governance, especially in large or multi-environment tenants

Suggested Features:

• Environment picker to scope the export
• Role-based filtering (e.g., show only users with “System Admin” role)
• Ability to sort and group by user attributes
• Export button with format options
• Scheduled export or API access (optional but very valuable for automation)

If you agree this feature would be helpful, please upvote and comment to show support!

Issue description: There is no way to export System Administrators across all environments.

Example:

Admins can only export/ retrieve users with assigned security roles in an individual environment. They would have to go through every organization and take action within its database.

Actions taken:

I've tried to perform several ways to retrieve users with assigned security roles, but there are no options to export users with appropriate roles within the environments they are member of.

Expectations:

==========

We should have an OOB workaround to export a user list which include their organization and appropriate security roles accordingly.

The user can use the "Group by" feature in Power Apps Grid Control, which is visible in the App view. However, we would like this functionality to also be available in the Table design view.

We recently encountered a case where a customer noticed that certain Customer Copilot features had been re-enabled in their Dynamics 365 environment—without any prior notification or indication of who made the change. Upon investigation, we discovered that D365 currently lacks audit logging or tracking capabilities for these types of configuration changes.

While it’s possible that system updates or automated processes may re-enable features, customers need full transparency and traceability for all changes—especially those that could impact data access, user experience, or compliance.

Problem

There is no built-in mechanism to:

• Identify who enabled or modified a feature (user, service principal, or system process)
• Determine when the change occurred
• Understand what was changed and the before/after values

Suggested Solution

Introduce comprehensive audit logging for all feature enablement and configuration changes in Dynamics 365. This should include:

• Who made the change (user/service principal/system)
• When the change occurred
• What feature or setting was modified
• Previous and new values of the setting

Additionally:

• Make this audit data accessible via Advanced Find, Power Platform Admin Center, or Audit History
• Optionally, allow customers to configure notifications for changes to sensitive or critical feature flags

Hi Microsoft,

The description of an email with a modified date is currently moved automatically to file storage after 365 days.

It would be great if Microsoft could enable a feature to be able to allow the end user to amend (lower) Microsoft hard coded 365 day period. We have lots of clients that need to store emails as part of business continuity and legislation and with the email description being held in Database storage for a long period of time they have a constant challenge of trying to reduce data to ensure it stays within the restrictive capacity provided by Microsoft.

We understand that moving the email description to File storage removes the ability to search on the body of the email, but in the majority of cases this is not an issue. Our clients generally find emails based on the From or Subject field.

As you know we always have the ability to purchase more storage, but as of today 1gb per month at around £33 is something most SMB don't want to entertain.

Please can we request this functionality is added to the core Power Platform product.

When I attempt to query the aaduser table using FetchXML it throws an error: "There is an unterminated string literal at position 15 in 'givenname:sdas'." FetchXml Condition is “condition attribute="givenname" operator="eq" value="sdas & dasa”,Escaping for other characters, such as '<', works without issues. When I add filter criteria to the Microsoft Entra ID entity view in a Model-Driven App, an error 'Invalid filter clause' occurs if the text in the filter criteria contains the '&' character. The error does not occur when the text contains other special characters such as '<'. Additionally, using filters containing the '&' character in views of other entities does not result in an error.