Good day all
Here's the scenario I am facing.
We have a simple setup table which typically contains 3 or 4 records. A field name, which is part of the primary index, was spelled incorrectly and also had an incorrect prefix. This has been rectified on a dev box and the changes submitted to source control. When creating a package and deploying this to various Azure environments, the deployment will fail due to index violations - duplicates (the field that was modified will now have blank values in the table).
My question: is it possible to run a data cleanup script on the target environments before a package with changes that will cause index violations will be deployed there? It would be amazing if this script could be included with the package and executed first to prepare the environment for the new code.
Can anybody offer advice on the best way to approach this please?
Thanks in advance!
Kind regards, Stephen
