Quick Base makes form and workflow creations easier than SharePoint
May 25, 2018

Quick Base makes form and workflow creations easier than SharePoint

Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with Quickbase

Quick Base is used to track communications request from all departments within the company. It provides robust reporting and allows us to ensure each request is assigned to a writer.
  • A dynamic form that only displays applicable field(s) based on a previous selection.
  • Report building
  • Workflow/notification creation
  • For those that are not Excel-savvy and understand formulas, it can be challenging to understand. The training I've seen speaks as if the student has a basic understanding of formulas. I'd like to see tips on how a beginner can use the Quick Base help, copy a formula, and the thought process in how to manipulate the formulas to work. Create training in taking the same formula and showing how to use it with 3 different real-live scenarios should help.
  • I have yet to find an easy way to decide if deleting a report or a field will cause regret later on. For example, I deleted what appears to be an unused report only to find out days later that the report was used as a summary lookup on another report. The other report showed a message "error in displaying report". Unfortunately, QB doesn't have a 30-day recycle bin to grant me the ability to restore the item. This would be a huge win.
I have evaluated this product only because our SharePoint intranet will be getting an upgrade EOY. I'm not sure what the full capabilities are yet but highly doubt it compares to QB.
  • Building and deploying business applications faster
  • Improving our ability to drive insights from our data
  • Building and deploying an application (or multiple applications) that meets our exact needs
We were able to achieve building apps faster, pull reports to justify head-count, and address our needs without consulting IT. It's nice not having to submit a request to IT to add a field that should've been done by me the moment the ticket was submitted.
Yes, my organization was able to build an app, create multiple tables, and connect them all easily. Our communications app not only tracks requests, but it allows Comms Admins to assign channels, add contacts, and add/modify/remove channel dates, all in one report even though these three items are all in separate tables.
I would say it's not difficult at all unless needs are more complex than the norm that would require formulas creation, webhooks, etc. There are times when connected apps are necessary and formula is almost always a need.
When I inherited an app, adding/hiding fields in view/edit/add mode is simple. Updating/creating reports is rather easy. The challenge is when the previous app builder kept every, single fields and every, single report that is no longer needed. It's hard to know what items can be removed.

Ease of use. I am a SharePoint Evangelist and built many SharePoint forms with complex workflows... and may I add, another application called SharePoint Designer is needed to build those custom workflows. With QB, I transitioned those forms and built the same workflows quickly and easily, all in one app.

Also, in SharePoint, I would have to create multiple "Content Types" to only display the fields that the role needs to see. This process is time-consuming and redundant. Of course, I could download InfoPath (another MS designer tool) to hide fields, make it two columns instead of one, add sections, etc, but why do that when there's an easier, user-friendly solution in QB?