AppSheet extracts tabular column structure from your spreadsheet, and works best when the spreadsheet has regular tabular data: the first row has column headers and the remaining rows are data. Extraneous data, drawings, charts, etc. may cause problems. Here's how you understand and control the process.
In the Data section of the Editor, you see a few simple controls. The Browse Data link opens the spreadsheet in a separate browser tab. If you are using Google Sheets, this allows you to edit the Google sheet in one tab while you see the effects on your app in the AppSheet tab.
If you click on the Preview Data link, you see the first few rows of the spreadsheet conforming to the column structure that AppSheet has extracted. Each column has a header name and a data type. Also, one of the columns has been identified as the unique key. This choice is very important: the unique key helps AppSheet synchronize changes made in the app back to the spreadsheet.
Every time you refresh the Editor page, AppSheet checks your app and shows error, warning, and info messages at the top of the page. Wherever possible, AppSheet tries to automatically inform you of any problems and automatically fix them.
When you change the structure of the spreadsheet, AppSheet notices the difference between the spreadsheet and what it expects. So it gives you a warning that there are more columns or fewer columns than the Editor expects. If you are editing the app on our web page, it will try to automatically pick up the new structure. If the extracted column structure is not what you expect, or there are errors/warnings you want to act upon, you would typically make changes to your data in the spreadsheet and then click "Regenerate" for the relevant table in the Columns tab.
You can also choose to switch to another spreadsheet. There are several reasons you might do this. For instance, if you start with an example data set for experimentation and now you want to switch to the real data, which might have a different structure, you'll need to regenerate. Another case would be when you want to switch to a different spreadsheet that has identical structure (eg: switching from test data to production data). Finally, you may realize that you need to add or take away a column in order to properly capture the data. In all cases where there's a change in the number of columns, AppSheet detects the new column structure and reacts appropriately to it.
Using a Specific Worksheet
In the Editor > Data > Tables tab, when you look at the details for the Tables in the app, you can provide a specific worksheet name in the "Worksheet Name/Qualifier" field.
If a worksheet with this name is not found in the referenced spreadsheet, AppSheet will default to the first worksheet.
Using Multiple Spreadsheets
In the Editor > Data > Tables tab, click on "+Table" to choose another spreadsheet. If you need to use a worksheet from the same workbook you are already using in your app, simply define the sheet name (case included) in the Worksheet Name/Qualifier field. The sheet automatically gets added to your app when you save your changes. You can now define control views over this data as well.
Note that you'll need to create a new UX view pointing to the new spreadsheet to get that sheet's data to display in the app.
See a good example of multiple tables and cross-table references in the Order Capture sample.
Verify your users’ identities
Enforce identity verification to prevent third parties from impersonating logged-in users.
Set up identity verification
Remind me later