QuickBase allows you to create custom reports in a variety of formats for your application. Common reporting needs include:
You can create reports that contain data from more than one table by using either:
Relationships (the most precise method)
Report link fields (a more informal method for linking loosely associated records)
The best and most precise way to access data from more than one table in your application is to create a relationship. A relationship is a link between two tables (similar to a join command in SQL). You usually link tables in a one-to-many relationship, where a single record in a "master" table links to multiple records in a "detail" table. For example, you have a Project Management application with three tables: Projects, Tasks, and Issues. You create a relationship in which Projects is the master table and Tasks is the detail table, because each project has multiple tasks. You create another relationship in which Tasks is the master table and Issues is the detail table, because each task has multiple issues. When you create a relationship between tables, you designate a field with which to link them. This field is called a "reference" field. "Reference" is not a field type, but an attribute of a field. A reference field in the detail Tasks table lets you select which master Project record to associate with a Task.
Data always flows down from the master table to the detail table in a relational database, like QuickBase. In the Project Management application, the data flow is Projects > Tasks > Issues. You include lookup fields in the detail table to pull information down from related master table records. Lookup fields can pass all types of data, including text. You could include lookup fields in the Tasks table to pull in the related "Project Name" and "Project Manager" from the Projects table. To create a report that contains text data values from both tables, you must create that report on the detail table.
You also can include summary fields in the master table to pull certain information up from the detail table; however, summary field do not pull specific text values up from the detail table. Summary fields perform functions such as giving you a count of the number of detail records tied to a specific master record, or giving you the maximum value in a numeric or date field across all your detail records. Summary fields can be exported and used in formulas. Once you create a summary field in the master table, you can pass the value of the field down to the detail table using a lookup field.
It may be useful to map out your tables' relationships so you can see how the flow occurs and then create your reports accordingly.
Note that at the form level, you actually can view specific information from the detail table on an individual master record. It's called an embedded report. However, you need to create reports to view information for multiple master records, and you should create those reports on the lowest level detail table.
Creating a relationship is usually the best way to link records from multiple tables. However, there are some cases in which you might not need the precision of a relationship and simply can create a report link field instead. A report link field is great for matching records with a loose connection—where one record may or may not contain a value from a field in another table. Instead of you and your users connecting records in separate tables (by selecting the related item from a dropdown list), QuickBase make those connections on its own automatically. For example, say you have a customer feedback table where you store comments submitted to your web site's suggestion box. In the midst of the "comments" field they may mention one or several of your products. A report link field enables QuickBase to search the comments field for mentions of each product name and have a link in your product record open all relevant feedback records.
Summary reports help you make sense of data from a large number of records in a table. You can sort and group summary reports to specify which records should appear first, how all records should be ordered, and whether like records should be grouped together.
If you have multi-dimensional data to display, you can group by more than one field using a summary report with crosstabs (short for cross tabulation). Summary Crosstab reports are much more flexible in terms of table design because they let you group records in rows or columns. This approach gives you added power—literally another dimension in which to display information. Read more about summary reports for a good example of when to use summary and summary crosstab reports, and how to create them.
Note that while summary and table reports calculate totals and averages for you, these values do not actually exist in fields within QuickBase. If you export the report data, the total/average data is not exported. You also cannot use this report-calculated summary data in formulas. Data must exist in a field to be exported and used in formulas. You can create summary fields in the master table to store total, average, and other summary data from related detail records. You can include the summary fields when you run reports on a master table, and if you export the report the summary field data is exported. You also can pass the value of the summary fields down to the detail table using a lookup field if you want to use the data in detail table formulas, include it in detail table reports, or export it from the detail table.
Are you managing a project and want to see all tasks that will complete each day, week, month, or quarter? Or perhaps you are managing sales and want to see what payments are due per month. QuickBase allows you to group summary reports by different increments of time (days, weeks, months, quarters, fiscal quarters, years, fiscal years, and even decades).
Specify this type of grouping when you create a summary report by selecting the appropriate field (such as Calculated Finish Date or Payment Due Date) in the Group by dropdown and selecting the appropriate time period in the Combine dropdown, shown below:
Common project management reporting needs include:
You can run reports to show you the tasks assigned to each person on your project team. You can accomplish this in a variety of ways. For example, your Project application contains a master Tasks table and a related details Resources table. Each Task record contains an "Assigned to" field that specifies which Resource is assigned to the task. You could create the following kinds of reports on the Tasks table:
A summary report
in which you set the Summarize
dropdown to "# of Tasks" and Group by to "Assigned to". The resulting report
contains the number of tasks assigned to each resource, and you can
click the resource's name to see a list of his or her task.
A table report
which you sort by the "Assigned to" field.
The resulting report contains a list of tasks sorted alphabetically
by resource name.
A timeline report
in which you set Sort & group
to sort or group on the "Assigned to" column. The resulting report contains a timeline
of project tasks grouped by resource name.
A line or bar chart
report in which you view "Assigned to" resources on
the x-axis and "# of
Tasks" on the y-axis.
You can then click any point or bar to view a list of tasks assigned
to that resource.
A pie chart report
in which you set the Series
to "Assigned to" and the Data
Values to "#of Tasks". You can then
click any section of the pie to view a list of tasks assigned to that
You can easily create a report to view the status of your project's tasks. For example, your Project application contains a Tasks table that has a multiple-choice text field for status (Not Started, In Process, Complete, and Blocked). If you run a table report on the Tasks table in which you specify to sort data by the "Status" field, you will see a list of all tasks sorted alphabetically by status.
You can also create reports that show you only tasks of a particular status, such as a report of only Blocked tasks. Read more about filtering records that display in reports.
QuickBase also enables to color code tasks by status, priority, due date, etc. to get the big picture at a glance. In the example below, the project manager has created report of overdue tasks (tasks whose Status is not Complete and whose Calculated Finish Data is earlier than today). The project manager has enabled row colorization to show high priority overdue tasks in red, medium priority overdue tasks in yellow, and low priority overdue tasks in green. Report users can quickly see where to focus attention and apply additional resources.
Read more about using row highlighting (colorization).
Are multiple people in your project responsible for completing different parts of the same task? If so, QuickBase reports can help you manage your project's workflow. After you implement this workflow solution, tasks flow automatically from one person's "to do" report to the next person's report when the first person completes his or her part of the task.
For example, maybe your marketing copy needs to go through an approval process that involves four different people. When the first person approves the marketing copy, it automatically appears on the next person's "to do" report. Or perhaps you have a developer who fixes software bugs and a quality assurance tester who confirms the fix. When the developer fixes a bug, it automatically appears on the quality assurance tester's "to do" report.
Read how to manage workflow with user fields and reports.
If you have created an application to manage projects and/or tasks, your users often want to see those tasks to which they are assigned. For this reason, QuickBase makes is easy for you to create one custom report that shows each staff member only those records that pertain to them.
How does it work? Since QuickBase knows who's logged in, you can ask the program to show or hide records based on whether or not the current user's identity matches the value in a user or list-user field. (What's a user field? What's a list-user field?)
Read how to create reports that show a user his or her own records.
Are you are creating many slightly different reports based on individual user's needs? If so, you may want to create a single report that prompts users for selection criteria for one or more fields.
For instance, you have three project task reports: one for open tasks, another for in progress tasks, and a third for closed tasks. Instead, you could create a single report that prompts a user to select the task status.
Or, you have an application that manages contact information for companies and find yourself creating reports to display contact information for individual companies. Instead, you could create a single report that prompts a user to select the company whose contact information he or she wants to view, as shown below.
Read how to create a report that prompts users for selection criteria.
Return to top
© 1999-2015 Intuit Inc. All rights reserved. Legal Notices.
Show help contents