Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Workflows are broken a...
Microsoft Dynamics CRM (Archived)

Workflows are broken after import.

(0) ShareShare
ReportReport
Posted on by Ahmad Saud 790

Dear all

I have exported a solution from Dyn365-sandbox and tried to import it into production (both are same version), import was done with warnings regarding all workflow related to CASE update/create operations.

in another words, the only broken workflows are the ones involving creating or update a CASE.

below is some of the errors i got:

Error: This workflow has errors and cannot be published. Please remove the errors and try again., Worklfow Id: fa56e196-1094-4d0e-b656-2760c7e1275a, ErrorMap Details: {ConditionBranchStep3: InvalidGuidReference ; CreateStep6: InvalidGuidReference ; ConditionStep2: InvalidGuidReference ; StageStep1: InvalidGuidReference ; WorkflowStep0: InvalidGuidReference}

Error: This workflow has errors and cannot be published. Please remove the errors and try again., Worklfow Id: 687c3784-5873-4e0a-9795-2b87c0271b88, ErrorMap Details: {ConditionBranchStep3: InvalidGuidReference ; ConditionStep2: InvalidGuidReference ; WorkflowStep0: InvalidGuidReference}

Error: This workflow has errors and cannot be published. Please remove the errors and try again., Worklfow Id: 9322a560-2fe5-46dc-a0b1-4671d1104b5b, ErrorMap Details: {ConditionBranchStep2: InvalidGuidReference ; CreateStep3: InvalidGuidReference ; ConditionStep1: InvalidGuidReference ; WorkflowStep0: InvalidGuidReference}

Error: This workflow has errors and cannot be published. Please remove the errors and try again., Worklfow Id: dc383196-b1d4-49a5-9f23-4c21be7e920e, ErrorMap Details: {ConditionBranchStep2: InvalidGuidReference ; ConditionStep1: InvalidGuidReference ; WorkflowStep0: InvalidGuidReference}

02685.4.png

*This post is locked for comments

  • Verified answer
    Alex Fun Wei Jie Profile Picture
    Alex Fun Wei Jie 33,626 on at
    RE: Workflows are broken after import.

    Hi,

    in this case, you can use crm data migration tool in sdk folder. copy the data from source to destination with same guid.

    community.dynamics.com/.../crm-data-migration-tool

  • Ahmad Saud Profile Picture
    Ahmad Saud 790 on at
    RE: Workflows are broken after import.

    thanks David, the production is almost new with very few customizations.

    secondly, is this "mechanism" a manual thing or there is a way to automate it.

    thanks.

  • Ahmad Saud Profile Picture
    Ahmad Saud 790 on at
    RE: Workflows are broken after import.

    Thanks Mohan

    i have only one lookup field, but there are 13 dependencies on this lookup, most of these dependencies are another workflows.

    so removing it is very difficult and risky. there should be another safer way!

    on the other hand, and since i am new to dynamics, i keep wondering how such silly bugs are still exist in such great product from microsoft!!

    thanks,  

  • Mohan Prasad MAni Profile Picture
    Mohan Prasad MAni 235 on at
    RE: Workflows are broken after import.

    1) Verify all the lookups and "Remove" them and add them manually again. This should remove the Red Cross sign (X) and when you correct all the lookups the workflow can be published. This is a workaround when you have less number of lookups used in the workflow

    Alternatively, The lookups that have been referred in the workflow should come from common source. We ran into this issue on a WF which had like 200+ lookups in it. We were able to resolve this by adding the lookup value imported using the same excel sheet. This resolved the issue

    Please mark the answer as Suggested if this resolves/helps your issue!

  • David Jennaway Profile Picture
    David Jennaway 14,063 on at
    RE: Workflows are broken after import.

    Most likely cause of the InvalidGuidReference error is if the workflow references specific records, and you don't have a corresponding record with the same ID (Guid) in the destination organisation. If you open up the steps that have errors, and click on each lookup field in turn, any that are missing will give you a 'Record does not exist' error.

    If this is the case, the ideal resolution is to have a mechanism to ensure such reference data exists and has the same Guid in each organisation. If that's not possible, or it's too late, then you can change the lookup values directly, but you'll have the same problem again if you deploy the workflows in the future

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,269 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,198 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans