Skip to main content

SharePoint Designer 2010 Reusable Workflows with Lookup Values


When you create a Reusable Workflow in SharePoint Designer 2010, that uses lookup values, and you try to deploy it in another environment, the lookup values will get broken.

This is happening because the list you are reading the lookup values from has another Guid.

Here is what I came up with to make this deployment easier:
  1. Deploy the reusable workflow in the new environment.
  2. Open the site you have deployed the workflow solution in SharePoint Designer
  3. Go to the related list (List and Libraries > Your Related List Name) and copy the new List ID value.
  4. Go to All Files > Workflows >  Your Workflow NameYour Workflow Name.xoml and open it in SharePoint Designer as XML (right click on it > Open with > SharePoint Designer (Open as XML))
  5. Find an  and you will find the old list guid in the ListId attribute 
  6. Replace the old guid value with the new one
  7. Save it and close the window.


The workflow should be pointing to the correct list.


Comments

Popular posts from this blog

Oversized buttons in IE

Yeah ... just another problem with IE. Lucky for all of us there are some people that can hack their way through the IE bugs. Here is a fix for this problem: input.button {   padding: 0.25em;   width: 0;   overflow:visible; } input.button[class] { /*ie ignores [class]*/   width: auto; }

Emmet in Visual Studio Code | cheat sheet link

Support for   Emmet   snippets and expansion is built right into Visual Studio Code,   no extension required .   Emmet 2.0   has support for the majority of the   Emmet Actions   including expanding   Emmet abbreviations and snippets .   Emmet is a web-developer’s toolkit that can greatly improve your HTML & CSS workflow   Links: Emmet in Visual Studio Code   Cheat Sheet (emmet.io)  

SharePoint 2010 State Machine Workflow error: "Failed to Start Workflow"

I've been working on a custom state machine workflow for a specific content type. I've associated the workflow to the content type like this: < AssociationCategories > ContentType ; 0x01........ </ AssociationCategories > This workflow has a custom initiation form, in which I'm passing some options to the workflow. After doing the association to the content type I started getting the following error: "Failed to Start Workflow" After doing a bit of debugging and head scratching I found that in the  StartListWorkflow () method inside the initiation page in which the workflow association is retrieved from the workflowList.WorkflowAssociations list and it does not take into consideration the ContentType workflow associations. private void StartListWorkflow () { SPWorkflowAssociation association = this . workflowList . WorkflowAssociations [ new Guid ( this . associationGuid )]; this . Web . Site . WorkflowManager . StartWork...