Microsofts ALM best practices state that you should be able to rebuild your environment from source. i.e.
This works fine. However when the next export and solutionpackager extract is done there's a number of diffs present - Mainly for CDS workflows, where GUIDs within the XAML change.
How can this be prevented?
what exactly do you mean with "CDS workflows"? Are those custom workflows you created and are therefore included in your solution or are you talking about standard OOB workflows?
Depending on how your workflow is built, if its referencing specific records in CDS, it does that by ID, thus you will see those ID's change from export to export..
Can you share a snipet of whats changing to help answer your question?
Hi @pcole ,
Unfortunately this is by design and cannot be prevented. As the previous user stated, within a classic workflow, there can be many references to data such as the Owner of the Workflow which would change if the deployment user/account is different or records GUIDs within workflow steps (e.g. assign a record to a Team/User) that might differ between the different environments. Also components that might change frequently are security roles for child business units as they are rebuilt upon solution import.
Hope this clarifies!
Check out these cool Power Apps & vote on your favorite!
Let's talk about the solution provided by Microsoft for Robotic Process Automation (RPA)
Check out whats happening in Power Apps
FIll out a quick form to claim your community user group member badge today!
Features releasing from October 2020 through March 2021