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

Question

Question

Sending SQL Lookup Results to a Forms Table

asked on June 17, 2021

Hello,

I am trying to pull some rows out of SQL using Workflow and then send them back to a Forms table. The SQL lookup results would be multiple rows to be sent back to Forms in the table as multiple rows.

For some reason it is not inserting all of the SQL rows into the Forms table.

Here are the SQL Lookup results from Workflow:

Here is what the Workflow is doing:

But my results in the Form look like this:

Here are the token in the Workflow Instance as well:

But if I look at the tokens for the Query SQL activity, it shows it found the other result but yet did not send it to the form"

It should have sent all 3 rows as shown in the SQL results above and I am having a hard time determining why my results show duplicated EBS rows instead.

1 0

Answer

SELECTED ANSWER
replied on July 14, 2021 Show version history

I just wanted to follow up on this - after troubleshooting some issues with another part of this process I realized this was not working correctly all the time. I then realized the reason it appeared to be working correctly was because the Form was saving my old values in the table from my submission so when I would send back to Forms it appeared everything was sent correctly.

There was just one small missing piece in the above - you still need to use a For Each Row activity to update a multi-value token in Workflow and then send the multi-value token back to forms. The workflow will look something like this:

Hopes this helps anyone else who may get stuck on this.

1 0

Replies

replied on June 17, 2021

Rows in a table in Forms will be treated as a multi-value token in Workflow.

Try moving the "Set Business Process Variables" activity outside of the "For Each Row" loop - and then send the query results tokens to the fields instead of the "For Each Row..." versions of those tokens.

3 0
replied on June 17, 2021

Matthew - THANK YOU! This worked perfectly.

1 0
replied on June 17, 2021

Fantastic!

0 0
SELECTED ANSWER
replied on July 14, 2021 Show version history

I just wanted to follow up on this - after troubleshooting some issues with another part of this process I realized this was not working correctly all the time. I then realized the reason it appeared to be working correctly was because the Form was saving my old values in the table from my submission so when I would send back to Forms it appeared everything was sent correctly.

There was just one small missing piece in the above - you still need to use a For Each Row activity to update a multi-value token in Workflow and then send the multi-value token back to forms. The workflow will look something like this:

Hopes this helps anyone else who may get stuck on this.

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

Sign in to reply to this post.