Dataverse Long Term Retention

Sometimes we have in-app notification we can enable in the app settings.

If the subject text is too long, it will end with ... instead of displaying it in a new line.

I checked it is because of the CSS text-overflow: ellipses, and over-flow: hidden. This is not using the WebResource under solutions, it is hard coded stuff, we cannot change, so I am just wondered if it is possible to make the subject display fully,or change the CSS for the subject in the product.

I can confirm that if I change text-overflow->unset, and over-flow: scroll, it can display full text by scrolling, but it is in my dev console.

Thanks!

When configuring Address Type choices in CE and Address purposes in FnO. There will be multiple choices when choosing the purposes in the Address field in Workers form. But when choosing the Address Type in Worker Address table, they will only allows one record there. Hence when mapping for Dual Write, we will need to add all the Address Type combinations possible on both CE and FnO, this is time consuming and ineffective. There should be better system or when choosing in CE, we can have multiple choices.

Today it's not possible to update table configuration for Azure Synapse Link for Dataverse using a solution.

Got it confirmed by Microsoft Support, ticket: ID#2306140050000427.

When working with multiple environments we would like to transfer the table configuration using solutions, the same way normal customizations are handled.

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.

Hello MS team,

My customer would suggest there should be ERDs for tables in Dataverse, or at least OOB tables. They need to better understand the relationships between them to build their reports.

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.

Dear Team,

I would like to propose adding a feature in Power Pages to log portal login account update actions(Delete,Update,Create). Currently, there is a lack of detailed logging for certain scenarios, which can make it difficult to track issues, especially when production data is involved, and Dataverse items are being updated randomly and intermittently.

By implementing detailed user action logs in Power Pages, we can better track and resolve issues, ensuring data stability and security in the production environment. This would also provide the development and operations teams with more actionable insights, enabling them to quickly pinpoint and address potential problems.

Thank you for considering this suggestion, and I look forward to your feedback.

We have related table fields as a View column in a table's Quick Find View. However, it is not displayed in the search results. This is a great inconvenience for the business, and it is requested that the related field be supported in the search results in a future release.

Currently, there is no audit for any change made to the Environment Settings in Power Platform Admin Center. So, when there is an unknown change in a setting such as 'Audit settings' for the log retention policy for an environment, we have no clue to who changed it.

All current audit features are for changes inside the environment Dataverse and access to environment. Even Azure Purview.

I'd be great if we can have an audit to record change for general Settings in Power Platform Admin Center as well.