Showing results for 
Search instead for 
Did you mean: 
Advocate II
Advocate II

Rebuilding environments from source (ALM) - diffs in CDS workflows

Microsofts ALM best practices state that you should be able to rebuild your environment from source.  i.e.  


  1. Export solution from CDS, unpack with solutionpackager /action:extract, then check into source control
  2. Completely reset environment (via admin portal or DevOps pipeline) 
  3. Install any dependent managed solutions
  4. Extract from source control, pack solution with solutionpackager, then import into source control.

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?

Advocate I
Advocate I

Hej pcole,

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?



Apologies, perhaps I should have been more clear, my issue is with Classic Workflows, created in the old Solution Explorer (not flows)

No worries. I got that.

I just wonder if you are referring to classic Workflows you created or some that come with dynamics.

These are classic (sync) workflows that we created.

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?

Super User II
Super User II

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!

Helpful resources

PA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

PA Community Call

Power Apps Community Call

Next call is happening on April 21st at 8a PST.

MBAS Carousel

Sign up for our May 4th event!

May the fourth be with you, join us online!


Experience what’s next for Power Apps

See the latest Power Apps innovations, updates, and demos from the Microsoft Business Applications Launch Event.

Users online (19,086)