Item: Quickbase
Rating: 7
Author: James Stewart

Overall Satisfaction with QuickBase

Use Cases and Deployment Scope

Many templates to build upon for a quick implementation. The templates are all very functional out of the box. Further development can be a tad awkward if you do not take time to study the product in depth, and spend time regularly developing in the environment.

Pros and Cons

Pros

Logging work requests
Tracking data and information requests to completion
Simple workload reporting

Cons

Modifying and advancing your application is confusing and awkward if you are not a regular developer in the product
Lookup tables and validation constraints in other tables based on lookup tables is awkward
Can only add single attachments to work tickets

Alternatives Considered

Worked in the past with ForntRange HEAT and ITSM. Wish Quickbase would give you more direct access to the physical database backend.

Likelihood to Recommend

We use it largely to log work requests. [We] get the requests out of individual staff e-mail boxes and into a central Quickbase repository. One of the delivered project management templates with minor modifications has been sufficient thus far. We would like to mature the application for our some of our specific needs, but do not have a resource to dedicate to Quickbase development. You have to use their web interface and learn their specific quirks. You cannot work directly with the database and create screens over the tables.

Comments

Please log in to join the conversation

Worth a look