Resource Icons
Latest Highlights
Check Out The Latest in The Qrew
Today's installment is brought to us by Quickbase Pipelines Product Manager GeorgiPeev.
In this QrewTip he demonstrates how to use the new AI Actions Channel in a Pipeline to automate repor...
1 day ago
Starting in March, we’re updating when we roll out our monthly major release. Instead of releasing on Sunday morning, we’ll now deploy our major release at 11:00 PM Eastern Time, usually on the secon...
8 days ago
2 MIN READ
Hey Qrew! Osa here from Customer Education.
We're trying something new: QBU Office Hours
Live, 1-hour sessions where you can bring questions and work through course-related stuff directly with ...
1 day agoThe Content Feed
Feed
Custom Rule to Prevent a Role Access to Specific Records
I am trying to create a custom rule for a specific Role that prevents this role the ability to view specific records using the Record ID field. For some reason I can get this to work for one record, but when I add an additional record ID it seems to break. Can anyone tell me why and what I am doing wrong? In the screengrab below, If I only have one Record ID look up (1643) line it works fine. When I add the second Record ID for 1881 this seems to break the rule. Thanks, Brian
Solving Filtered Multi-Selects in Quickbase
One limitation I run into fairly often in Quickbase is filtered multi-selects. Quickbase supports conditional dropdowns on relationship fields, which works well when a user is selecting a single option. The issue comes up when users need to select multiple options and still have those options filtered based on one or more previous selections. Since multi-select fields can’t be filtered, users end up seeing options that don’t apply. I recently built a solution for this and wanted to share the pattern, since it’s reusable across a lot of different scenarios. The Challenge Out of the box: Conditional dropdowns only support single selection Multi-select fields can’t be filtered Users end up seeing options that don’t apply In this case, the requirements were: Users must be able to select multiple options in both steps Only valid options should ever be shown The experience should feel simple and intuitive, not like a workaround The goal wasn’t to force something into a multi-select field — it was to keep the user experience clean while still enforcing valid selections. The Idea (High Level) The approach was to: Break the selection into two steps Let Quickbase build the valid options for the user (for example, using a pipeline) Let users select from only those valid options Rather than asking users to figure out what applies, the sytem does the work for them. Example Use Case Here’s a scenario people can apply this to: Step 1: User selects one or more Vendors Step 2: User selects applicable Services The key requirement: Not all Services apply to all Vendors Users should never see invalid combinations Instead of showing every Service and relying on users to know what applies, Quickbase only presents options that are valid based on what they selected in the first step. User Experience From the user's perpective: The user selects one or more Vendors The user saves/submits their changes The system generates a clean list of only the valid Services The user checks the Services they want This ends up feeling very similar to a filtered multi-select, without exposing irrelevant options to the user. Why This Works Well This pattern: Prevents incorrect selections Keeps the interface clean and focused Is easy for users to understand Scales well as options grow Works for both many-to-many and one-to-many scenarios How Others Can Reuse This This approach works anytime: Selection B depends on Selection A Users need to choose multiple options You want to hide anything that doesn’t apply What you'll need: A clear source of truth for valid combinations A step where the system generates valid options A simple selection step for the user You don’t need the exact same data model - just the same concept. Replace “Vendors” and “Services” with whatever fits your use case. April Barragan | Solutions Consultant Website | LinkedIn | Knowledge BaseIntroducing the Code Page Samples App
Introducing the Code Page Samples App Hello Builders! We are on a constant journey to elevate the level of sophistication that can be achieved in Quickbase. From new aggregate capabilities, Pipelines, a refreshed UI and class-leading governance, Quickbase is a truly no-code tool. But to us, no code doesn’t have to mean “code not allowed”. While we are retiring iCal and vCard fields natively, those features can be achieved with a little bit of JavaScript and our new RESTful APIs. More recently, we announced that we will be changing the way the platform handles custom content (like JavaScript code) that is inserted outside of code pages to put security first. Combining this effort with our roadmap to build extensibility, we both analyzed product usage and spoke with hundreds of builders to understand common use cases and edge case scenarios for extending Quickbase. While we aim to provide as much native functionality as possible, we have a strong set of APIs that allow builders to extend the platform and innovate. Much of this can be achieved client-side, in code pages. To help builders take advantage of these techniques, we have collected examples into a new app, the Quickbase Code Page Samples app! This app is open to everyone on the internet. Use it as a guide to better understand how to take advantage of code pages, and how they can be used to extend the platform, solving for even more use cases. As we continue to listen and learn from you, we’ll update the app to include additional examples. Please note: this app's purpose is to highlight helpful techniques for code pages, and while this overlaps nicely with the need to move away from using inserted JavaScript, the app is not intended to be focused exclusively on that initiative. Over the coming months, we will publish additional blog posts dedicated to each technique. The first one, about Using Code Pages to Refresh with a Delay is available now. These posts will explain how a given technique works, and how it can be applied to your own apps. Keep an eye out for these posts over time. Finally, please remember that these code samples are provided as-is, and are not supported directly by Quickbase. Have a great week, -The Quickbase Product teamNew from QBU: Live Office Hours!
Hey Qrew! Osa here from Customer Education. We're trying something new: QBU Office Hours Live, 1-hour sessions where you can bring questions and work through course-related stuff directly with our team. Think of it like dropping by during office hours in college, except way less intimidating and with better tech. These sessions are built to support what you're learning in QBU courses, like "help me understand why this works" or "I'm stuck on this concept from the lesson." Quick note: Office Hours are focused on course content only. For app-specific troubleshooting or technical issues, your usual Support/CX team is still your best bet. Upcoming sessions January 15, 12–1 PM ET — Customer Education Q&A Come to Customer Education Office hours to get answers and help building a personalized learning path of courses that will accelerate your building. January 23, 12–1 PM ET — Intermediate Topics Relationships, forms, dashboards, reports—all the good stuff for when you're ready to level up. Seats are limited so it stays interactive. You bring the questions, we bring the answers (and probably some coffee). How to prep Bring 1-2 specific questions from a course you're working through (or just finished). If you know which lesson or module you got stuck on, even better - it helps us jump right in. This is a pilot! We're testing this out to see if it's useful for you, so your feedback matters. After you attend, let us know what worked, what didn't, and what you want to see next. I hope to see you there!Monday Qrew Update - Week of January 12th
Happy Monday, Qrew! Here’s what’s coming up—hope you can join us for one (or all) of these sessions this week: 📅 1) App Builder Qrew Meetup — Tuesday, Jan 13 @ 12pm EDT Agenda: Wes McAda shares how he built a real-time amusement ride capacity tracking app. Register: https://quickbase.zoom.us/meeting/register/DoqyWs61RGODggbk_xqs6g 📅 2) Atlanta Qrew Meetup — Thursday, Jan 15 @ 1pm EDT (please confirm time) Agenda: Join the Atlanta Qrew for a FastField spotlight, a fireside chat on what you’re working on, and a brainstorm for February’s agenda plus our next onsite. See you there! Register: https://quickbase.zoom.us/meeting/register/1AOIVeGDQh6ibWalvxNAlA 📅 3) How to Go from App Inheritance to App Ownership — Thursday, Jan 15 @ 1pm EDT Register: https://quickbase.registration.goldcast.io/webinar/f791e78d-5677-430f-90f9-2b21eab2042b?_gl=1*nmh986*_gcl_au*MjU1MDM5NTYyLjE3NjYxNjczMjY.*_ga*NzAzNzY0MzYyLjE3NjU5OTAzNDE.*_ga_YZ6780317K*czE3NjgyMzg1MjkkbzI0JGcxJHQxNzY4MjM4NjQ1JGo1OSRsMCRoMA.. ⚠️ Reminder: Office hours with Sam Trachy are cancelled until Tuesday, January 20th. FastField Office Hours is available M, W, F @ 2pm EDT. Thanks—and let’s have a great week!
Connected Table Refresh
Hello all! I've been scouring the discussions and I just wanted to make sure they're all still accurate since most of them are years old at this point. It seems the Refresh Connected Data button still doesn't show for non Admin level accounts. What is the best way for my Project Manager to force a data refresh? Is it still the webhook api calls? Or has there been a better way developed?QrewTip: AI Actions Pipelines Channel
Today's installment is brought to us by Quickbase Pipelines Product Manager GeorgiPeev. In this QrewTip he demonstrates how to use the new AI Actions Channel in a Pipeline to automate reporting at regular intervals. Want to learn more? Check out the help article on the AI Actions channel. There you'll find example YAML and learn about channel limits. You can also read GeorgiPeev's other posts about the AI Actions channel: Unlock the Power of AI in Your Workflows Document insights with AI Actions summarizing a 10K filing in Pipelines The Power of AI in Your Workflows: Introducing OpenAI Pipelines Channel
January 28th 2026 Qrew Meetup Event
Portland Qrew is meeting Wednesday, January 28th 3PM PST at Harder Mechanical Contractors and also on Teams. This month Lee will bring Pecans and Green Chilis. Then we'll talk about current projects, new changes and challenges and our favorite Quickbase Bug. Anyone can show off work and cheer each other on. We ask attendees to bring Quickbase problems to solve and then work together to provide a solution. Anyone willing to share is welcome to have a problem solved by a team of very nice people who all love helping. Afterwards I suspect we will go out somewhere and welcome recommendations. If you would like to join remotely email jharrison@harder.com directly and he will send you a Teams invitation.Table for activities
I have an excel spreadsheet with name of company and then up to 75 activities from one particular company, then it's price My task is when the user uses a pull down menu to pick the activity the other fields fill in automatically. So if they pick Amigo Parasailing the price auto populates and then there will be another field that would say # of people and then a field that would total # of people by the Cost of the activity. Example amigos (company) and amigos has 65 different activities Para sailing 100.00 Razor 250.00 Scooters 1 hr - 25.00 Scooter 2 hr - 20.00 Aries (Company) Glass bottom boat - 15.00 Double parasail - 100.00 I might have about 50 Vendors with 600 activities in total I first uploaded the spreadsheet into the table but that didn't work. I used dropdown as a field for the activity and vendor - then I am thinking does it all have to be in one field - vendor, activity and cost? But then I would not be able to multiple by number of people. Is the only way to do this is through form rules -I hope not hahaha I appreciate all your suggestions
