Looping through field values in Pipeline
I have a record that contains a text field with multiple values separated by commas (which I can also turn into a multi select field if that makes things easier). I want to loop through the values...
Forum Discussion
You can use the Text channel to "Find All Matches to a Regex", and use the following Regex: ([^;]+) if you go with the multi-select option which separates values using a semi-colon. Otherwise, you can change the semi-colon to a comma in the middle of the regular expression, since the comma is the delimiter in your use case: ([^,]+)
Then For each "match/Regex filtered group" (because it's split by a semi-colon or a comma in your case), you can then use each group to create a new record.
So in the subsequent create record step, map the regex step's Group 1 to the new table: {{b.group_1}}
See screenshots below for reference.
Enjoy!
------------------------------
Kristoffer Keene
------------------------------
Then For each "match/Regex filtered group" (because it's split by a semi-colon or a comma in your case), you can then use each group to create a new record.
So in the subsequent create record step, map the regex step's Group 1 to the new table: {{b.group_1}}
See screenshots below for reference.
Enjoy!
------------------------------
Kristoffer Keene
------------------------------
Kristoffer- Many thanks for your reply. A follow up question to see if I am understanding this method correctly:
Does this method require there be the same # of items in the list of values everytime? In my situation I will have records where the multi-value field has different #s of values (E.g. record 1 might have 1 value in that field, record 2 might have 2 values in that field, etc). So in each case I need to make sure the loop in pipelines can be dynamic based on the # of values in that field.
I think what was throwing me off is the 'Group_1' notation and I'm just not familiar with the Regex step. Does the regex step provide this 'dynamic' capability? Or does 'Group_1' mean the first value in the group? and subsequently there would be a 'Group_2', etc if the field had multiple values? which would seem to imply it doesnt provide that dynamic capability.
Apologies if I am not following correctly. Thanks.
------------------------------
Jennason Quick Base Admin
------------------------------
Does this method require there be the same # of items in the list of values everytime? In my situation I will have records where the multi-value field has different #s of values (E.g. record 1 might have 1 value in that field, record 2 might have 2 values in that field, etc). So in each case I need to make sure the loop in pipelines can be dynamic based on the # of values in that field.
I think what was throwing me off is the 'Group_1' notation and I'm just not familiar with the Regex step. Does the regex step provide this 'dynamic' capability? Or does 'Group_1' mean the first value in the group? and subsequently there would be a 'Group_2', etc if the field had multiple values? which would seem to imply it doesnt provide that dynamic capability.
Apologies if I am not following correctly. Thanks.
------------------------------
Jennason Quick Base Admin
------------------------------
- You are correct that regex group will be dynamic, meaning if there are 3 values split by a comma (value1, value2, value3) then three records will be created. If the next time there are 5 (value1, value2, value3, value4, value5) then five records will be created. Group means for each match found in the regular expression (in your case a new group for every comma)
------------------------------
Kristoffer Keene
------------------------------