​@Jenna Schorer 

You can bulk update attribute values in DocuSign CLM using a simple workflow. First, generate a report containing the document IDs and download it as a CSV file. Then, add a new column to this CSV with the updated attribute values. The workflow will use the document IDs to locate and update the corresponding documents in DocuSign CLM.

Michael, thank you so much!  I had been playing around trying to figure out a good Workflow to do this.  This looks like it will perfectly solve the issue I have.

Can you let me know what parameters you selected for Decision and timer trigger?

I am new to Docusign so please help me out!

Hi, I swapped the Decision out for a Rule instead.  It’s set to wait every 500 rows.  And I set the timer to wait for 10 seconds.

Another question about this one if anyone has an idea.  I have been trying to get this to work for weeks now and nothing gets it past the Find Document step.  The Update Variable step right before it IS correctly putting in the Document ID into the variable, but when I use that variable in the Find Document step, it keeps failing.  Any ideas where I’m going wrong?

Hi ​@Jenna Schorer - If you search for the document Id separately, using just CLM Search, do you return any results that way? I’m wondering if the list of IDs was from another account, maybe UAT? If so, the list of Ids will now be different if you are running the same workflow in production. 

Hi Kelly, yes if I search just the Document ID, it pulls it up in the search.  I got the list of files in the csv from a report in Production, so we’re good there.  

If you can export your workflow and attach it here as a new message, I can try later today to see if I can figure out the root cause. Or if you want to try and message it to me directly, feel free!

Hi Kelly, here is the json.  -Jenna

Interesting! When I set up the workflow in my own account and a run a small sample file, I’m able to get the “Find Document” step to work successfully for every Id in my CSV. One thought you could do is build a failure path from the “Find Document” step which routes back up to the For Each Loop step. That way you can see if it fails on every ID or just a few. 

I don’t think this is the issue but one minor thing I see is the vStepCounter variable in the Update Variable Value 2 step should be incrementing by (roughly) the number of steps being processed in each loop, not set to a static 0. To do that, change vStepCounter to a Number type (right now it’s text). Using the expression builder, set the value of vStepCounter to: Convert.ToInt32(GetVariableValue("vStepCounter")) + 5.

Thanks Kelly!  So, to make it slimmer I removed the timer section altogether and I am just doing these in smaller batches to compensate.  After that and a couple of other tweaks mentioned above, the workflow now works, but only for the first row of the csv file.  No matter what I do, it won’t continue the loop to subsequent rows.  I even added a step for “Next Loop” and tied it back to the “For-Each Loop” step, but no go.  I have double-checked the csv file and it does not contain any hidden spaces or lines and no extra commas at the end of lines when checking via a word editor.  I have double-checked the variables and everything looks right, including when I check the iterator variable.  I’m at a loss as to how to move it along the list.