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

Question

Question

WF For Each Entry Creates Unneeded "1" and "2" Folders

Workflow Version 10
Updated March 11, 2020
asked on March 11, 2020 • Show version history

I am attempting to create a workflow that copies the entry into a folder within the same parent for each entry that is made into a specific multi-entry field. Template below: 

 

I did the "For Each Entry" tool in the workflow: 

But now, a folder is created outside of the "legal" folder that houses all of these records and the record is copied into the 1 or 2 folder AS WELL AS in the subsidiary folders that correspond with the entries created in the template. 

 

 

How do I make the 1&2 folders stop auto creating? 

0 0

Answer

SELECTED ANSWER
replied on March 11, 2020

Good catch! I was so not looking at the 2nd move. I deleted it and that fixed the problem. 

Now.... It isn't renaming the second, third, ect documents that are "copied" into the additional folders created from the multiple entries. 

Any ideas?? 

0 0

Replies

replied on March 11, 2020

Can you verify that the two "Move Entry" activities aren't making the extra folders? Otherwise, I'd start to suspect that you have another workflow that is triggering on these documents.

0 0
View 3 previous replies
SELECTED ANSWER
replied on March 11, 2020

Good catch! I was so not looking at the 2nd move. I deleted it and that fixed the problem. 

Now.... It isn't renaming the second, third, ect documents that are "copied" into the additional folders created from the multiple entries. 

Any ideas?? 

0 0
replied on March 11, 2020

Do you know why the Parallel activity is being used? For this sort of thing, I'd generally just have a Move followed by a Rename.

0 0
replied on March 11, 2020

That's what I changed it to after your first reply and changed the path to "iteration" instead of "current value" I just need to figure out how to have it name the iteration folder according to the field entry instead of naming it 1,2,3, ect. 

0 0
replied on March 11, 2020

I figured it out!!! YAYAYAYAY!!! 

0 0
replied on March 11, 2020

Oh good! I was just typing this up... Now I'm curious to see how you did it.

 

"Iteration" is just that, a count of how many times the loop has run. You want your path to include the specific field value of the current state of the loop body.

Here's what I did to accomplish that:

Iterate over any one of the fields in the multivalue group. It doesn't matter, since we just want to run it for each one.

Use the Iteration as an index to grab a specific group of fields out of the multivalue field.

0 0
replied on March 11, 2020

Good to know!! I will be putting this in my info bank for future use. I just changed it to current value and then added a delete entry to the end of the workflow because it was leaving a copy of the entry in the beginning entry folder. Trial and error!! lol

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

Sign in to reply to this post.

Details
Related Posts
Loading ...