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

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.

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.

Thanks Mark, that is a great idea to put a link on an admin page.  I did learn the trick on moving the box to the corner which is a HUGE advantage.

I am about to start building out order management functionality so I know that number is going to still grow quite a bit.  I would be surprised if I land in the 30-40 range.

It just means that you get to continue to use your imagination on how arrange the boxes to keep most of the Relationship lines from crossing.

lol made my night with that one!

Gliffy is my favorite tool for designing apps. and planning at workflows.  It has a few advantages over the 'in-app tool.'

• You can plan BEFORE you build.
• You can add field lists, comments, icons, workflows etc.
• You can easily extract a presentation-quality image file.

I actually do agree with Debbie that especially for larger apps they should be diagrammed out before you start building.

For simpler apps I tend to scribble something out on a back of a napkin and then throw myself into it.

But I will say that once an app is well under development it tends to be a journey and not a final destination. As such the app keeps evolving and you need quite a bit of internal discipline to maintain a third-party tool in sync with the changes you�ve made in your app.

So maybe the best practice is to start with the 3rd Party tool diagram (or at least a neatly hand sketched diagram) so you can plan your app but then on a going forward basis once the app building has been underway for a while and you have caught up to your diagram, go into the native Relationship ship Diagram, unscramble it, and maintain the built-in tool going forward each time you make new tables or Relationships.

There is also Draw.io which is a totally free option that works wonderfully. So if someone needs a good diagramming tool but doesn't want to pay I would look there.

There is also Draw.io which is a totally free option that works wonderfully. So if someone needs a good diagramming tool but doesn't want to pay I would look there.