Forum Widgets
Recent Discussions
Pipeline Iterate over JSON nested data
I was pulling in JSON data from Ground Control and was having some trouble pulling in some nested data while creating a record. Here is how I solved it. I hope I can save some people time. Used the method posted here to get this started: JSON Handler details Data initially pulled was not an issue at the top level. Nested inside my data is "customFieldValues". Sample: "customFieldValues": [ { "name": "SomeFieldA", "value": "Abcdefg" }, { "name": "SomeFieldB", "value": "1234567" }, { "name": "SomeFieldC", "value": "CwhatIDidThere?" } ] To pull in this value I needed to use a raw_record Jinja expression and state the location in the array. {{b.raw_record['customFieldValues'][0]['value']}} 0 is used since this is the first location in the Array. (This assumes that b. is the reference used for the other fields such as {{b.status}} ) This is placed in the field reference in Create Record step for SomeFieldA. ------------------------------ James Carlos ------------------------------
JSON Fetch > Iterate over JSON Records > Create Records
I'm having issues getting a pipeline to add records for each JSON object. I think it has to do with the JSON schema example in the Iterate over JSON records step, but I've tried a few different options without success. Here's what I'm looking at: Below is an example of the data from a user data call. This has 2 employee objects (or arrays? I'm not sure...) I'd like to create a record for each employee, pulling their email address from the data into a field. When I enter the example below in the JSON Schema Sample and run the pipeline, I get only a record created for employee 1. I've tried altering the JSON schema sample to what's shown below. When I take this approach, I get a record created, but it is completely blank (no email). Any help would be much appreciated! ------------------------------ Addie Brunson ------------------------------Looking for Connection and Collaboration Tool Users for September Qrew Meetup!
Hello Qrew! Anyone using Quickbase to work with people outside your org? Come talk about it at the September 22 nd Qrew meetup! Here’s the list of features that help with connection and collaboration: Emailing non-users – send updates to any email, no login needed Emailing a record – share one record's exact view with someone in a click Public app sharing – open an app to anonymous users, read-only, write-only, or both Secure links – expiring links that let someone view or edit one record without logging in Document generation – auto-build PDFs or Word docs from your data Role-based access – control exactly what outside users can see or touch If you’re using these features, we'd like to hear from you. Please reach out and we can feature you at our next Qrew Meetup. Thank you!
What Quickbase AI prompts are working for you? Let’s build a prompt library together!
At the recent App Builder Qrew meetup, we heard so many great AI prompting tips at our latest Qrew Meetup that I don’t want them to disappear into one recording. Let’s build something together: a Quickbase AI Prompt Library — by users, for users. If you’ve got a prompt that helped you: build something faster clean up data troubleshoot an app create or improve a Pipeline find insights save time or just make Quickbase AI behave a little better Drop it in the comments! Bonus points if you share using this format: 1. The prompt (give some context) 2. What you were trying to do (describe any contraints or guardrails you added) 3. A screenshot/visual of the result (Share the output and the results of it) Let’s make this thread useful, practical, and full of examples people can borrow and reference. The goal is to turn what we collect in the community and turn it into a reference library for all Quickbase users. Thank you for sharing your prompts! Can't wait to see what we gather.
Default setting to open in same page for Reports
Hi, Is there a way for my app settings to automatically default to 'open in the same page' when editing a report? I know how to change the setting within the field itself but not when editing a report record. This ends up with a host of tabs open in my browser vs. staying within the project record itself.
