Resource Icons
Latest Highlights
Check Out The Latest in The Qrew
4 MIN READ
Having visibility into what changed, when, and by whom, and being able to restore previous values is essential to every software we use nowadays. This is even more important for maintaining trust, ac...
2 days ago
2 MIN READ
June is heating up with many Qrew events and activities to fill your days with learning new tips while connecting with other builders and admins. This month we’ve got four virtual Qrew Meetups coming...
16 days ago
A Problem That Had Me Pulling My Hair Out
In working on Version 2 of Realm Insights (one of the applications that makes up the Governance Core Apps), which is slated to release June 13, 2...
10 days agoThe Content Feed
Feed
June 2025 Cascading Permissions Qrew Meetup Recap
Hello Qrew! Thank you all who were able to attend yesterday’s special hands-on training Qrew Meetup. Here’s what we discussed: To follow along, we recommended everyone to download the "Empower 2025 – Learn Cascading Permissions" app from the App Exchange before the session. Lauren Molino, Director of Advanced Solutions Services, showed how cascading permissions in Quickbase let you control data access with precision by combining user roles, data relationships, and dynamic rules. She walked through building a scalable permission system—starting with a user table and current user formula field, then cascading permissions through related tables—to handle scenarios like restricting project visibility to employees who’ve signed an NDA for a company. Lauren shared a great tip: using a parameters table to link employees and companies makes it easy to manage complex, dynamic permissions without duplicating roles or filters. A helpful takeaway from the session: Always test your permissions with real user scenarios to ensure employees only see the projects and tasks they’re supposed to—this saves time, reduces errors, and boosts data security. Missed the meeting? Here’s the recording: https://quickbase.zoom.us/rec/share/aJG4TJFrKTuiPV0UwM04RVSIFr4wqPIIOLyO7Q60tDwwc2itVal9BlRwzKV-97Q.nQarFMe5whLtgSgi?startTime=1749657243000 As promised, I did a raffle for all attendees who stayed for at least 15 minutes of the meetup. Here are your Attendee raffle winners: Congrats to Harrison Smith and Mike Freyder!!! I will be reaching out within the next week to send you your $50 dollar gift cards. In July, we are going to have two Qrew Meetups. We will be doing a General Qrew Meetup on Wednesday July 9 th and a Pipelines Qrew Meetup Wednesday the 23 rd with two more Empower encore presentations featuring Nathan Call, Manager of Implementation Services, and Kevin Slider, Team Lead of Implementation Services. Details are available on the events page. Thank you and have a great afternoon!
Report help
Hello! I'm diving into someone else's app, trying to wrap my head around their reporting needs. The previous admin created several "checkbox" fields that are in reality, types of answers to a master field. I need to tally each checkbox and ideally, I'd love to get this all on one report. I theorize the reason they did individual checkboxes vs. one multi-select field is because, in my own experience with multi-select, a report of such won't cleanly count how many times each item was selected, but will report out instances of the specific combination of what was selected. In my example, I'm tallying types of support received, where there are 10 sub-types as check-boxes, so ideally this report shows the exact count of each type of service counted. Please and thank you!Doc Gen Replacing filename error
Leaving this here for you. Ran into a problem where when I printed the Doc, it showed this crazy error. {"message":"Bad Request","description":"This document template has field markers that require a Record ID."} What does that mean? If you look at the two URL's of the Print button below, the second is cut off. var text fileName = "template"; https://api.quickbase.com/v1/docTemplates/1/generate?&tableId=bkp8cwnzs&realm=hardermech.quickbase.com&format=pdf&pageSize=Letter&filename=template&margin=0.25%200.25%200.25%200.25&unit=in&orientation=portrait&recordId=3364 var text fileName = [Override Template Name]; https://api.quickbase.com/v1/docTemplates/1/generate?&tableId=bkp8cwnzs&realm=hardermech.quickbase.com&format=pdf&pageSize=Letter&filename=512604-19254.Oregon.Summit this one is missing all this stuff at the end: "&margin=0.25%200.25%200.25%200.25&unit=in&orientation=portrait&recordId=3364" Here is how I fixed it. I moved the filename variable to the end of the URL. var text url = "https://api.quickbase.com/v1/docTemplates/1/generate?&tableId=" & $tableId & "&realm=" & $qbRealm &"&format=" & $format &"&pageSize=Letter&margin=" & $margin &"&unit=in&orientation=portrait&recordId=" & ToText([Record ID#])&"&filename=" & $fileName; Not sure if this is known or not but leaving it here for future me.
File Name for PDF attachments
I'm creating a reoccurring notification with a PDF attachment. The attached file name is only showing as "document-1". The pdf is created through the document template and I'm able to already save it with a specific file name. How do I change the file when it's sent out as a PDF attachment with the notification?
Document Template Save PDF to field in Record API Pipeline
I have been wracking my head all day on this. I was reading Generate Documents from your records in your app where it says "However, you can also create API calls and use Pipelines, code pages, or custom integrations to generate documents. Each part of the formula represents an API parameter.". I was using Restful "Generate a Document" and was able to make a request: How do I get the output of making a request or basically the document template for this record as a file attachment in the record? I tried using: <qdbapi> <rid>1700</rid> <field fid="22" filename="Model_T.jpg"> Base64 encoded file content</field> Thank you so much!Data Change Logs Just Got Smarter!
Having visibility into what changed, when, and by whom, and being able to restore previous values is essential to every software we use nowadays. This is even more important for maintaining trust, accuracy, and control in your Quickbase apps. That’s why we are rolling out a major upgrade to our Audit Logs and particularly to Data Change Logs - giving admins a more powerful, reliable way to track and recover data changes with (almost) zero setup required. What’s New in a Nutshell All scalar fields are now tracked by default once auditing for an app is enabled - no manual enabling needed Only actual field changes are logged - cleaner, more relevant audit trails App admins can now restore changed and deleted values - right from the app audit log Existing field property repurposed - now controls presence in change logs, not logging behavior See full release notes Let’s unpack the details. Easier Setup: Track All Scalar Fields Automatically Previously, tracking data changes required manually enabling individual fields one by one. Now, all scalar fields (like text, numbers, dates, checkboxes, and more) are automatically audited as soon as auditing for an app is turned on. • Important • Automatic tracking for all data changes has been temporarily disabled. In the meantime, manually enable tracking for specific fields using the Show in data changes checkbox. Learn more on our service page and in the May 2025 release notes. We will be progressively re-enabling all realms through the end of June 2025. Realm admins can enable data change logs for a particular app from the Admin Console Apps page: As soon as data change logs for an app are enabled, we will start tracking any data changes for all scalar fields in the app. The changed data will be stored at a record level. Here’s an example data change log event for a single record (both in app and realm audit logs): Once you click on the “View data changes” link, the following modal is displayed: The pop-up will contain the previous and current values for all fields from the record where data changes have been made. That same information is also available in JSON format in the CSV export, as well as in our Audit REST API. A Smarter Use of a Field Property We’ve also updated the meaning of the Track field property (Table settings ---> Fields ---> Field Properties) Before: This determined whether the field was tracked at all: Now: All scalar fields are always tracked. The repurposed field only controls whether the field is always shown in the record change log, no matter if the field data has been changed or not: If you already have an app where data change logs had been previously enabled, we will automatically start tracking all fields. However, you may want to do a clean-up and uncheck the repurposed checkbox for some fields to avoid them being always unnecessarily present in the change log entries. You should also keep in mind that if you disable data change logs for an app that had tracking for certain fields already enabled, the setting for these fields will persist the next time you enable data change logs for that same app. Restore Changed Data Instantly This one’s a game-changer: App admins can now restore a field’s previous value directly from the app audit logs. This works both for updated and deleted records. Whether it was a bulk update gone wrong or someone changing the wrong record, app admins can recover from data mistakes in seconds - no need to dig through manual backups, contact tech support or manually re-enter data. What you need to do: Locate in the logs the record that you want to restore, click “View data changes” Select the fields you want to restore - all of them or specific ones Click “Restore previous values” Upon a successful restore, you should see a message like this: You can also restore any deleted record as a new record: • Note • Keep in mind that the data restore option is available only in the app audit log. Data change logs are available in the realm logs, but realm admins do not have the ability to restore data. This is intentional, as we would like to keep the restore closer to where the data lives. Designed to Scale Some of you generate millions of audit events every single day. As part of this change, we thoroughly evaluated the platform performance to ensure app experience and audit performance are not impacted. The new changes are not going to affect your app space entitlements – audit is a separate service. We also decided to retain the existing limit of 50 auditable apps per realm. While this may change in the future, we want to better understand your usage patterns, compliance needs, and platform behavior before potentially enabling higher app limits. The Big Picture Data change log updates are part of a broader investment in powerful, scalable audit capabilities. Read our recent blog post for details on other recent audit improvements. Try It Today If you’re already using Audit Logs, these enhancements are live now. Easy setup. Built-in restore. Smarter logs. Less noise.
Add data to Multi-select field
Hi, I want to use names from a text lookup field as the source of a multi-select field. Some lines of the text lookup field have multiple names which are currently separated by ";". On the multi-select field I want to display the individual options on a separate line. Is this possible? This is an example of what I have: Brand (Text lookup field pulled from a separate table) A B; C D; G; H E; F This is what I want: Impacted brand (new multiselect field created) A B C D E F G H I want the user to be able to select multiple brands from the list
Error - Over 100 Multi-select values
To overcome 100 value limitation, I created "Agent" table to capture all drop-down values and used it as reference in Company's Employee field as below. It has approximately 600 values. But when I save the record, I encountered 100 limit error (The field with ID '45' would have more than 100 choices:) I tried switching the Employee's field Input type to From list, cleared values and back to From another field. But it didnt work. Is there an alternate solution for this? Please guide.New Style Forms in Mobile - native Save button keeps user on Add Record form
Has anyone else run into this issue? We created a new style form for desktop and applied it to mobile as well. On desktop, when a user saves a new record by selecting the "Save" option (not Save and new or any of the other available options), they will re-direct as normal. But on mobile, when the user clicks the native save button that follows them down the form, the record saves, a "record saved" message briefly shows at the top of the screen, and then the user remains on the Add Record page with all of the information they just recorded. If you do not notice the message that flashes on and disappears from the screen, it appears as though no action occurred, which naturally makes a User want to click the save button again. This is causing many duplicate records to be created and causing confusion for users as they are unsure with what to do next. We created a work-around by adding a Rich Text field that will complete the save action and redirect the user as intended, but we are unable to completely remove the native save button which lingers. Does anyone know of a fix in the works for this, or even a way to completely hide the native save button from the form?
