Migrating Dataverse Table Schema between Environments

[steersebastian]

Hi at all

We're having for customers solutions implemented which use different Canvas Apps as well as Flows and some stored procedures in combination with SQL DB via on-premises gateway (Azure SQL but with private endpoint). We use DEV, TEST and PROD environments in Power Platform for ALM.

We now need to migrate everything to Dataverse since we want to get rid of the SQL DB.

We do manage to replicate the data schema and data from SQL to Dataverse with dataflows which is straightforward so far. The initial replication between environments does not seem to be a big problem as well. 

But we did not find a possibility to migrating evolved table schema from DEV to PROD environment without toughing the productive data on PROD. For example if I want to extend tables von DEV environment and want to migrate these changes to PROD but don't want to lose the data on PROD.

Thanks a lot for any hint!!

Best

Sebastian

[rampprakash · Accepted solution]

Hello @steersebastian,

Is your DEV and PROD already in Dataverse ? if yes, then try creating a SOLUTION in Dev Environment, export the same and Import it in PROD, without any data change it will work properly.

Before Proceeding this Step, Create a COPY Of PROD to another instance and import the same from DEV to the COPIED Instance and proceed the same

Please mark as Answer if it is helpful and provide Kudos

Subscribe : https://www.youtube.com/channel/UCnGNN3hdlKBOr6PXotskNLA
Blog : https://microsoftcrmtechie.blogspot.com

[steersebastian]

Hi @rampprakash 

Thanks a lot! Thats exactly what I wasn't sure about.

Best 

Sebastian

[steersebastian]

@rampprakash Do you know about any limitations while importing the solution with modified data schema from DEV to PROD? For example any collisions with new relationships, mandatory columns , business rules etc. which might not be applicable on existing data on PROD? 

Is there any official documentation from MS?

Thanks a lot for you support!

Best

Sebastian

[rampprakash]

Hello @steersebastian 

There is only one condition, for example you already have a Field in a table with Datatype as Whole number in Prod (new_wholenumber), then in Dev if you are recreating the same logical name from Wholenumber to text.

Now you are importing the solution again at that time you will get an error because of DataType Change.

Apart from that you can move anytype of data like Relationship or Business Rule or flow or Security Role or table or Process etc

Please mark as Answer if it is helpful and provide Kudos

Subscribe : https://www.youtube.com/channel/UCnGNN3hdlKBOr6PXotskNLA

Blog : https://microsoftcrmtechie.blogspot.com

[RakeshTel]

Hi @rampprakash ,

While promoting the solution that has Custom Dataverse Tables from Dev Env to Prod Env?

Does Prod Tables data records overwritten with Dev Tables values or Prod Tables Data Records will remain intact?

What is the best practice, do we need to remove custom tables from solution or will keep it inside? Thanks in advance!!

The requirement is that Prod data will remain intact if we deploy new version of managed solution. Managed solution will have Custom Dataverse Tables in it, and there will not be any change at field/column level.

Since Dev env has different data records , need to ensure prod data records will not wiped out with Dev data record during deployment of managed solution.