Performance - add table as read-only or just don't add?

If I have google WorksheetA and WorksheetB with my AppA built off WorksheetA, but I want to add a read-only TableB1 for AppA from WorksheetB, which has 8 tables in total. Is it best to just add TableB1 as read-only and ignore (in AppA) the other 7 tables in WorksheetB or add all WorksheetB tables as read-only.

Is the answer the same for where TableB1 needs to be added to AppA as a dynamic table?

I’m just starting out on exploring cross-worksheet, cross-app links.

Better your workbook only include worksheets your app is using. AppSheet has to load the entire workbook even if only one worksheet is used.

If your workbook contains worksheets the app isn’t using, do not add the unused worksheets as tables in the app.

Remember to remove all blank columns and rows to maximize performance.

A Google Sheet is likely to perform better with AppSheet than Excel.

1 Like

Thx @Steve That all makes sense. I knew Appsheet had to read the entire workbook, so wondered whether specifically telling Appsheet that the unused 7 tables were read-only was a good idea, rather than letting Appsheet do something else that I didn’t know about.

1 Like