Menus or app groups

  • 0
  • 1
  • Question
  • Updated 4 years ago
  • Answered

I'm currently working on a design for a new CRM-type application. The system is likely to have more than 50 tables, easily up to 100 by the time we’re done. I’m concerned that a user may have trouble navigating through a large app like that. Is there a way to build a menu system in QuickBase?

One idea I had was to create a new app for each module and then use cross-app relationships. That would break things up pretty well and make security a little bit easier, module by module.  The only issue with that is we currently use QuickBase for a lot of other little apps and they would get mixed in the user’s app list. Is it possible to create a new “app group” or billing account to keep a group of apps separate but still be billed only once per user?

I’ve also gotten to the point where I think QuickBase may not be the best solution for this type of application.

Any thoughts or ideas are appreciated.

Photo of Hunter Contracting

Posted 4 years ago

  • 0
  • 1
Photo of Ⲇanom the ultimate (Dan Diebolt)

Ⲇanom the ultimate (Dan Diebolt), Champion

  • 30,434 Points 20k badge 2x thumb
I would concentrate on documenting what you have, creating an ER diagram, refining roles and workflow and generally working on organization. Creating an ER diagram is one of the first things I do when I see a client's application for the first time. When applications get this large they tend to accumulate "cruft" and maintainers become adverse to cleaning things up for fear of breaking something when they don't remember what some parts of the application is used for. It is not uncommon to see extra fields and relationships that are never used.

It is also possible to create various navigation aids using both native and script features but I would not jump into that activity until you deal with general organizational issues.
I agree.  One app and extensive use of Dashboards to help users do what they need to do.
Extensive deliberate use of Cross app relationships is risky because when you look at field usage on the parent side of a Cross app relationship it won't tell you that the field is in use or even that a relationship Exists.  Then you delete a field and disaster results.
Thanks for the feedback. Good stuff to keep in mind as we plan this app.