Formula-URL fields are a great way to create custom links, helping users navigate to forms and pages within and outside of Quickbase.
Here are a few examples:
Let’s go through these examples one at a time:
Say your company stores a biography of each employee on its public website. The link to each profile follows a similar file path. For example, [www.]mycompany.com/profiles/tina_bradley'.
In this case, ‘tina_bradly” at the end of the URL will direct the user to Tina Bradley’s profile
Using an employee’s [FirstName] and [LastName] from their employee record you can construct a URL-Formula creating a link on each employee’s profile using the following formula:
[www.]mycompany.com/profiles/' & [FirstName] &”_”& [LastName]
The first part of the formula is hardcoded with "www[.]mycompany.com/profiles/". Then we use the ‘&’ symbol to append the root URL with the employee’s [FirstName].
After that, we add an underscore with ‘&”_”’. Last we add the last name to the URL string with ‘& [LastName]’
In this case, suppose you have a table where your company stores time cards. You’d want to show different fields depending on whether the timecard is for regular hours or time-off.
In this case, you can create one form for ‘regular’ time cards and a different form for ‘time-off’ time cards.
Once you’ve created your two forms you can create your formula-URL field in Quickbase:
URLRoot()&"db/"&Dbid()&"?a=dr&rid="&ToText([Record ID#])&"&dfid=10"
One great feature of Quickbase formula-URL fields (and Rich Text fields) is the ability to create buttons, which can incorporate API capabilities (including things like modifying or adding records).
Let’s say your company has a number of projects. When a project is complete, you’d like the project manager to open the record and click a button to mark the project complete.
In this example, we’ll create a checkbox field called ‘Project Complete’. When checked, the project will be considered complete. Then we’ll create another field to store our button. When the button is clicked it will check the ‘Project Complete’ field.
URL=URLRoot() & "db/" & Dbid() & "?act=API_EditRecord"& "&rid=" & URLEncode ([Record ID#])&
"&_fid_Your Field ID=1" & "&apptoken=" & "Your app token";
So, why create a button to check the ‘Project Complete’ checkbox field? Why not just have the user click the checkbox?
First, by creating a workflow of a button, you can make actions (such as completing a project) more explicit to users.
Second, this is just a basic example that can be used as a building block for more sophisticated buttons. For example, your Quickbase formula might stipulate that the button be shown on a record only if certain conditions are met. For instance, the button might only appear on a project if that project has already been awarded.
If you want to take it to the next step you can start doing such things as inserting JavaScript into your field to redirects, add pop-ups, and a whole variety of cool tricks.
Visit here to demo examples in this article.
© 2025 Quandary Consulting Group. All Rights Reserved.