Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
How to Prevent Broken Workflow References in CRM 2011 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi 

    I got around 20 workflows on my development environment and its uses references to teams and other lookups. When I'm deploying the solution to other environments like test, its all broken on lookup references. I have to fix it manually on each workflow. 

    Is there any way to avoid this manual fixing?

    thanks

    Anil

    Monday, October 6, 2014 4:15 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    The only supported way is to ensure the teams and other lookups have the same primary keys in each environment, which you can only do by creating them programmatically, or with one of the migration tools that allows you to specif the primary key when creating the record

    Microsoft CRM MVP - http://mscrmuk.blogspot.com/ http://www.excitation.co.uk

    Monday, October 6, 2014 9:10 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    One way to make this easier is to clean up any condition expressions you have in the workflow. For example, you might have a workflow with a condition that checks if a record is owned by a specific team. Instead of using the lookup references in the condition, you could join on the Team entity and then use the "name" field in the condition.

    When you do this, your broken references won't occur inside the workflow conditions. You will still need to clean up broken references that occur anywhere else (e.g. when setting values etc).

    Please feel free to contact me via any of the following methods:

    Tuesday, October 7, 2014 8:32 AM