You’re offline. This is a read only version of the page.
2
Take a scenario of deleting a column and recreating with a different datatype. When exporting and importing the solution to another environment it will fail on import. In traditional SQL server based application you might handle this situation by having a migration SQL script to create the column with a different name, migrate any existing data from old to new column, delete old column, rename new column to old name. With Dataverse you don't have that luxury. What is the approach here?
Hi @hickley
As per OOB Behavior you cannot change Datatype of Field once it get Created, You need to Recreate the Field.
If the Destination Environment is Unmanaged Solution --> Delete there and import it
If the Destination Environment is Managed Solution --> You cannot Delete instead Create Difference Field in Source and Import it and Map the Respective code for the new fields.
Please mark as Answer if it is helpful and provide Kudos
Subscribe : https://www.youtube.com/channel/UCnGNN3hdlKBOr6PXotskNLA
Follow me on Twitter : @rampprakashd
Blog : https://microsoftcrmtechie.blogspot.com
Share
Report
All responses (
Answers (
