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

Discussion

Discussion

Struggling because Cloud Uses For Each Value Instead of For Each Row for Forms Table Data

posted on December 31, 2024

I am struggling to iterate through a table of data from forms and do different actions based on different columns in the table. In On Prem interacting with a table from forms was done through the For Each Row activity and would present tokens for each column in the dataset regardless of what column you chose to iterate on.

In Cloud we can only use the For Each Value activity which does not allow visibility to the other columns in the table when iterating. We can only use the Current Value.

For this use case, I am trying to recreate a simple Table Maintenance form we have used frequently in On Prem. Let's say it is the list of approvers with approverDisplay, approverUser, approverID (key) and a checkbox to indicate the approver row should be deleted.

We then in WF just iterate through all of the rows and evaluate in a conditional branch whether the row indicates it should delete, add or update the data in the approver table. If the delete checkbox is checked we delete. If the key is empty we add. Otherwise we just update. I cannot get this to work in Cloud.

 

I've tried both passing the table data as input parameters AND writing the data to a temp table then reading from the table, but either way I cannot evaluate the entire row of data and then write it to a table.

0 0
replied on January 2

This post needs deleted. I am now able to see the Run Rule activity under the For Each Row activity. Not sure why I couldn't see it originally.

0 0
replied on January 2

Ok well I don't know why For Each Row wouldn't see the Run Rule activity when I was trying it, but it certainly sees it today. So this post is irrelevant. I can't delete it because it has been replied to but I certainly would like to just delete it lol.

replied on January 1

Hi Lexie!

In my example, I am inserting my data into a data management table VIA a form. If it's a new submission (no id) returned VIA a lookup it's an Add, if it has an id then it is an Update and if delete is checked it goes down the delete branch.

Use the for each row instead of the for each value.

I hope that helps!

You are not allowed to follow up in this post.

Sign in to reply to this post.