Return to Question

In SP2010, this workflow is triggered when I create or edit an item in a list.

If Current Item:ID equals (other list):ID
    Set Comments to Blah
Else
    Set Comments to Humbug

I'm sure that's not the right way to check if another list contains the same ID as the one I just created/edited, but my third test case had an empty string in Comments.

Test case 1: create, other list has no elements -->

• returned Humbug (expected Humbug)
  Test case 2: create, other list has same number of elements -->
• returned Humbug (expected Humbug)
  Test case 3: create, other list has one more element than triggering list -->
• returned empty string...

I would have expected Humbug, because the workflow terminated without encountering any errors. My other test cases returned an expected value of Humbug.

In SP2010, this workflow is triggered when I create or edit an item in a list.

If Current Item:ID equals (other list):ID
    Set Comments to Blah
Else
    Set Comments to Humbug

I'm sure that's not the right way to check if another list contains the same ID as the one I just created/edited, but my third test case had an empty string in Comments.

Test case 1: create, other list has no elements -->

• returned Humbug (expected Humbug)
  Test case 2: create, other list has same number of elements -->
• returned Humbug (expected Humbug)
  **Test case 3: create, other list has one more element than triggering list -->
• returned empty string**

My question is, how is this possible? If the workflow completed with no errors (which the workflow settings page seems to indicate since it does not have any workflows in progress and workflows halt on error), how is Comments still empty? Either 'Blah' or 'Humbug' should have been printed to the Comments column.

In SP2010, this workflow is triggered when I create or edit an item in a list.

If Current Item:ID equals (other list):ID
    Set Comments to Blah
Else
    Set Comments to Humbug

I'm guessing that's not the right way to check if another list contains the same ID as the one I just created/edited and get 'Blah' printed, but my third test case had an empty string in Comments.

Test case 1: create, other list has no elements -->

• returned Humbug (expected Humbug)
  Test case 2: create, other list has same number of elements -->
• returned Humbug (expected Humbug)
  Test case 3: create, other list has one more element than triggering list -->
• returned empty string...

I would have expected Humbug, because the workflow terminated without encountering any errors. My other test cases returned an expected value of Humbug.

In SP2010, this workflow is triggered when I create or edit an item in a list.

If Current Item:ID equals (other list):ID
    Set Comments to Blah
Else
    Set Comments to Humbug

I'm sure that's not the right way to check if another list contains the same ID as the one I just created/edited, but my third test case had an empty string in Comments.

Test case 1: create, other list has no elements -->

• returned Humbug (expected Humbug)
  Test case 2: create, other list has same number of elements -->
• returned Humbug (expected Humbug)
  Test case 3: create, other list has one more element than triggering list -->
• returned empty string...

I would have expected Humbug, because the workflow terminated without encountering any errors. My other test cases returned an expected value of Humbug.

SP2010 This workflow is triggered when I create or edit an item in a list.

If Current Item:ID equals (other list):ID
    Set Comments to Blah
Else
    Set Comments to Humbug

I'm guessing that's not the right way to check if another list contains the same ID as the one I just created/edited and get 'Blah' printed, but my third test case had an empty string in Comments.

Test case 1: create, other list has no elements --> returned Humbug (expected Humbug) Test case 2: create, other list has same number of elements --> returned Humbug (expected Humbug) Test case 3: create, other list has one more element than triggering list --> returned empty string...

I would have expected Humbug, because the workflow terminated without encountering any errors. My other test cases returned an expected value of Humbug.

In SP2010, this workflow is triggered when I create or edit an item in a list.

If Current Item:ID equals (other list):ID
    Set Comments to Blah
Else
    Set Comments to Humbug

I'm guessing that's not the right way to check if another list contains the same ID as the one I just created/edited and get 'Blah' printed, but my third test case had an empty string in Comments.

Test case 1: create, other list has no elements -->

• returned Humbug (expected Humbug)
  Test case 2: create, other list has same number of elements -->
• returned Humbug (expected Humbug)
  Test case 3: create, other list has one more element than triggering list -->
• returned empty string...

I would have expected Humbug, because the workflow terminated without encountering any errors. My other test cases returned an expected value of Humbug.