none
Designer workflow lookup missing columns RRS feed

  • Question

  • Hi there.

    I have already created a workflow used (mainly) to send out email notifications based on a document's status in a library.  Recently I was asked to add another status and corresponding email notification.  However, when I'm using SP Designer and look under "current item" (for the TO: field of the email), I noticed that most of my fields from the document library are now missing.

    Has anyone ever experienced this before and if so, what can I do to fix it?

    Thanks.

    Friday, April 30, 2010 7:47 PM

Answers

  • I have still not been able to figure out why most of my fields disappeared from the "Current Item" source of the "Workflow Lookup" option for selecting a user to receive an email. 

    While I am not doubting that using Visual Studio to create SharePoint workflows is a far more customizable and powerful option than SharePoint Designer, I do not consider it an answer to my original question.

    To anyone looking for a reasonable workaround, here is the best solution I have found.

    1. Select the "Build Dynamic String" action. Click "dynamic string" once added.

    2. Click "Add Lookup" and your fields should all appear under Current Item.  Select your desired field.

    3. Either use the pre-designated variable or type a new one.

    4. Go back to selecting users for your email. In workflow lookup, select workflow data as your source and choose the custom variable you specified in the previous step.

    5. Your workflow will now send an email to the user in the variable.

     

    Hope that helps someone else out in the future.

    • Marked as answer by Alex Moon Friday, June 11, 2010 8:44 PM
    Friday, June 11, 2010 8:44 PM
  • Hi Alex,

    Um, yes, I have.  I ended up going with visual studio workflows and haven't looked back.  I think if you peruse the workflows forum you'll find most of the posts are regarding sharepoint designer workflows which are presumably no-coding, but are actually (my opinion) far more complex.

    Basic steps to get started:

    install visual studio.

    Install the sharepoint sdk.

    read through the help on the sdk....there are walkthroughs for workflows.  there are also tons of blogs and examples for code you many need.  once you've mastered the basics (8-16 hours) you will find yourself copying and pasting your own code.

    Best regards,

    S'

    Monday, May 3, 2010 12:58 AM

All replies

  • Hi Alex,

    Um, yes, I have.  I ended up going with visual studio workflows and haven't looked back.  I think if you peruse the workflows forum you'll find most of the posts are regarding sharepoint designer workflows which are presumably no-coding, but are actually (my opinion) far more complex.

    Basic steps to get started:

    install visual studio.

    Install the sharepoint sdk.

    read through the help on the sdk....there are walkthroughs for workflows.  there are also tons of blogs and examples for code you many need.  once you've mastered the basics (8-16 hours) you will find yourself copying and pasting your own code.

    Best regards,

    S'

    Monday, May 3, 2010 12:58 AM
  • I guess I forgot to mention that we are using WSS3.0 instead of MOSS.  Will that make a difference?  I downloaded the WSS SDK files but wanted to make sure what you are saying will still apply.

    Thanks for the help.

    Monday, May 3, 2010 9:15 PM
  • Hi Alex,

    I beleive so; the visual studio workflows are actually based on the workflow foundation, not moss or wss.

    Best regards,

    S'

    Tuesday, May 4, 2010 2:39 AM
  • I have still not been able to figure out why most of my fields disappeared from the "Current Item" source of the "Workflow Lookup" option for selecting a user to receive an email. 

    While I am not doubting that using Visual Studio to create SharePoint workflows is a far more customizable and powerful option than SharePoint Designer, I do not consider it an answer to my original question.

    To anyone looking for a reasonable workaround, here is the best solution I have found.

    1. Select the "Build Dynamic String" action. Click "dynamic string" once added.

    2. Click "Add Lookup" and your fields should all appear under Current Item.  Select your desired field.

    3. Either use the pre-designated variable or type a new one.

    4. Go back to selecting users for your email. In workflow lookup, select workflow data as your source and choose the custom variable you specified in the previous step.

    5. Your workflow will now send an email to the user in the variable.

     

    Hope that helps someone else out in the future.

    • Marked as answer by Alex Moon Friday, June 11, 2010 8:44 PM
    Friday, June 11, 2010 8:44 PM