So you've snapped and posted photographs of all your Hummel collectibles and you'd like to share them with the world. Of course, you've inventoried your entire collection in a Quickbase. Now, you want to connect each record with its corresponding image, but the images all live on your "Hot Hummels" Web site. Sure, you could create a file attachment field to store and show images within each Quickbase record, but you'd rather not store them in two places.
URL fields to the rescue! Quickbase URL and Formula - URL fields let you store and compose links that deliver whatever page you wish to the viewer's browser. The URL field type you choose, depends upon what you'd like to do:
When you want users to type in an entire URL for a record they're entering, create a plain URL field. For example, say users are entering company information into your Quickbase. A URL field lets them enter the company's Web site address. Once they save, Quickbase displays the field as a link that delivers the Web site to any viewer.
When you want users to enter part of a URL (like the image file name of a Hummel figure on your Web site) use a Formula-URL field. You can compose the formula field to always include the start of your Web site's URL. When you create another field (something like Image Name) then you or a viewer can use it to enter only the file name that completes the URL. Format your URL formula field to concatenate (string together) the start of the URL and whatever file name lives in the Image Name field to get a custom URL for each record.
FAQ - What if I want all records to show the same URL?
If you want each record to contain a link to one particular Web site, create a plain URL field. Open the field's properties page and set the Default value to be whatever URL you want. Save changes. Add the field to forms or reports and make it a "Read-only" type field. That way, the one address you entered appears to each viewer, but no one can edit it.
To create a plain URL field:
Create the URL field.
Add a new field. Name it something like "Company Web site" or whatever describes the type of URL that users will enter. Select URL as the field type. When prompted, add the field to forms where you want it to appear.
Set URL display preferences.
Your URL field doesn't necessarily need to show a huge URL that's hard for average readers to parse out. Instead, the link it displays can contain a more informative label like "Company Web site" or "View product image" or whatever you want. To show more descriptive text, enter the term you want in the Display section's Link text field.
You can also tweak format with the following options:
Don't show 'http://' when showing the URL. Turn on this checkbox to shorten the URL to a more digestible length by removing extras from the beginning. So, instead of https://myaccount.quickbase.com, viewers would see only myaccount.quickbase.com. Or, if your URL ends with a file name, Quickbase displays only the file name.
Display as a button. If you really want to emphasis to users that they can "click here" to see a picture or related Web page, then turn on this checkbox to display the URL field as a button instead of a blue underlined link.
Open target in new window. If you don't want viewers to stray away from your Quickbase application, turn on this checkbox. When you do, the URL field's link opens a new instance of the browser in which to display the link's destination. The Quickbase screen from which viewers launched the link still displays underneath the new window.
When you're done setting preferences, click Save.
When editing a record, app users will be able to enter Web addresses in the new URL field. When viewing a record, the URL field appears as a link or button.
To create a Formula - URL field:
Create a field to contain the portion of the URL that users enter.
Create a Text field (read how to add a field) in which users can enter a portion of your URL. For example, this may be an image file that lives on the Web or an HTML page that contains information relevant to the record. Add this field to forms on which it should appear.
Add a Formula - URL field to the same table.
Compose the formula.
Within the Formula box, type the formula that generates the link that this field will display. This formula should begin with the start of your URL in quotes, followed by an ampersand and then a field reference to the field whose value completes the address. For example:
"http://www.example.com/images/" & [Image Name]
Set display preferences.
Formula-URL fields offer the same display settings as plain URL fields. To learn about all your options, please read Step 3 in the preceding section.
Now whenever a user enters a file name in the field you created in Step 1, Quickbase automatically generates a working URL that opens that file in a viewer's browser.
Note: If your Formula-URL field includes an API call and your application requires application tokens, you'll need to insert the appropriate token in the API call. (API calls and app tokens are not available to accounts on the Quickbase Essential plan.)
Formulas and workflow
Many users find the formula URL fields to be extremely valuable because they make it easy to design complex workflows, for example, when you are using formulas such as URL field buttons like, Add Task, Add Document, or Add Project. It doesn't matter if records are child or parent records you are creating, only that you are leaving one location to manually add or edit a record and you wish to return back to the location from which you started.
Workflows that require user input
When creating a relationship, Quickbase automatically generates an "Add Record" Formula - URL field. In the field itself,
"&z="&Rurl()is added to the field when the relationship is created. This provides a quick way for users to create a child record.
There are two valid use cases for
"&z="&Rurl(). One is when you use
API_GenAddRecordForm and the other is when you use the
a=er function to edit a record. In both cases, you would manually modify a record, save the record, and return back to the URL from which you started. Here's an example using
URLRoot() & "db/" & [_DBID_TASKS] & "?act=API_GenAddRecordForm&_fid_48=" & [Record ID#] & "&_fid_8=" & [Est Start Date] & "&z=" & Rurl()
And here's an example using
>URLRoot() & "db/" & Dbid() & "?a=er&rid=" & URLEncode([Record ID#]) & "&dfid=12" & "&z=" & Rurl()
The thing to remember about the above two examples is that you are starting from one spot, either adding or editing a record, manually saving the record and returning to your starting spot. The
"&z="&Rurl()only works in this situation.
Workflows that do not require user input
If you are using another API call such as
API_EditRecord, the format for redirecting to another page is different. In this case, you can redirect the final API call in your formula to an
a=doredirect URL. This takes the z=rurl() concept and makes it more valuable, since it allows you to make one or more API calls, and then reload the current page. For example:
URLRoot() & "db/" & [_DBID_TASKS] & "?a=API_EditRecord&rid=" & [Record ID#] & "&_fid_7=Approved" & "&rdr="&URLEncode(URLRoot() & "db/" & Dbid() & "?a=doredirect&z=" & Rurl())
You can also use
rdr to redirect the user to a specific page. For example, after a new record is created, perhaps you want to display a "thank you" rich text page you've created. This thank you page should appear as the next step in the workflow, if the user was on the app dashboard before they created the record, or if they came from the table home page. For example:
URLRoot() & "db/" & [_DBID_TASKS] & "?a=API_EditRecord&rid=42&_fid_7=Approved"&"&rdr="&URLEncode(URLRoot() & "db/" & Dbid() & "?a=dbpage&pageID=30")
Is this help page useful? Rate it:
© 1999-2021 Quickbase, Inc. All rights reserved. Legal Notices.