Resource Icons
Latest Highlights
Check Out The Latest in The Qrew
1 MIN READ
Hello Qrew!
We’re back with this month’s edition of Certification Wins, where we proudly spotlight the amazing individuals in our community who’ve achieved Quickbase certifications this past April!...
9 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...
4 hours ago
2 MIN READ
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 you start. We'll cover the basics, with...
11 days agoThe Content Feed
Feed
Best practice for using @mention in a log rich text field.
Anybody have a best practice on using the 'Mention' feature in a log rich text field? My use case is: A rich text field w/ log edits turned on is used as a collaboration tool for team members to provide updates and ask each other questions. They mention each other in the comments and receive an email when they have been mentioned, via the handy 'send to users @mentioned' feature in the new notifications (see image below). However, when the 'Log edits' setting is turned on, Quickbase will email ALL the users who have ever been mentioned, when really we want just the person/people who were mentioned in the most recent comment. My workaround for this is to create a formula field to parse out the most recent comment and then a webhook or form rule to enter this value into another rich text field, with the @mention feature turned on. This last rich text field is used in the 'To' setting of the notification. This is a lot of work to simply use the mention feature! Is there a better way to do it that I'm missing?
Muliple Choice field set with Form URL?
I am wanting to place an image on a form. I have many forms and each version may have a different image. I was wondering if it is possible to set a Multiple Choice field to a specific value using the URL the user clicks on to open the form? My thought is that if I can set the field to the correct value then I can determine which image to show on the form based on the field value that has been set. Is there a better way to accomplish this? Thanks, BrianNew email notification beta has arrived
NOTE: THIS BLOG WAS AUTHORED BY BrianCafferelli , BUT DUE TO TECHNICAL CHALLENGES, BRIAN WAS NOT ABLE TO PUBLISH. Companies around the world run time-sensitive, business-critical processes on Quickbase. And one of the ways this streamlines how you manage critical information is through our built-in email notifications. The ability to send alerts to the right people at the right time ensures that your team stays productive. We’ve upgraded much of the user interface across the Quickbase platform recently, such as reports and forms. And the next step in this journey is simplifying emails and making them more flexible. We’re proud to announce that we have re-built emails from the ground up. We are providing a new and modernized experience that supports new forms, allows you to pick the time of day an email is sent, and more. Read on to learn more what’s possible using new email notifications. Using new forms and notifications together We recently rolled out a new version of forms, providing a drag-and-drop building experience and giving you more control over the layout and appearance. However, using these new forms requires a separate legacy form to be built for emails as well. We are now making this build experience easier and more consistent, now that you can display a new form in a new email notification. This helps make your notifications more professional-looking and engaging. Embedding reports and charts Legacy emails in Quickbase allow you to send a single report to a group of users periodically. New email notifications will also allow you to send a chart, and even multiple reports or charts in the same email. This puts a lot of power into the hands of the app builder since you build these user interface elements such as reports, and can use them in many places such as dashboards and emails. Expanded options for the From field Being mindful of who appears in the From field of your email can help clarify who is driving the process at hand and help an email recipient to respond quickly. Quickbase enables you to set your From field to the generic “notify@quickbase.com”, or the user set in a User-type field. For example, an email on a compliance requests table could appear as coming from the user who placed the request. Our new email notification feature adds a few options for setting your “From” field. You can have your emails appear as coming from the owner of the email notification. Or you can even have emails appear as coming from the user who triggered the email in the first place. This gives you a great amount of flexibility to set up email notifications to match your exact process needs. Setting CC and BCC fields With the legacy emails, you can dynamically set the recipient based on data in Quickbase. For example, based on the Assigned To field in your table. This maps to the To field in the email message. However, it’s not possible to populate the CC or BCC fields today. New email notifications enable you to CC and BCC people. (This ability must first be enabled at the realm level) Attach files to your emails Using legacy emails, you could include a file attachment as part of the form or report being sent. New email notifications will let you go a step further and take a file from a File Attachment field in Quickbase and attach it directly to the email. Better bulk options We have also added more flexibility for managing bulk emails. For example, imagine that you have created an email notification which is sent when a record is edited. If a user clicks to edit a single record, then saves it, the email sent will reflect the changes made to that individual record. But what would you like to happen when a user enters grid edit mode, and updates many records at once? Legacy email notifications allow you to choose whether you want to send the email if many records were changed at once. Our new email notifications go one step further and make it easy to send individual emails (up to 10 at once), or to send a combined email that covers all the triggering records. Audit Logs We get support cases from builders asking to verify whether an email notification was sent, when it was sent, etc. The Quickbase Tech Support Team has access to that information today, but customers are not able to see it directly. When you leverage our new email notifications, account admins will be able to track usage of those emails in their Audit Logs. A streamlined builder experience We’ve also made it easier to build email notifications. We have combined the functionality of legacy notifications and legacy subscriptions together, allowing you to set up either a triggered email or a scheduled email. Need to change the trigger type later? No problem! Using the new email notifications, you will be able to go back afterwards and switch the trigger type without needing to create a new email from scratch. This also provides a more intuitive and streamlined experience, similar to how trigger behavior can be modified for a pipeline. For scheduled emails, you will also be able to specify the time of day the message will be sent. This is a long-time customer request which makes it easier to plan out your workflows. Our updated rich-text editor helps you to create impactful and professional messages, with new features like inserting report widgets into your emails. And you can still modify the HTML markup directly if you’d prefer. Tips for new builders To create notifications that are impactful, here are a few things to keep in mind: Leverage the conditions in the trigger to ensure the email is sent precisely when you need it to be Write out your email in a way that makes it clear why the recipient is receiving it, and what they should be doing upon receiving it Use rich text and images like your company’s logo to create a more engaging message. The future of legacy email notifications and subscriptions In order to make all the powerful improvements above to email notifications, we needed to re-build the feature from the ground up. That means that you will need to create new emails to take advantage of these new capabilities. However, we realize that most of you rely heavily on legacy notifications and subscriptions. So those legacy emails will continue to be available and operate exactly like they do today, and we do not currently have plans to change that behavior. Try it out today! We opened up our beta program for new email notifications to all users in March 2024. Simply navigate to table settings, and when you click the New button for emails you will see the new “Build your own” option. To learn more about new email notifications, please see the article in our help center.Join us for a Jamboree of June Events!
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 up with brand new topics and a hands-on training opportunity. App Builders Qrew Meet Up June 10, 2025 | 12:00–1:00 pm EDT – Register here Join Nichole Braswell, Quickbase Developer at Sympo, to discover an easy way to manage multiple forms for a single record with just one button. Plus, Lyla Rozelle, Sr. Product Manager, will give a quick tour of the updated admin console account summary page, and Ventsi Tasev, Group Product Manager, will share the latest on Audit log feature updates. Cascading Permissions – General Qrew Meet Up June 11, 2025 | 12:00–1:00 pm EDT – Register here Join this Empower encore Qrew Meet Up with Lauren Molino, Director of Advanced Solutions Services, for a hands-on, follow-along session where you'll learn how cascading permissions can help you control access across your Quickbase apps, streamline workflows, and boost security—all with fewer manual updates. To follow along, download the "Empower 2025 – Learn Cascading Permissions" app from the App Exchange before the session! Code Pages Qrew Meet Up June 24, 2025 | 12:00–1:00 pm EDT – Register here Join us for a quick overview of code pages with helpful tips and resources to get started, then explore four real-world code page examples by customers and Quickbase subject matter experts that you can try out after the Meet Up. Pipelines Qrew Meet Up June 25, 2025 | 12:00–1:00 pm EDT – Register here Wes McAda, Senior Software Developer at Versar Inc., will give an enhanced encore of his Empower 2025 session on using Pipelines with an Everyone-on-the-Internet app, featuring time-bound secure links, cascading permissions, and new security features for staging documents. In the spirit of having more fun at our Qrew groups, we will be doing more raffles, door prizes, and certification celebrations throughout the month. Find additional event details on our Events Page and don’t hesitate to reach out if you have questions or comments. We can’t wait to see you in June!Relationship Condition Dropdown stopped to work after formula update
Team, I have a challenge to my relationship update. For my relationship I was using "Formula Field" [SMO_Predecessor_Key] which was selected to create conditional dropdown based on its value. [SMO_Predecessor_Key] used in formula another field [SMO CPS Template] which had some logic in it based on field [SMO]. I no longer need this logic so I decided to rewire [SMO_Predecessor_Key] directly to field [SMO]. After I did it I have problem that my Relationship PROXY field does not work in Legacy Form. It ask to choose [SMO_Predecessor_Key] even if this is already selected. I notice that if I re-select value in field [SMO] in form (i.e. remove value, select it again, even without saving, this starts to work. So problem is with data which are already filled in. [QUESTION] - is there a way to force such refresh to all records and to not need to do it 1 by 1 in form? What I tried: I tried to Import records ID# and field SMO but during Import No update to records (as SMO does not change). Tried to create new field [SMO_Predecessor_Keyv2] and update Conditional Value to it and back. But not working as well. This is how dependency of fields looks line (Blue changed to Green) Current workaround but not well seen by users 😢
Count days between 2 dates with a twist
I have a Start date and end date I am using the Weekdaysub(end date), (Start Date). but i want to add a IF statement like say to add saturdays to the mix. so if I was to set the date from 5/25/2025 and end on 5/30/2025 but if the saturdays check box was clicked it would also add the saturdays between those dates and return 6 (Monday-Saturday) and if the saturdays was not checked it would return 5 (Monday - Friday)
Delete option
I'm at a loss right now. I have an app and for some reason I'm the only one that can delete from one of the tables. I have checked the roles and they do have the delete option. I have checked the form and it does not have any rules that restrict delete. I as the admin am the only one that can delete. Any ideas on where else I can look. I've looked everywhere that I can think of. FYI: These are the new forms.Running totals for charts
Hi all Want to share my solution on how to create running totals for charts. QB does not support running totals for charts, only summary reports. QB Junkie has a really good solution to create running totals using the query formula but as stated in her video it only works with small data sets and it is really memory intensive. QB has posted a solution to use the report API function to build a new running totals table from a summary report but I found this to be even slower and it does not give the user live updates. I use own table relationships that allows me to chart large datasets quickly and live. Below is an example of this application but I use this for many other data sets that do not use dates so do not get stuck on the dates table step. Create a dates table. I made the key a text field so that i can create the reference field. Record ID is also an option but a bit harder. My key was "<date>-<project no>" Create an own table relationship I use pipeline's Make Request action to create and maintain this table with its key and related field value. This is a Jinja code on Exchange I borrowed so let me know if this is of interest to anyone. It super-fast but again not a requirement. Summarise the values I want into the dates table Create a blank formula field and this will be my running total Summarise the blank formula field i created in step 6 above. I use the own table relationship for this. Go back to the blank formula field in step 6 and write a formula that adds the summarised value in step 5 to the summarised value in step 7. BUT I found this needs to be via an if statement and can't be a simple addition as it fails randomly. Maybe a bug in QB but I found my way around this and its now super reliable. My if looks like this If( Nz([Field in step 5]) + Nz([Field in step 7]) <> 0, Nz([Field in step 5]) + Nz([Field in step 7]), Nz([Field in step 5]) <> 0, Nz([Field in step 5]), Nz([Field in step 7]) <> 0, Nz([Field in step 7])) Thats it. Fast reliable running totals to draw charts! See screenshot belowQuickbase to google calendar pipeline issue
I have a pipe line set that manages my calendar installs to a google calendar. It has 3 pipelines New install are added changes in installs are updated deleted install are deleted. The path flow work great but the dates are not correct. Here is the quickbase calendar Here is the Google Calendar: Start Date and End dates are date/time fields built with the following: Does anyone have any ideas why these dates are distorting by a day?
