Forum Discussion

IvanWeiss's avatar
IvanWeiss
Qrew Captain
6 years ago

Restructuring Task Table Broke all my API Buttons, Not sure how to fix

I recently corrected my tasks table.  It used to have a List User Field for Assigned To so that I could easily assign tasks and create API buttons to be able to create tasks from my "Opportunities" Ta...
APIs and custom code
Forms
Formulas and functions
DebbieTaylor's avatar
DebbieTaylor
Qrew Trainee
6 years ago
Congrats on correcting the task, Ivan. 

Before you invest more time in building API buttons, I'd encourage you to step-back and review your application design.  Grab a sheet of paper (or use the tools in QuickBase).  Draw a rectangle for each table.  Draw an arrow to represent each relationship (point it toward the child table).  This picture is called an application diagram.

Review the diagram with an experienced app. builder.  Mark Shnier is great; CloudBase Services will spend an hour with you gratis.  If you have a good design, building the app. will be easier and faster than if you have extra table OR bad relationships.

Writing API buttons is the equivalent to running water lines.  It's only worth doing once you are absolutely certain where you want the faucet.  So, find yourself a great architect and map out your 'building.'
QuickBaseCoachD's avatar
QuickBaseCoachD
Qrew Captain
6 years ago
imho, the in app tool is the best idea as it's always up to date.  

Uncheck the "Show Reference fields" to reduce clutter.  When the tale pop up window smacks you in the face enough times when dragging the boxes around, you will learn to drag it out of the way to a bottom corner (neither of those "stick" so you will have to do them again when you come back to the diagram.

Consider putting a link to the Relationship Diagram page on an Admin dashboard while you are building the app. it will save you a few clicks.

20 tables is not a lot for that tool and 20 tables is not that unusual for a Quick Base app.