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

Question

Question

Cloud Workflow pass multivalue token to lookup rule

asked on February 12

I am trying to pass a multivalue token into the lookup rule, but it looks like it is only getting the first value (single line rather than multivalue).

The Where portion of the lookup is supposed to be Where ColumnValue In MultivalueToken.  Is this possible in the current Cloud Workflow?

0 0

Replies

replied on February 13

If I'm understanding this correctly, I don't think you can do what you want directly.

Best I can tell, there is nowhere for the input parameter to be set to multivalue.  Even if it did, the WHERE clause would have to know if it is an "AND" or "OR" for the multivalues (obviously OR is the only one that makes sense... but someone has to code that).  If you know how many multivalue inputs you have, you could just create one for each input:

On your lookup rule activity, you would just add your multivalue field for each Id input and index the token.

You could also set up a workflow like this:

I set up a multivalued "InputValues" and a multivalued "ResultValues".  Then, I just run the query for each InputValue and dump out the result of the query into ResultValues.  I don't think the cloud has a datarow type so if you want multiple columns returned, you would need to manage multiple ResultValue tokens.

Here's the result when I run mine:

0 0
replied on February 13

Thanks @████████ I was not able to make it work, so I had to take another approach.  The biggest concern is the activity limits in Cloud Workflow.

0 0
replied on February 13

What are you trying to do that runs into activity limits?

0 0
replied on February 17

I had not run into the limits while trying to test, but with Cloud, hitting limits is always a concern when developing workflows.  Then you try to use loops, you must look ahead to what is the possible max number of loops your workflow would potentially try to run,  how many activities the loop may add to the instance as it loops, and other potential breaking points.  I do not want to build and deploy a workflow only to have it fail because of not considering the built in limits.

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

Sign in to reply to this post.