Forum Discussion
DebbieTaylor
Qrew Trainee
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.'
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.'
IvanWeiss
6 years agoQrew Captain
Debbie, I could not agree more that a strong app diagram would be very helpful. I was using the built in tool and started to create one but honestly it got a bit complicated. I have a subscription to LucidChart so I was going to document it there but as complicated as it is now with quite a few tables I thought might be best to just leave it to the app tool to maintain. But might be better to go a 3rd party route.
Any suggestions to a good tool or method for a relatively larger app? I probably have more than 20 tables at this point and it is still climbing. I am about to start building out order management functionality too so that is only going to further complicate it.
Any suggestions to a good tool or method for a relatively larger app? I probably have more than 20 tables at this point and it is still climbing. I am about to start building out order management functionality too so that is only going to further complicate it.