Add row on another table

[Cannone_Cannone]

Hello at all!!
I have an a question!!
I use the action ADD row in another table,
The row
the rows are inserted in a different sheet from the main sheet of the App.
in your experience, is it better to put everything in the main sheet or how do I use it?
all this can you have more slowdown of the app?
thank you

[SkrOYC]

This is like “One big table vs multiple ones”
I’d say, based on my experience, the only need for one big table is when you need one-to-one relationship and you need items created automatically for each one of the main ones.
You end up with a big table, multiple slices, and some custom actions for navigation.
I have a 3-in-1 table because I needed both, one-to-one and that records from table 1 always have records on table 2 and 3.

About speed, I don’t see why this could affect that. I don’t remember anything on the docs about it

[Kirk_Masden · Accepted solution]

SkrOYC:

One big table vs multiple ones

There’s more discussion of this issue here:

App Design: Multiple tables vs. Single table + multiple slices Tips & Tricks 💡

One spreadsheet table per “entity” (a set of things in the real world) is the norm in AppSheet: Every entity that you define (Job, Employee, Building) should have its own table (or sheet) within the document that you are connecting to AppSheet. Put more simply, it is often the case that a “view” (UX) will have it’s own table. I think this is good standard practice for beginners but there are potential drawbacks. When, for example, I built a flashcard app with a separate table for each “s…

In my case, I felt one table was better. In my app, certain calculations occur instantly if the data is on one table but not if it is on separate tables. But, I’m sure that are many pros and cons depending on the situation.