Qrew Groups
Connect with others from your area, or who share the same role, professional interest. Find your Qrew here!
Links Banner
Main Content
Recent Content
Open Notifications Stopped Working this Month (7/2025)
Hi all! I've had an app built for years that houses my internship program data. It sends out an open notification to internship supervisors to evaluate our students' performance near the end of their internship. The notification contains a link that takes them into the app to complete a form which pulls goal data from the student's workplan to be evaluated on. It last worked properly (was completed by a supervisor) on 7/6). This week, particularly the last 2 days, my team started getting emails saying the link shows them the form for about a second, gives an error code, and takes them to a log in page. Supervisors have never needed to log in before. Just click the link and they access the form. I'm not super savvy at Quickbase - any ideas on what happened/broke?
A solution to un-pivot table data
If this topic has been discussed and there are well known solutions to this topic - I apologize. I didn't come across any before I came up with the solution below. Background: I was working on a request from my team to build out some functionality that required a lot of check boxes. I didn't want to take a lot of time building a custom form to ensure that the checkbox data was stored with a row for each box. There are 28 checkboxes representing various issues (oil leak, lights, forklift forks, etc). While not totally necessary, I did hope I could somehow un-pivot these columns into a table where only issues that were checked had a record. TLDR; Using fetch JSON and the Quickbase API, you're creating a list of field ids that you want to unpivot and then for each record in a second set of JSON data, you are looping through that field list and creating a new single record in a 2nd table with the values you are unpivoting as well as any other data you wish to repeat in each new row. This process leaves the original table completely intact. Solution: API Urls You'll need two API request urls. One request for the field information for the table that has the information you wish to un-pivot (eg, field id, field label, etc) One request to a report that has the data you'll need for the records in the new table. (eg. values in fields, checkbox data, etc) Don't forget to include columns that contain foreign key data you'll use in the new table If you know how to create/build those URLs, skip ahead to step 9 To build/learn about how to build the API URLs, go to developer.quickbase.com On the left side of your window you'll see a list of different topics related to the Quickbase API. Select the arrow next to the 'Fields' label. Then, click on the first item on the list "Get fields for a table" From here, you can enter the table id of the table you want to un-pivot, and fill out the other information related to realm, authorization, etc. I suggest also testing it and seeing the data that comes through. Copy the url produced in the top right corner. This is your field data URL. Back on the list on the left, click on 'Run a report', and then repeat steps 6-7 to get the record data URL. Pipeline | Fields Data Create a new pipeline and add a 'Fetch JSON' step. Populate the fetch JSON step with the field data url and required headers. This step is a GET step. Following that step, create a 'Iterate over JSON' step The step should automatically select the prior step, but in case it didn't, in the 'JSON Source' field, select the previous step as the source. In this step, it is helpful to have a sample of the JSON schema so you can reference some of the items in the next step. So include a sample data dump from the developer.quickbase.com API website. This makes references to specific field data much simpler In the 'Iterate over JSON' step, go to the bottom and filter the field list to ONLY include the fields you want to unpivot. In my case this was simple as all of my fields were checkboxes, so I just chose the 'Field Type' field as my filter, and conditioned it on "checkbox". If you aren't as fortunate as me, and you don't use the 'Field Help' field for your applications - you could use the 'Field Help' field as your filter by populating each field that you wish to un-pivot with the text 'unpivot', and then filter on the 'Field Help' This is absolutely vital to the process. If you can't get the field list down to exactly what you want you'll get unwanted rows. Pipeline | Record Data The 'Iterate over JSON' step from above will have created a 'loop' step. IN BETWEEEN the 'Iterate over JSON' step and its corresponding loop, repeat the steps 1 - 4 from the Pipeline | Fields Data section for the Record Data url A second loop will have been created as part of this new 'Iterate over JSON' step Move the Field Data Loop (from the 1st part) INTO the new loop you just created. The field data, i.e. the information that has field ids, field labels, etc. should be nested INSIDE the loop that has the table data, i.e. the records that have the actual information you want to un-pivot. Testing for Field Data In the nested loop (the field data loop), create a 'condition' step. In the drop down field where you select the field to evaluate, go to the bottom of the list and choose "Expression (advanced)". In the dropdown to the right, you can leave it as "evaluates to True" In the criteria field below the two dropdowns, include the following jinja {{d.raw_record[(b.id|string)]['value']}} To explain, what we're doing here is taking the table data we downloaded (d.raw_record), and using the current field id (b.id) of our loop to grab the data ['value'] for just that specific field. In my case, the value was either going to be 'true' or 'false' because it was a checkbox. You may need to adjust the logic to test if the field has data or not. If you don't test for this, you'll get empty rows of data. Creating a Record If you haven't already, create the table where the data is going to go. In the pipeline, in the 'If condition is met' branch, add a 'Create Record' step Choose the table you created Add all the fields from that new table that you are going to populate with data from the un-pivot. For each of the fields in the NEW table that you'll use to group on, use jinja to select the fields that will fill each of the new fields. I've included the jinja I used to populate the fields that get the same data for every record. This was the record id of the report that has all the checkbox issues {{(d.raw_record['3']['value'])|int}} Below was the date of the report which I wanted to include in each new record {{time.parse(d.raw_record['6']['value'])|date_mdy}} For the field that contains the value that you want to un-pivot, you use the same jinja statement you used in the condition section to check on valid data. {{d.raw_record[(b.id|string)]['value']}} Cross your fingers, say a few prayers, call your mother and then hit run on the pipeline.Client Portal With Userids
Are there any tips out there of how to let a user sign in without the Quickbase branding screen. I have a situation where customers will be logging into a supplier Quickbase app, with proper userids. But we want to suppress all the Quickbase branding on that page. ------------------------------ Mark Shnier (YQC) Quick Base Solution Provider Your Quick Base Coach http://QuickBaseCoach.com mark.shnier@gmail.com ------------------------------
Could not parse XML input
Hi, I'm getting errors on my pipelines for a multi-line field. Quickbase reported an error: 11 : Could not parse XML input : XML Parsing Error. not well-formed (invalid token) at line 3 column 353 (which is byte 700) When I look through the activity log and the original db i'm seeing these characters: †and “. When I talked with the users they said they did not put them in the field. After a little research it looks like it was a copy and paste issue. My question is how can i prevent this from being sent through the pipeline? Thank you
Button to go to related record in a different table
Hi, I have 2 tables, I would like to add a button in the form from the Accounts table that takes me directly to the related record in the Findings table. Both tables have the same Account ID field so I have created a table to table relationship between the two. I'm assuming I can achieve this with a url field with a formula that some how finds the related record in the Findings table by matching the account ID# but I have no idea what that formula would be. Please help Thanks
Matching Fonts on Templates using Rich Text and Standard text
Hi, I'm very new to the quickbase world and trying to manage an app that was built for my agency. My question is about changing the font that prints from a form in Rich Text. We have several forms that use templates to print out and when there are both rich text fields and standard text fields used, the rich text fields default is different than the standard text in both size and font. This obviously looks terrible but I can't find a way to adjust it. I have read several articles and conversations about using rich text with HTML tags, but I can't find a way to actually adjust the font (I think prior to 2023 the options in Rich Text fields, were well richer). Can someone offer a suggestion. BTW, I am not a programmer so I need basic instructions on where to find things and how to adjust them. HELP! And TIA - HayleyFYI: No Qrew Meetup Today! Next one is Wednesday 7/9/25
Hi Folks! A friendly reminder that there is not App Builders Qrew Meetup today. Our next Qrew Meetup is tomorrow Wednesday July 9th at 12pm est. General Qrew Meet Up: From Good to Great – Unlocking the Power of Reports (July 9, 12–1 PM EDT) Join Nathan Call as he shares pro tips on turning basic app data into visually engaging reports that drive smarter business decisions. Perfect for anyone looking to level up their reporting game. Here's the link to join our session tomorrow: https://quickbase.zoom.us/meeting/register/JW5Luqc_Ruqn3b7u0Hvdbw Thanks and we'll see you there!The magic of Service Accounts
We’re so glad you’re here! Today, let’s learn about Service Accounts and how they can help teams with multiple Realm Administrators or Builders working on integrations. Service Accounts are special admin accounts that let apps connect to Quickbase and use its data without needing a specific person to log in. This is super helpful when multiple people on a team are working together on integrations because it makes it easier to see who’s doing what and simplifies collaboration. Here’s why Service Accounts are important for your team: Transparency: They give a clear view of how and when data moves in and out of your apps, so everyone knows what’s happening. Security: They help keep things secure by allowing automated tasks without sharing personal login details. Continuity: They ensure processes aren’t reliant on any one individual. This helps avoid disruption. Even if someone leaves the team, everything continues running smoothly. For step-by-step instructions on setting up Service Accounts, check out our help article: Setting up Service Accounts. Feel free to ask questions or share your experiences with Service Accounts below…and happy building!
