Dataverse Long Term Retention

We'd like to propose feature to impose data usage limitation for individual environments instead of allowing shared capacity on Tenant level.

This is to help customer better managing their storage and capacity usage in long term instead of having to replanning the capacity management as the business grows.

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!

Allow updates to 'Regarding' lookup columns using a dataflow.

Provide analytics on the Dataverse requests triggered from runs of Power Automate flows. This allows the identification and optimization of flows that are consuming the most requests.

Include details on how additional capacity was purchased (e.g. data purchased from vendor, allocated via licenses, etc) in the Power Platform admin center under Resources, Capacity, and Storage Capacity by Source, and Additional Capacity.

With elastic tables having recently gone GA some of the limitations of cosmosdb query which you can get round using User Defined Functions in a full cosmosdb installation you cannot do in Dataverse due to having no UI, way to implement.

When creating a new table, we define Display name, the Schema name will also be updated correspondingly. And this is by design.

If we define the Display name with upper-case, then the Schema name will also be defined in upper case correspondingly. And it will not match the lower-case Logical name. Because it seems that Logical name is always in lower-case by default when creating a new table and column.

In case, the Display name is defined in upper case, as long as we modify the Schema name to lower case from the beginning, then it would match the Logical name.

However, not all users will be aware of this behavior and only notice when using the schema name and logical name to develop other function.

For example, when we develop an Odata API to retrieve lookup value, if Schema name and Logical name are not the same, then it will return error. After we updated both the Logical name and Schema name to be identical, it works.

It would be a good idea if we can match Schema name and Logical name in both upper-case or lower-case when we create a new table and column automatically.

We did not find proper documentation related Dataverse search like how columns are got indexed and how we can remove unwanted indexed columns.

After testing we are able to remove columns from the index by removing them from displaying as columns within the Quick Find View. 

Please published Microsoft documents with all details for Index calculation and how we can remove unwanted indexed columns.

It would be better to make virtualtables from F &O to work on power pages fully functional. currently not all features are inculed or fully working as expected. also documentation related to virtual entities to be updated with latest changes if possible.

We propose enhancing Microsoft Dataverse Long Term Retained Data to include support for the open-source, vendor-neutral Apache Iceberg format.

This enhancement would allow us to export data to the Apache Iceberg Format and retrieve our long-term retained (LTR) data in an open-source, vendor-neutral format.

Additionally, we want to express our interest in having Dataverse LTR Data integrated into Polaris-Catalog.