You are viewing limited content. For full access, please sign in.

Question

Question

for each loop - issues with moving documents

asked on May 13, 2021

We are testing with a very simple for-each-loop, new workflow

 

We search for a list of documents, this works as expected then we are wanting to do 2 document moves based on each document in the loop.  We can get the first move to happen, but the second move fails

 

We have tried using the output_entry from move1 to feed move2 - but this is no go - screenshot attached.  We can get move1 to trigger correctly, but any of the move2 steps fail.

 

Any suggestions?

 

 

 

 

2021-05-13_9-03-10.jpg
0 0

Replies

replied on May 13, 2021 Show version history

What error message are you getting? That's going to be important for narrowing down the issue.

Also, how are you identifying the second entry to move? I assume the "Move 1" activity is using the Current Entry of the For Each Entry Loop, but you don't appear to have any activities that would be retrieving the second document entry.

1 0
replied on May 13, 2021

We don't see any "error" per se, just not working.

 

We have tried referencing the move1 output (we expect this is the right one to pick) and the for_each_loop output (we expect this to not work, as the Move1 takes over).

 

For the Move2 - we have also tried the starting entry, thinking that would be the entry in the for-each loop.

 

We have tried all the combinations but in all cases, the move1 works, the move 2 does not.

 

 

 

2021-05-13_13-02-05.jpg
0 0
replied on May 13, 2021

If you pick the Current Entry of the loop or the Move 1 output, then you'd just be moving the same entry twice unless Move 1 is a copy and not a move.

Starting entry does not change automatically, that is something that is set when the workflow is initiated or explicitly set with the "Change Starting Entry" activity.

If you're not seeing any errors or warnings in the message tab of the workflow instance, then that means it is in fact moving the entry, perhaps just not the one you're intending to move.

1 0
replied on May 13, 2021

Can you show us a screenshot of the workflow from the instance details so we can see what path your workflow took?

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.