Resource Icons
Latest Highlights
Check Out The Latest in The Qrew
3 MIN READ
Can you believe that Quickbase has been hosting Empower since 2015?!
Much has changed since then (even how we spell "Quickbase") but Empower is still Empower: the best place to conn...
6 days ago
Hey Qrew 👋
Ben here. And if you’ve been anywhere near Quickbase today, you’ve probably felt it. Something big just dropped.
Yep… Pave is here.
Now, I’ve read all the announcements, sat in o...
2 days ago
2 MIN READ
Learn about the most recent updates to Quickbase, right here:
Highlights include:
AI Announcments
QBAI does the work for you: - Analyzes your data - Gener...
17 days agoThe Content Feed
Feed
Boston Qrew is headed to Houston Empower26, and we’re bringing serious energy with us
We’ve got more than a dozen members making the trip this year, which says a lot about the momentum building in our community. Boston has always been a city of builders, problem-solvers, and people who know how to turn ideas into action, and that spirit shows up every time our Qrew gets together. Empower is one of the best chances all year to connect with other innovators, swap ideas, learn from real-world success stories, and come back with fresh ways to create impact. For our group, it’s also a chance to represent the Boston community, strengthen relationships, and meet fellow Quickbase users from across the country. What makes this especially exciting is that our Qrew continues to grow. New faces, returning members, different industries, different perspectives, all united by a shared drive to improve how work gets done. Seeing so many people investing their time to attend speaks volumes about the value of this community. Houston, get ready for a little Boston flavor. If you see our crew around Empower, come say hello, share what you’re building, and connect with us. We’re excited to learn, collaborate, and bring new ideas back home. Boston Qrew is showing up strong, and we’re just getting started.From A to Z: Why Pave Feels Like a Big Deal (and What It Means for the Qrew)
Hey Qrew 👋 Ben here. And if you’ve been anywhere near Quickbase today, you’ve probably felt it. Something big just dropped. Yep… Pave is here. Now, I’ve read all the announcements, sat in on the conversations, and I know there’s some buzz across our passionate community, so I want to break this down the way we do best here in the Qrew: 👉 What is Pave 👉 Why Pave matters 👉 Why The Qrew should care So… what is Pave? Let’s skip all the fancy buzzwords for a second. At its core, Pave is a full-stack AI app builder, but not the kind that gets you halfway there and leaves you duct-taping tools together at 2am. This is the difference: A lot of platforms get you from idea to prototype Pave gets you from idea to real, scalable, production-ready app We’re talking: Built-in structure Governance baked in (hello, Quickbase governance, how do you do?) Ready for actual business use, not just demos that wow your boss for five minutes Or put another way… This isn’t just “look what I built.” Plenty of tools out there for that. This is “look what my business is now running on.” That’s happening with Pave. Why this hits different If you’ve been in the Qrew for a while, you already know this pain: “I built something awesome, but now I need access to five other tools and a small miracle to make it usable at scale.” Pave changes that. No more: Stitching together third-party tools Managing separate infrastructure Wrestling with “okay but how do we actually deploy this?” Instead, it’s all in one place, built on what Quickbase has been doing for decades: 👉 Secure 👉 Scalable 👉 Built for real operations The part I’m most excited about This is where it gets very Qrew. Pave is designed for the people closest to the work: The ops leader fixing broken processes The builder who sees inefficiencies everywhere The team member who says, “there has to be a better way” Sound familiar? 😏Yup, that’s you. That’s how you found us in The Qrew. What Pave does is shorten the distance between idea and impact. Less: “Let me submit a request and wait…” More: “I built it. It works. We’re using it.” Bridging the gap (desk to field) Another big unlock: Pave is built to connect desk and deskless workers. If you’ve ever tried to: Get field data back into systems Align ops teams with what is actually happening on the ground Build tools that work for both sides …you know how messy that gets. Pave is aiming straight at that problem. Built by the same people who power Quickbase One thing worth repeating: This did not come out of nowhere. Pave is built on: Decades of Quickbase innovation Deep understanding of how real businesses operate And a ton of work from teams across the company So yeah, big moment, and a lot of people behind it. Still the Quickbase you know and trust Let’s address the question a lot of you are probably already thinking: “What does this mean for the Quickbase platform I use today?” Short answer. It is not going anywhere. Quickbase is staying deeply committed to its core platform. The apps, workflows, and systems you have built are still the foundation of everything. That investment continues. Pave is not a replacement. It is an expansion. Think of it as building on top of everything that already makes Quickbase powerful: The reliability you depend on The scale your business requires The flexibility you use every day If anything, this is about doubling down on helping you do more, not starting over. What this means for the Qrew This is probably what I’m most looking forward to out of all this noise. I’m already thinking about: What you all are going to build first The workflows you’ve been wanting to fix The “I hacked this together but…” projects that can now level up And you know what’s coming next… 👉 Demos 👉 Pave specific conversations 👉 Meetups where we swap ideas and show off what we’ve built I can be a little selfish here, no? A Pave Community, anyone? We will make this happen. Go check it out 👀 If you have not yet, take a look at Pave here: Then come back and tell us: 👉 What would you build first? 👉 What problem would you finally solve? Because if there is one thing I know about this community… You are not going to start at A or B. You are going straight to Z. Big day, Qrew....biiiiiiig day. Get fired up for Pave! -Ben
QB Dynamic Filters not working in Summary Report.
I have a summary report which when I add dynamic filters to the report and filter like with status. The report goes blank then refreshes and display the data without filtering but on top the filter is still selected. I don't know if there's something the QB Engineering team is working on but I've tried on different reports and the menace is still the same. I am a cooked potato today please help if you ever had the same issue. Thanks in advance.
Pipeline Not Updating
I have a pipeline that says it's updating a record but it's not. I have an identical pipeline that is working. It take a file attachment uploads it to Sharepoint and then updates the quickbase record with the link to the sharepoint attachment. I have two on the same quickbase but different tables. The first one I created works fine and the second one says it works and it does except for updating the quickbase record with the sharepoint link. How can I tell where it is failing? CarolCode Pages are wild!
Hey everyone! Not sure if you all have spent much time playing around with the capabilities of code pages, but Kojo and I wanted to just say... there are some incredible things you can do in there. Especially when you leverage AI tools like claude / codex... A full customer-facing website — We just completely moved our customer-facing website (EOTI) into a code page. Yes, a real website, living inside Quickbase. A flappy bird style game — We also built a game with a live leaderboard (we'll be doing a full on competition at empower!) Something free coming to the Exchange — We have something really exciting in the works that we can't wait to share. It'll be free, and it's the kind of tool that could genuinely benefit anyone's realms! Feel free to reach out anytime! — Cam
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. :)April 2026 Pipelines Qrew Meetup Recap
Hi Pipelines Qrew! Thank you all who were able to join the Pipelines Qrew meetup On Wednesday. Wes McAda shared three use cases for using Pipelines and Jinja for Project Expense Summaries. Those three include: Using Jinja + namespace to pull unique Project IDs from an expenses table and upsert parent Project records Using a callable low-code pipeline to find expenses missing a related summary, create or find the matching Project Type Summary, and relate sibling expense records Using Jinja + regex + namespace to calculate scalar dollar values, handle null expense types, and distribute records into separate Food, Lodging, and Unallocated tables Qrew tips from the meeting: Wes McAda’s Qrew tip: Think about data volume, reporting needs, and performance when deciding between relational summaries and scalar values. The best approach really depends on the use case. Jim Harrison’s Qrew tip/example: Jim brought up another potential use case to replace “search” with buckets as they can be a very efficient way to pivot and transform data in a pipeline and shared an example to the Qrew to review. Missed the meeting? Here’s the recording. Want the YAML? Reach out to me via email elavielle@quickbase.com for copies of it. As a reminder, we will not be hosting any virtual Qrew groups in May. Instead, we will meet up in Houston on May 18 th at 7pm on the 6 th floor of the Marriott Marquis for a special Qrew Meetup the day before Empower 2026. Hope to see you there!