Dataverse Long Term Retention

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!

We are using Form Component Control to show a sub-form on the main form. The main form contains a lot of fields, and the sub-form is placed at the end of the main form. We have some mandatory fields on the sub-form, and if the screen is too small, then the mandatory fields validation is skipped on save, thus letting the user save the record without having all the mandatory fields filled in. We noticed that if you scroll the main form a little bit, then the sub-form loads and all the mandatory fields work as expected.

As I understood, this is expected, because the validation is done on the client side and only the visible part is rendered, but I don't think that this is a good design, considering that we can have mandatory fields in the sub-form.

Proposal:

Either don't let makers have mandatory fields in the sub form or make a toggle to forcefully render the sub-form in the UI, so it is properly validated.

When using certain fuzzy searches in the dataverse we can see a certain result match whilst filling in the searchfield (1 match) but when we press enter, this specific result isnt in the "top results page" as the word searched contains characters such as .- (without spaces, 1 long combination).

The result will only be available if we click on the specific entity page.

Idea would be to highlight multiple columns in setup which are seen as the most relevant ones to be displayed on the "top results" page, and therefor improving the general quality of top results

Give Provision to delete Audit records with Event Type Audit Log Deletion and also give the provision to delete specific entity records with Timeframe as this will help to retain only specific records with specific timeframe.

The largest table by far in our system is ProjTransPosting. We've been told it would fall under a project operations LTR scenario if it were to be included in the future. Please consider adding this new scenario.

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.

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

The sorting in Dataverse search is determined by the relevance score rather than custom criteria. We would like to have the sorting done on each column based on the created-on/modifie-on date, allowing us to sort the search results as we do in views.

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.