Dataverse Long Term Retention

Our environment has encountered a 1,000-attribute limit on the entity/table in D365, necessitating a rearchitecture of our usage. We propose increasing the attribute limit to 2,500 to accommodate larger data collections and prevent similar issues. This change would support smoother implementations and ongoing operations, such as enabling the installation of CJI and other applications.

I am using Dataverse and building a Model-driven application in Power apps. Right, there is not functionality that allows to format a decimal column as % or $ I know that it is posible to define columns as currency but there is a los of limitations using in Power automate and defining formula columns, Rollups. Also, will be nice to include the same functionality for formula columns when th result is a decimal by example for calculation of the amount using the quantity and Unit price

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.

Issue:

-Cannot retrieve Retained data of Activity such as email, message, note while using edit filter in Activity view due to nature of Activity table. The query normally uses link-entity element to retrieve corresponding data in another table.

-Error message: The link-entity query is not supported.

-Current limitation: Queries are allowed on one table at a time. Joins and aggregation functions aren't allowed.

-Ask: The option to view retain data there should be hidden to avoid confusion for regular users. Or the current warning message should be more meaningful to user.

Currently, the Dataverse Recycle Bin retains deleted items for only 30 days. After this period, the data is permanently deleted.

For some users, data may be accidentally deleted due to errors in their code or workflows. For instance, a user might run a script that mistakenly deletes a large set of records because of a misconfigured filter. These users need time to correct these errors before restoring the data, and 30 days is often insufficient.

I propose extending the Recycle Bin storage period to 90 days. Alternatively, users should have the option to set a custom period for how long deleted data is stored before permanent deletion, similar to configuring audit settings.

We would like to suggest an idea that the URL field format can be modified such as automatically adding the key "https://" before user type in a link.

Also, we suggest that the error message when we type incorrect format can be changed to fit with different scenarios.

Create an option or feature to toggle the visibility of application in microsoft 365 such as (Power pages)

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.

Hello,

I got this link from your support and I can't find the right category though please send this bug to the right team:

Every time after the update of Power Automate Desktop the variable Microsoft.Flow.RPA.UIFlowService.ScreenDefaultResolutionEnabled in the UIFlowService.exe.config is set to false. Though I have to change every time back to true after update.

Please fix this bug.

Thank you very much.

Best regards,

Julia Pfeiffer

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.