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

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)  

How to deloy InfoPath 2010 "Administrator-approved form template" to SharePoint 2010 programaticaly

Scenario: you've developed and InfoPath 2010 form. This form contains code that requires full trust, so you need to deploy it as a administrator-approved form template. This requires an farm administrator to check, upload and activate the form for the site collection. Solution:  to automate this operation I  created a farm level feature - w hen the feature is activated upload the form  programmatically and w hen the feature is deactivated remove the form  programmatically. Here is how I did it: 1. Create an Empty SharePoint Project and set it to be deployed as a farm solution 2. Add an Empty element item - EmptyElement1 . This will also generate a feature - Feature1 3. Delete the Elements.xml file of the EmptyElement1 4. Copy/Paste the InfoPath 2010 form into the EmptyElement1 5. Right click on the added form and click Properties:  - Deployment Type: ElementFile  - Deployment Location> Path: set it to blank 6. Open the generated featu...

SharePoint 2010 put back the "Set Up Groups for this Site" link

The " Set Up Groups for this Site " page has been, for some unknown reason, hidden in SharePoint 2010. The page is still there and it can be accessed here : /_layouts/permsetup.aspx . To make this generally available I created a custom action to add this to the " People and Groups: All Groups " ( /_layouts/groups.aspx ) page, in the Settings dropdown menu: xml version = "1.0" encoding = "utf-8" ?> < Elements xmlns = "http://schemas.microsoft.com/sharepoint/" > < CustomAction Id = "64f25e2b-f9fb-4e37-b848-5949603b03ab" Title = "Set Up Groups for this Site" Description = "Use this page to specify who can access your site. You can create new SharePoint groups or re-use existing SharePoint groups." Location = "Microsoft.SharePoint.GroupsPage" GroupId = "SettingsMenu" Sequence = ...