KristofferKeen1
Quickbase Staff
Joined 6 years ago
User Profile
User Widgets
Contributions
Re: Looping through field values in Pipeline
Hey Brittany- Figured it out! Even though you could convert the UserList field into a formula text field and use the regex to split that text field. Here's a way to not need that helper field and use the UserList field directly in pipelines. UserList is an array of objects so you need to extract the email attribute from all the objects and then parse that list. This Jinja will extract them to create a single string that you can use in regex: {{ a.user_list | map(attribute="email") | join(";") }} ------------------------------ Kristoffer Keene ------------------------------Re: Looping through field values in Pipeline
Hey Brittany- Looking at your screenshot, the jinja looks correct. So I want to double check: that you grabbed the correct list-user field? there is more than 1 user listed in that field for the record you found do you have the for each loop after this step? ------------------------------ Kristoffer Keene ------------------------------Re: Looping through field values in Pipeline
Oh that makes more sense! I recommend creating a "template days" table with every date listed 1/1/22, 1/2/22, 1/3/22 all the through say ....12/30/2030, 12/31/2030 (Feel free to go farther in time, but at any rate, I would create a quick excel table to list all the dates and import them to your template table) ... From there when your pipeline is triggered, you could search through all the records in between the 2 dates, I believe the Query with Date "is between" includes your two dates Then have the pipeline create a new record for every date that it finds. That's the short of it. However, even more efficient would create a bulk upsert, which is probably what you were originally thinking in this thread. So when all the dates are found in between and added to your bulk upsert, then you commit the upsert/import all of your dates. See screenshot below for a list of your steps: Hope that helps even more :) -Kris ------------------------------ Kristoffer Keene ------------------------------Re: Looping through field values in Pipeline
If it's just a single date in 2 different fields, then I would just have 2 Create Record steps, 1 step for the first field and create a new record in Table A, and another step for the 2nd field and create a new record in Table B. You could also have 2 different pipelines be triggered off the two different fields and then the next step creates a different record based on the respective date fields. However, if you are looking to loop through a concatenated field and say the data is separated via a semi-colon, then 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. Hope that helps, Kris ------------------------------ Kristoffer Keene ------------------------------Re: Looping through field values in Pipeline
Hey Paul, I hope the screenshot below helps direct you better: You could prepare the upsert as step b and have one final import/upsert at the very end of all records found, but in the example above, I showed how to prepare and upsert per split. I think your biggest question is around getting the search step to match the split field, so here's another screenshot setting the search query to match the Regex's group 1 response: Let me know if you have any additional questions :) ------------------------------ Kristoffer Keene ------------------------------Re: Pipelines
There is another way explained in Bree's exchange app "Create X Children": https://www.quickbase.com/exchange/pipelines-create-x-children/4093 and calling the API: https://api.quickbase.com/v1/records. It's also recommended to do some testing in the API Portal (https://developer.quickbase.com/operation/upsert) ------------------------------ Kristoffer Keene ------------------------------Re: Embed a Web Page in a Form
As an update to this thread, earlier this year QB released an easier way to embed links on forms. For URL field types, go to the field settings under "Display" and there is an option to "Embed as iframe in forms." So for example, you could put your iframe embed code in a code page and then call your code page via a formula - URL: https://SUBDOMAIN.quickbase.com/db/DBID?a=dbpage&pageID=4 https://SUBDOMAIN.quickbase.com/db/DBID?a=dbpage&pagename=mypage.html ------------------------------ Kristoffer Keene ------------------------------Re: Looping through field values in Pipeline
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 ------------------------------Re: Looping through field values in Pipeline
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 ------------------------------
