Blog Post

The Qrew Blog

January Q Tips; Tips and Tricks from The Qrew

ben_simon's avatar
Community Manager
4 months ago

📢📢📢📢 Introducing "Q Tips", a blog series designed for Qrew members to share tips with the rest of The Qrew. Q Tips are short and sweet. The idea behind a Q Tip is there's something you do in Quickbase that makes your life easier, and you want to give access to this gold nugget to the rest of The Qrew. 

Do you want to submit your own Q Tip? Join the Champions Program and take the Q Tip challenge! I'll review all submissions and publish entries everyone in The Qrew can benefit from. What do you get? Points, badges, and the priceless feeling of knowing you made The Qrew a little bit smarter today.📢📢📢

Here are three slick Q Tips submitted by The Qrew this month...


@Prachi Thakkar shared the following on setting up an effective Email Notification: 

Streamline your workflow with email notifications in Quickbase:

  1. Identify Trigger Points: Determine the specific events or conditions that should trigger an email notification. For example, when a new record is added, when a status changes, or when a due date is approaching.
  2. Create a Notification Workflow: In Quickbase, you can set up a notification workflow by going to Table Settings > Notifications. 
  3. Define Your Conditions: Configure the conditions under which the email should be sent. This can include field values, record changes, or specific dates.
  4. Compose the Email: Customize the email content, including the subject, message body, and recipient(s). You can include dynamic field values within the email for personalized messages.
  5. Testing: Before deploying the workflow, thoroughly test it to ensure that the notifications are triggered correctly. I'd recommend sending to yourself to see what your end users are going to see first. 
  6. Deploy and Monitor: Once you're satisfied with the setup, activate the workflow. Quickbase will now automatically send email notifications based on your defined conditions.
  7. Review and Refine: Regularly review the effectiveness of your email notifications and make refinements as needed. You can adjust conditions, recipients, or email content to optimize the workflow.


@Roja M shared this nugget on redirects:

(NOTE: ON ALL OF THE BELOW, =1 or =2 are examples of the ID #, not the actual ID #s to use. You'll need to know the record or page ID to replace 1 or 2.) 

Some redirecting tips to save clicks and faster operation...

1) When you would like to redirect to table view just add "?a=td"

2) When you would like redirect to view mode of the record just type "?a=dr&rid=1"

3) When you would like redirect to edit mode of the record just type "?a=er&rid=1"

4) When you would like redirect to edit mode of the code page just type "?a=pageedit&pageID=2"

5) When you would like redirect to view mode of the code page just type "?a=dbpage&pageID=2"


@Aidon Olligschlager provided a tip on how to reduce wasted space on reports: 

Do you notice a lot of wasted space on reports when using text multi-line fields? Try using a Formula Rich Text field to combine all these different fields into one. In this screenshot you can see a repeating string I created to identify which notes fields are not blank and then to combine the notes into one field for easy reporting. I made the formula a little cleaner by creating start and end tags since they are all formatted the same. By using formula fields like this, I'm able to make reporting much cleaner to look at.

Published 4 months ago
Version 1.0


  • I love the idea of having the start and end tags as a variable in a formula field, makes it so much cleaner and so much easier to adjust them instead of going through and changing 10+ lines individually.

  • KatlynAllen's avatar
    Qrew Assistant Captain

    These rock! I recently started using the Redirect to a Code Page function myself. :)