Resource Icons
Latest Highlights
Check Out The Latest in The Qrew
2 MIN READ
Quickbase Admin Getting Started Guide
If you're new to being a Quickbase admin, start here! While it may feel like there is a ton to learn, the Getting Started Hub has you covered. This is how...
12 days ago
Ready for a chance to win and boost your Quickbase skills?
The App Builder Qrew is hosting a raffle giveaway—simply download Mark Shnier’s app from the Quickbase Exchange and show proof (a sc...
8 days ago
As Empower 2025 comes to a close, the excitement doesn't have to end! April brings a fresh wave of engaging Qrew meet ups and webinars designed to keep you connected and inspired. Check out the event...
20 days agoThe Content Feed
Feed
Need help deciding between two db setups
I am pretty new to qb and am currently trying to create an app to help my department track a student's requested thesis committee. The (hopeful) process: student will submit form with their identifying info, proposed thesis title, then choose their requested thesis supervisor, and selected reader, both fields pull from the same list of faculty (though if someone is chosen in one field they will not appear in list in 2nd field - that's for another time to figure out). So in trying to build something I came up with two different setups and am wondering which people think would be best. Which do you think will be better longterm. Attached are screenshots of both relationship diagrams. Hopefully they are decipherable.
Printing to Dymo Label Printer
Hello all, I just wanted to share how I was able to successfully set up a print button to print using a Dymo label. I have been searching online for a solution and I was being pointed to Trinity and that just wasn't an option with my organization. So below is the steps I took to get what I needed. Step 1 Create a Formula Rich Text field with the address information. Below is the formula I used to get it my address in one field. Everywhere you see brackets, those are my field names. I have Name, Organization, Street Address, Street Address-2, City, State/Region and Postal Code. You will need to change those names in my formula to fit your field names. Also, we have some [Organization] that are very long so we I had to add some adjustments to the font if the character length got to a certain size. My formula is attached in the word document labelled "Step 1 Formula". Step 2 Create a form on that table that specifically displays only the formula rich text field you created above. My field is named Address Label. The only thing you need to put on that form is the Address Label field you created in Step 1. Remember to hide your label on the form to remove the name of the field. The picture attached labeled "Step 2" shows what my form looks like. It won't be much since its only one field with a hidden label. Step 3 Make note of the Form Id number for your new form. Mine is '10'. Step 4 Create a formula URL field on your table to execute the print. My field is labeled "Print". I also made it a button for a cleaner look. The formula I used for my button is attached labeled "Step 4 formula and field settings" Replace Realm Name, TableID, [Record ID#] and IDofTheForm with your information. Realm Name Located in your URL browser. Mine is dekalbcountyga https://dekalbcountyga.quickbase.com/ TableID Located in your URL on the table you are wanting to access just before the /table. In this example, mine is kdubsk9v kdubsk9v/table [Record ID#] This is the key field in your table. The default for every table is [Record ID#], however, if you changed the name of your key field like I did, you will need to put that field name there. IDofTheForm Located in your main Form page. Previously I showed mine was 10 Change the settings in that field to display a button, open in a new window, etc. Image attached labeled "Step 4" is a screenshot of all my settings in this fieldOnce you have that done, the only thing you need to do is in the print settings, after you select your Dymo printer, you will need to change your margins to None. I am in now way a Quickbase pro but I will help anyway I can. Hopefully you all find this useful. :)
Find and append new unique values to secondary table
I have an app where I run a daily upload of data (much of it duplicate due to the nature of the source), but sometimes my daily upload includes a new record that needs to be added to a secondary table within the app. The key field in the secondary table matches one of the fields in my daily upload. I have set up a QB action that should identify new unique values in the field related to the secondary table's key and copy these records. But I am running into a problem. Sometimes my upload will include several rows with the same value in the field that I want to use to populate the secondary table's key field . When this happens, my action is registering an error. I only need the value in one of the duplicate lines to write to the secondary table, but I need to preserve all of the lines in the primary table. Any suggestions?
Script a button to print current record to DYMO
I'm finally moving a product pricing process from EXCEL into QB. The last step is giving a user(s) the ability to print product labels from QB to a local DYMO printer. What I had envisioned was a button on the record form that would take a half dozen or so values in the record and push them as values for the label. Has anyone here done this already? If so, are you willing to share any of your scripting? My JavaScript experience is extremely limited. This link is an example of printing to a DYMO via a JavaScript library, but I don't really understand how to set the values of QB fields as the values to send to the printer. http://developers.dymo.com/2010/06/02/dymo-label-framework-javascript-library-samples-print-a-label/ Any help would be greatly appreciated.Color Code Fields
I have looked everywhere and tried everything I can find but no luck. I want to background color a field if the values are the same. For instance, if a field for "Job 2345" has the number 523 in the ID field and "Job 1234" has the same 523 number in the ID field, color the background so they're identifiable. And hopefully grouped together so all jobs with field ID 523 can have the same crew assigned. Thoughts?April Pipelines Qrew Meet Up Recap & the Agenda for May
Hello Pipelines Qrew! Thanks to everyone who joined our recent Pipelines Qrew meetup on Wednesday! Here's a quick recap what we discussed: Smarter, Faster Pipelines Boryana Atanasova and Georgi Peev reintroduced powerful enhancements to Pipelines that were announced at Empower 2025, including sub-second triggers for small workflows and a new Bulk Trigger (available in beta soon) that processes multiple records sequentially. The Pipelines Product team is rolling out new channels for OpenAI, Bluebeam, Procore, and NetSuite, plus an AI Actions channel and document processing connector to extract structured data from files directly into Quickbase. Real-World Use Case: External API Parsing Savin Kumar from Accenture highlighted how he uses Pipelines to bring in data from multiple external APIs to create interactive reports—all within Quickbase. Tools like Jinja templates and our API docs made it seamless. Some folks were impressed but also intimidated with where to learn JSON and Jinja expressions. I know I am! Often, it’s all about having a space you can test our jinja codes (we recommend using your sandbox, versioning feature, or builder account) and copy/paste to see what works as you build and update your Pipelines. Here are some resources shared from the Qrew that can help: Jinja Pallet Project Intro to JSON vis W3Schools Become a Jinja Ninja – Quickbase Course Missed the meeting? No worries! Here’s the recording: https://quickbase.zoom.us/rec/share/mSGHS4hOjm8Jy7LkPfVbv10a0imdrB8e5Ss0TlIxDlbzZyWHWUH2VakXrO-sQ9Uz.6zCm7BBq38B4Z-f3?startTime=1744818892000 Sign up for the Beta Interested in trying out the new features mentioned in our meeting? Reach out to the product team via email because this will be an invite-only Beta test group. Boryana - batanasova@quickbase.com Stasha - smarkovska@quickbase.com Georgi - gpeev@quickbase.com At our next Pipelines Qrew Meet up on May 14 th 2025, Wes McAda will do an enhanced encore presentation of his Empower 2025 session on using Pipelines on an everyone-on-the-internet App that includes time-bound secure Links with cascading permissions and added security features for temporarily staging documents. And if we have extra time, I’d like to do a working session on using AI to build Pipelines. Thank you and have a good day!April App Builders Qrew Recap and Upcoming Agenda for May
Hello App Builders! Thank you to all who were able to attend Wednesday’s App Builder Qrew Meet Up. Here’s what we discussed: User-Focused Technique for Flexible Data Management Mark Shneir shared a user-focused approach that lets users quickly add child records to a parent, filter and view data in reports, and temporarily link unrelated tables using a “wildcard” user focus table. This technique streamlines data management and enhances the user experience, and it’s one that he uses with clients at least twice a month. Real-World Use Cases Mark also shared examples of how to quickly add team members or order items to projects, matching delivery truck requirements with team member skills, and efficiently associating orphan time records with invoices using his shared techniques. These scenarios demonstrate how it supports complex, multi-user workflows. Learning and Adoption While creating URL formula buttons can be a challenge, resources like an example app and community support make it easier to learn. The User Focus App in the Exchange by Mark Shnier is available for anyone to download and use as a cheat sheet to apply to your apps. You can access the app here or search “User Focus: in the exchange to find it. Missed the meeting? Here’s the link to the recording: https://quickbase.zoom.us/rec/share/wB-J2e9ckJZj1Dr0unLoT3HuTX2xPgskejRsmjMKMgGdI8iT0yseTYs3J3LBJGoM.y_6WRLx4wN7Ze0aq?startTime=1744732008000 App Builder App Download Raffle! As mentioned in our meeting, we are running a raffle for the App Builders Qrew! All you need to do is download Mark’s app from the exchange and go to the discussion post and share your “proof” of download to be entered into the raffle. You may also email me your proof but would love to get everyone to login to the Qrew discussion site to participate. We will keep the raffle open until April 22 nd . Winners will be announced at the next App Builders Qrew Meet Up!!!! May’s App Builder Meet Up Agenda: Our next App Builders Qrew Meet Up will be on Tuesday May 13 th at 12pm EST. Ventsi Tasev from the Product team will be there to share an update on Audit logs and Prashant Maheshwari from Krishna Beads will be sharing his use case on how to automate and stack data with some fun formulas anyone can apply to their reports soon after. Thank you and have a great afternoon.Glossary for New Admins
Table of Contents 1. Roles in your Account 2. People at Quickbase You Interact With 3. Database Terms Used in Quickbase *You can also download these basic database terms here. User Roles in your Quickbase Account Account Admins These are the people at your organization who will have the ability to manage your account’s users, designate other admins and roles, manage security settings and account level permissions, and work with Quickbase on billing changes. There are two types of Account Admins, Full Management and Support level: Full Management – This type of admin has ALL administrative permissions. This includes the ability to control your access rights and any other account-level permission settings as well as make changes to your billing. Tip: We recommend every account have at least 2 Full Management Account Admins at all times. Support Level – This type of admin can manage most aspects of your account, but does not have the ability to make changes to your billing plan or to control administrative access permissions (like the ability to create and control the powers of other admins) Learn more about your account admins and managing users on your account here Realm Admins This role allows someone to manage security settings for a realm, such as password requirements, single sign-on settings, advanced encryption, as well as some other user management settings depending on their plan. They also possess the ability to view all pipelines on your account. This role can be added to an Account Admin or it can be given to users who do not have other admin permissions. Tip: We recommend each account have at least 2 users with the Realm Admin role to provide coverage for vacations, sick times, and transitions. App Admin This person can change the structure of an app, such as updating tables, fields, forms, etc. Each app can have one or more app admins and we often recommend there be at least two app admins so that they can cover for each other. A user can be assigned as admin to one or more apps directly in the app or can be an App Admin by granting them the permission to create new apps on your account directly. End Users This is a term we use to talk about the users at your account who do not have any of the above admin roles. They are the people from your organization you will invite to your apps to use them in their day-to-day work. You can share one or more apps with these users and app admins can create custom roles and permissions for what they can access in each app to match the data and access they need for their work or take advantage of the built-in roles that come in an app by default. Learn more about our built-in roles and working with custom roles here Quickbase Humans You will Interact With Account Executive (AE) Your Account Executive at Quickbase (often referred to as your "AE") serves as your point of contact when you want to talk about your Quickbase account, plan, and billing. They will help you with your renewals and exploring when it is time to expand your usage. You have likely already met them during the sales process but you can also find their contact information in your Admin Console. Customer Success Manager (CSM) Customer Success Managers, or CSMs for short, work with customers to explore how Quickbase can be more effective in their specific circumstances, help with planning and optimizing usage, and understanding the value they are getting from Quickbase. You likely met someone from our customer experience team during your sales process. Note that, post sale, if your account has an assigned CSM, you can find that person's contact information at the bottom of your Admin Console. If your account does not have an assigned CSM, you can always request to speak with one via your AE. Tech Support Engineers Tech Support Engineer are here to help with technical questions on the platform when you find yourself stuck or are running into issues. You can connect with a rep by creating a support case here. Database Terms Used in Quickbase Table A table is a container of similar items or objects and information about each of the items. For example, a table might hold information related to your customers, projects, or equipment. It is like a tab in a spreadsheet. Record A record is a single entry in a table containing information about one item or object. A table in your app is made up of records. It is like a row in a spreadsheet. Field A field holds an individual data value. Using our example above a field might list the Name of your customer, the status of a project, or the serial number of a piece of equipment. Together, a set of fields containing information about one item forms its record. A field is like a column in a spreadsheet. Form A form is a layout of fields used to add, view, or edit one record at a time. Think of it as a digital version of a form you might fill out in your office. A table can have multiple forms that can be customized for specific users and uses with only the fields that are needed for that use. Learn more about creating forms here Report A report allows you to filter the records and fields you would like to view from a table allowing you to focus on specific information. For example, you could show only customers who are currently active, you could show all projects that are in progress, or show all equipment bought in the last year in a report so long as that data is in your record. You can also choose which fields you would like to see for the records being displayed in your report. Learn more about creating reports here Dashboard Dashboards can be created in Quickbase to display data and reports drawn from your apps, helping you to consolidate important data for your users. You can create multiple dashboard tabs and configure each to display just the data and reports you want to show. You can also set up dashboards that are unique to different roles in your app to tailor their experience. Learn more about dashboards here Relationship Relationships are connections between tables that allow the tables to borrow data from each other and support creating connections between your data. For example, a customer table could be related to a contact table so that each customer record could have multiple contacts from that company while a Project table could be related to a Tasks table so that each Project can have a number of tasks related to it with their own fields and data. Relationships allow Quickbase to go beyond what a spreadsheet can do when it comes to having related information and finding data insights on those relationships. Learn more about creating table-to-table relationships here Key Field A key field holds a unique identifier for each record in a table. Quickbase automatically creates the Record ID# key field and populates it with unique values. For some uses of Quickbase you may want to explore implementing your own custom key field
Using pipelines to log the date/time including the seconds of a record change
I have a pipeline that logs when a record was changed in a tracker table. I need the date/time of the change to be accurate to the second. I can't have a pipeline copy the Date Modified of the source record to a Date/Time field in the status change record as we would lose the seconds. I can't use the Date Created of the record created by the pipeline as this and the user's action are offset by a second or two. I need this to be when the user made the change, not when the pipeline created the record. I created a Formula - Date/Time field in the source table that is ToUnixTime([Date Modified]), then the pipeline copies that to a Number field in the status change record. This works, however I'm in search of a more elegant solution than creating a formula field in every table that needs this. Is there a Jinja expression that will give me the ToUnixTime() of Date Modified without having to create a formula field?
