Dataverse Long Term Retention

here you go

Here just write anything and Click submit

I dont know

Rationaliziw subbing hibbbsy ihhsn igss shuhejdhjdhjdehdjdhejfrfjuyrsgtjymrewtgfdsr,uteygurjeghdrujgysdk,fsgdfhregreyfuewgfujfgsudf

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.

We followed the steps in the documentation ; the retention policy seems to have run completely (it is stated as "completed"), but no record were archived ; there are all marked as error. I opened a MS support ticket (2309200050003267), but we got no valuable answer from the support team. They have no clue why it is not working.

The support told us to write this feedback in this thread...

When Environments are copied from in admin portal the dataflows are not copied or at least do not show up in the dataflow area. They do however exist in the Dataverse table called dataflows. because of this trying to import a solutions containing managed dataflow will fail with an obscure error. The only way to fix this is to delete the records form the dataflow table and re import the managed solution. The issue is that you can't delete data flow records that are marked as managed... If you can't copy the dataflows and make them available in the target environment, then the records for those dataflows in the dataflow table should be removed allowing the next solution import to import the dataflows.

Example the production environment is copied to a new UAT environment we then import the latest solution changes for testing, but the import fails because the dataflows are missing.

Hi Product group team,

If Dynamics or any other Microsoft services detect any outage from Microsoft, the system should link the outage page (where we encounter any error message) which had a link to azure health status or Microsoft Service health. This would have saved us time reviewing our network connections, capacity, or any other environmental factor before we would engage Microsoft.

Thank you.

Currently, if we wanted to change a grid control for an entity, we need to update it manually. Now, if we wanted to use that grid control for all entities, we need to manually update all entities. This will consume a lot of time as there's a lot of entities in Dataverse.

It would be best if we have the capability to update or change the grid control for all entities in bulk.

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.