Archive for the ‘Quick Tips’ Category

Making your Application Fun and Easy to Use

Friday, January 20th, 2012
Like chrome on a car, icing on a cake, or bling on your favorite outfit, there are certain details to a QuickBase application that can make or break the application. They may not have to do with the fundamentals of the application (tables, fields, relationships) but they are very important to the user.
So before you send your application off to users, here is a checklist for QuickBase bling.
1. The Blue Bar — This is a list of tables in your application. It’s handy for savvy users, but confusing for your more tech-phobic users. If your user base has no idea what it would mean to “List All”, you should hide the tables in the blue bar, and instead put function-oriented links on their dashboard (see here).

You can hide the tables either of two ways:


(a) to hide them for all users, click on the table name, then customize, then properties. Click on the Advanced tab, and then on “Hide from Menu Bar.”

(b) To hide a table for certain roles, click on Users in the Silver Bar, then Permissions (by role), then the role you want to address. Then click on the User Interface tab, and then the “Hide Table” checkbox, either for one table or all.


And while you are on that page…


2. The Silver Bar - Most of your users do NOT need to see some of the links on the silver bar. So follow the same instructions as in (b) above, and then in the “Menus” area, deselect the options you want to remove from the silver bar. Typically, you can remove “Customize” and “Users”, as those are options most users are not concerned with. If you want to have total control over the user experience, you can remove all the options. (see https://www.quickbase.com/db/bdx6xa6th for an application that is tightly locked down).

And while you are there….

Hiding tables

3. Saving Shared Reports - While you are setting up roles, go to the “Permissions” tab and decide whether your users should be able to “Save Shared Reports”. The answer is probably no. We all create reports all the time, and if we all save them as “shared”, then pretty soon the list of available reports is huge, and no one know what any of them do. So let your users share Personal Reports - that should still keep them happy. For more info, see this.Saving Shared Reports

4. Help Bubbles - It may be totally clear to you what “Capitalizable Task Budget Revision Number” means, but it might not be so clear to your users.  So make judicious use of “Help Bubbles”. They are set in the field definition, and then available on forms.Help Bubbles

5. Dashboard, Dashboard, Dashboard - You can’t spend too much time on the dashboard. This is the first page most users will see and it needs to clearly show them exactly how to do what they want to do. If they do not like the dashboard, you’ll hear from them (or worse, you won’t hear from them, and they just won’t use the application).
Think about the following:
  1. What buttons and links should I put on this page, so that the user can easily get to whatever reports, forms, and pages they need to get ti?
  2. What reports and charts should be on this page so that the user sees them immediately?
  3. Do I want to keep the report list (on the left margin) and the “Introduction Section” on the dashboard? Usually, the answer is no.

What if some users need one dashboard and another set of users need another dashboard? Most likely, you then want to create separate roles for those sets of users, and give each what they want.

6. Default Fields - Dashboards with columns that head off to the east horizon or confusing or worse. To fix that, click on the table name in the blue bar, and then customize, and then fields. If you don’t see some check boxes on the left of your screen, click on “Show Advanced”, and then in the “Default Columns” field, select the fields that users will typically want to see in a list - usually not more than 10 fields. If the list gets too long, the important fields get pushed off to the side of the screen and your users will have to scroll to the right, which no one likes to do.

7. Face time - No, not the Apple application, real face time. No matter how great your application is, don’t just email your users a link and tell them to have a nice day. Find a time to work with them, live or over the web. Explain what the app is for, and show them how to use it. Check to make sure that fields and reports have names that make sense to the users. Make sure there is plenty of time for questions.

That’s it! Remember, it don’t mean a thing, if it ain’t got that bling.

Happy clicking

Eric Segal
The Data Collaborative

Put QuickBase in Your Pocket

Friday, December 17th, 2010

Smartphones and tablet devices change our lives at home, work, and on the go. Now, QuickBase is part of the mobile revolution.

At least 3 mobile apps work directly with QuickBase, and a fourth app provides a nice platform-independent bridge to QuickBase data. In this article, I’ll take a quick look at these choices, and let you know what might be best for you.

(Full disclosure: One of the apps comes out of my shop. But I’ll do my best to be impartial. That’s easy, in fact, because all three apps use the same tool set and produce similar results.)

The three apps now available are:

  • PocketBase from Madskills, Inc. Written for iPhone and iPad, PocketBase was the first app out of the gate, published on the iTunes App Store on July 4, 2010. It costs $1.99.
  • QuickDroid, from Bret Foreman. This $10 app for Android devices was launched in October, 2010. (Don’t confuse this app with the identically named QuickDroid app from Daniel Himmelein, which has nothing to do with QuickBase.)
  • MobileBase, from The Data Collaborative. This free Android app from my shop is the newest offering on the market. It was published this month

Comparing Basic Features of the Apps

Getting Started. Generally, to use any of the apps, you enter a username and password, select an application, a table, and a report, and then you can view the report. If you are an Enterprise QuickBase user, all three apps let you select a realm.


Below, a screenshot of MobileBase, which presents QuickBase on Android.
Screenshot of MobileBase from Data Collaborative


App Tokens. All three apps permit you to enter app tokens. But typing those 26 alphanumeric characters on a teeny keyboard can be very frustrating. The easiest solution is to allow access to your applications without apptokens.

MobileBase provides one other option by providing a default app token that makes life a bit easier, because you can type the app token into your computer instead of your phone. But taking that route compromises security, since the app token is not private.

Sending Email and Making Phone Calls from QuickBase. All three apps also allow you to click on email addresses to send email. And PocketBase and MobileBase do the same with phone numbers. QuickBase durations are a little tricky (do you display them in seconds, hours, years, or what?) but MobileBase and QuickDroid both handle these well.

What You See On Your Screen. All three apps struggle with presentation, which makes sense as you just cannot display as much data on a smartphone display as you can on a computer screen. PocketBase handles this challenge by giving you neat search capability to search for a row within a report. MobileBase gives you two presentation modes. One mode shows as a table (displaying lots of data but can require horizontal scrolling). The other mode shows as an expandable list (displays less data until you click on a row). All three apps allow you to view reports in table mode.

PocketBase and MobileBase both allow you to save favorites, which makes it easier to return to reports you want to see again and again.

Why are these three apps all so similar? It’s because they all use the same toolset. QuickBase gives us a limited number of tools (or “API calls”) that we can use to connect with QuickBase. Those tools allow apps to do some things easily and other things not so easily. We’d like to allow you to generate new reports from your phone, but the available API calls do not make that easy. We’d also like to let you look at charts, but those are not available through the API. (MobileBase gets around this by opening the charts and summary reports in your Android’s browser, so you can at least view them that way).

So can I enter data into QuickBase on any of these? Sadly, the answer is no. But don’t despair and please read on, because a fourth app offers another option. Data entry in any of these apps would be a little more complex than data reporting. Although all three developers are considering adding data entry to a future version, none have done so yet. Here at Data Collaborative, we are waiting to see what the demand is like for QuickBase smartphone apps, and I suspect the other developers are doing the same.

So what’s the solution if I want to enter data to QuickBase from my smartphone? Canvas provides a neat tool for cross-platform data entry, such as from your smartphone to QuickBase. You design a form once, and then you can use it on many smartphones. For now, Canvas handles Android, Windows, and Blackberry models; iPhones and iPads are coming soon. At Data Collaborative, we’ve connected Canvas with QuickBase (and QuickBooks too, if you’re interested). There is an additional charge for Canvas.

So vote with your fingers! Check out these apps and then rate them in the appropriate marketplace. I bet I can speak for all the developers in saying that we look forward to hearing what you have to say!
That’s it for now. Happy clicking –

Eric Segal
The Data Collaborative
.

Keep Up To Date On Your Data With Auto-Refreshing Charts

Wednesday, December 15th, 2010

Recently in QuickBase Straight Up, we provided you with some tips for enhancing QuickBase dashboards and pages with jQuery. Here, we offer another way to get the most from your dashboard, by embedding auto-refreshing charts in iframes. It’s not a beginner-level project — you’ll have to get your hands dirty with a little bit of HTML — but we think you’ll be very pleased with the results.

Of course, QuickBase lets you embed charts in dashboards by default, but these images are static and don’t give you the kind of real-time access to your data that you may require. By embedding a frame with a refresh interval of 30 seconds or a minute, you can get an effortless real-time view of the latest changes to your QuickBase data.

For instance, let’s say your widget business manages its sales orders through QuickBase. A large volume of orders come in every day, and you want an easy way to keep tabs on which products are in the highest demand for the current day. The first step is to create a chart report that presents the information in the format you want it. In this case, we’ll use a pie chart to show the daily distribution of widget sales.

Pie Chart of Widget Sales

Once you have created your chart, the next step is to obtain the URL of the chart image (which is distinct from the URL of the QuickBase page on which the image resides). How to do this varies from browser to browser, but the first step is to right-click on the image. If an option called “Copy Image Address” or “Copy Image URL” is available, select that. Otherwise, select “Open Image in New Window” and copy the URL from that new window. In Internet Explorer, you may need to select “Properties” and copy the URL from the Properties window. The URL should look something like this:

https://www.quickbase.com/Chart/chart.aspx?realmhost=www.quickbase.com&dbid=bfjqnbu8m&qid=5
&generate=image

There are a couple changes to make here. First, after the parameter called "generate", change "image" to "map". Next, we’ll want to add some size parameters to the end of the URL so that the image can fit nicely on the dashboard. This can be done by inserting "&width=600&height=400" at the end of the URL. Note that 600 by 400 is just our recommended size; feel free to experiment with those values until you find the ideal resolution for your needs.

Now it’s time to add the chart to your QuickBase dashboard. Navigate to your application’s dashboard and click the “Customize this Page” link in the upper-right-hand corner of the page. On the customization page, click the “Add New Section” button and select the “Text” option. Click the “HTML” button in the new section’s toolbar to switch to HTML editing mode.

Illustration of Adding a Text Section

Now, insert the following code into the section:

<html>

<head>
<meta http-equiv="refresh" content="30" />
</head>

<body>
<table>
<tr>
<td>
<iframe id="chart1" src="chart URL here" width="600" height="400" scrolling="no" marginwidth="0"
marginheight="0" frameborder="0">
</iframe>
</td>
</tr>
</table>
</body>

</html>

In the <head> section of the code, the number 30 represents the refresh interval of the page in seconds. You can change this value to whatever you choose. In the <body> section, replace “chart URL here” with the image URL from earlier, making sure to preserve the quotation marks in the original HTML. Also, change the iframe’s width and height parameters to match those specified in the image URL. If you’d like to add multiple charts to your dashboard, simply duplicate the portion of code from <tr> to </tr> and fill in the other image URLs.

Congratulations! You now have an auto-refreshing dashboard - or maybe more than one.

Have you come up with any inventive uses for your auto-refreshing dashboard? Let us know!

Happy clicking –
Eric Segal
The Data Collaborative

Use QuickBase for Event Registration

Thursday, June 10th, 2010

 
The folks at QuickBase made a little change recently that makes life a lot easier. You can now use QuickBase for event registration without exposing your users to an ugly error message.

 

Until recently, if you opened an application to everyone on the Internet, allowing anyone to enter a record but not see any records, they got an ugly message after saving a record. Now, if a user saves a record and does not have permission to view any records, they are automatically redirected to the application dashboard.

Know what You are Doing with Proxy Fields

Tuesday, December 8th, 2009

    Almost every time you set up a relationship in QuickBase, a “proxy field” is created. That’s so when you pick a parent record, you see a dropdown that is meaningful to you.
    For example, if you have a relationship between Projects and Customers (one Customer to many Projects), the real relationship is between the Project and the Customer’s Number. But a Customer Number (1,2,3) is probably meaningless to you. What you really want to see is the Customer Name. So in a case like this, you want the Customer Name to be a proxy field in the relationship.

 

   The Infamous Proxy Field - Should it be banned?

 

 

 However, Proxy Fields are problematic. In the example above, if you had both the Customer Name field and the Related Customer field on the same form, they would cancel each other out and neither would work! And Proxy Fields can create problems when they are used for filtering records in a Report, too.Â
    At Data Collaborative, our general practice is not to use Proxy Fields. But we are QuickBase geeks - we eat and breathe this stuff. Our advice to you is this: pick one strategy and stick with it. If you use Proxy Fields, be careful about mixing a Proxy Field and a Lookup Field on the same form. If you don’t use Proxy Fields, learn how to use Record Picker fields to make the lookup dropdown have meaningful values.