Unanswered

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

(0) Share

Report

Posted on by Community Power Pla...

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

Export solution from CDS, unpack solution.zip with solutionpackager /action:extract, then check into source control
Completely reset environment (via admin portal or DevOps pipeline)
Install any dependent managed solutions
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?

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (6)

Answers (0)

BenediktB 50 on at

Like (0)

Report

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?

//Benedikt

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

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

Was this reply helpful? Yes No
BenediktB 50 on at

Like (0)

Report

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

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

These are classic (sync) workflows that we created.

Was this reply helpful? Yes No
MattB-MSFT Microsoft Employee on at

Like (0)

Report

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?

Was this reply helpful? Yes No
EricRegnier 8,720 Most Valuable Professional on at

Like (0)

Report

Hi @Anonymous ,

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!

Was this reply helpful? Yes No