Dataverse Long Term Retention

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

In a scenario where you have a table, standard Dataverse table or virtual table, with a lookup to a virtual table for F&O, you in a canvas app would like to be able to filter out all records related to a specific parent lookup record.

Example:

In my scenario below, I have created a Dataverse table called "Payment Plans" It has a lookup to Projects, a Virtual table for F&O table.

In my grid, I would like it to filter out only the payment plans connected to a specific Project

Second deployment of Patch will fail with error "import: FAILURE: A patch cannot be imported as a holding solution".

The reason why the pipeline failed to import the second patch after the first one is due to the pipeline step of the system using StageAndUpdate, while the Power Platform pipeline defaulted to ‘Upgrade’ with Overwrite only.

Based on the article for Power Platform pipelines, "Not currently. Pipelines default import behavior is Upgrade with Overwrite customizations."

Normally, for patch, the default method should be ‘Update’ instead. And we cannot use ‘Upgrade’ for patch. However, because Power Platform pipeline only support ‘Upgrade’, it causes conflict in the import logic for patch deployment. This is currently by-design behavior

For the pipelines in Power Platform to fully function as a deployment channel, we need the Update to be included in the future to enhance user experience.

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.

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.

Issue description: There is no way to block auto-assign roles for users in the Default Environment.

Example:

Users with the Power App license is always auto-assigned the System Maker role in the Default environment. Please note that we cannot remove it.

Actions taken:

I attempted to deactivate automatic license-based user role management and remove licenses for an organization. For further information, please refer to the following resource: https://learn.microsoft.com/en-us/power-platform/admin/opt-out-automatic-license. However, this process doesn’t apply to the default environment with specific roles.

From the document: "Does this impact the "Default" environment too? For the "Default" environment, Environment Maker and Basic User roles will continue to be automatically assigned to users even after opt-out."

Expectations:

==========

We should have an OOB workaround to prevent users, especially Guest Users, from accessing the Default Environment. Alternatively, if possible, the Opt-out option could be applied for the Default environment.

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.

I would like to be able to set a view to LookUp field on Business Process Flow(BPF). Since we can do it to the same field on the form, It would be nice to see customizations on the same field on BPF.

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.

Please enable to create long-term retention policy for Annotation entity without depend on other Activities