So I have a reference to another table that d...

[Joshua_Giles]

So I have a reference to another table that does nothing but act as a referenced list for a drop down in my form. For some reason after every other save those virtual columns revert back to the type “text” instead of “lists” which produces an error. I have to change it back to the list type every time and my error goes away and the app acts as it should. Why does this keep changing from list to text? This has never happened to me before, even though I’ve referenced lists exactly like this multiple times.

[Steven_Coile]

What is the App formula for the virtual column?

[Joshua_Giles]

@Steven_Coile

'REF_ROWS("“DLSWHSE” Daily Time Sheet", “Service Request #'s:”

and

'REF_ROWS("“DLSWHSE” Daily Time Sheet", “Activity #2 Work Performed:”)

The specific error that I am receiving is:

“Column Name ‘Related “DLSWHSE” Daily Time Sheets By Activity #2 Work Performed:’ in Schema ‘Work Performed Categories_Schema’ of Column Type ‘Text’ has an invalid app formula 'REF_ROWS(”“DLSWHSE” Daily Time Sheet", “Activity #2 Work Performed:”)’. Unable to find table ‘’"

Like I’ve said, I’ve always been able reference rows like how I’m doing now. None of the settings are different (that I can find, and I’ve definitely looked). The only steps that I’m taking:

1.) Created a data filler tab in my excel file. 2.) Added those tables to my data table pages 3.) Turned the column I wish to turn into a dependent drop down to a “Ref” type. 4.) For the, “ReferencedTableName” drop down, I’ve selected the data filler table 5.) Everything else stays the same. Click “okay” 6.) Save

Upon reload I get the error referenced above. However, I can manually change the virtual column that the reference created from “text” to “list”. Click save, and boom the problem is fixed and the referenced row acts exactly how I want it to (a dependent drop down). However whenever I do anything in the app the virtual column type changes itself back to “text” and then produces that same error.

[Steven_Coile]

@Joshua_Giles REF_ROWS("“DLSWHSE” Daily Time Sheet", “Service Request #'s:” has too many quotes. Remove the quotes from your worksheet (and then table) name.

Specifically, change:

“DLSWHSE” Daily Time Sheet

to:

DLSWHSE Daily Time Sheet

[Joshua_Giles]

@Steven_Coile So I thought that, that might be the issue, and went to remove them from my tab name. However, once I did this, all of my existing formula and formatting for the other columns are deleted. Is there any way to not have to reformat everything? (Basically starting from scratch and the app was essentially finished.)

[Joshua_Giles]

Also, @Steven_Coile that totally fixed it. :’( but now I’m looking at the rest of my day rebuilding what I already built :’’(

[Steven_Coile]

@Joshua_Giles The best way I’ve found to rename a worksheet without losing AppSheet configuration is this:

1. In the AppSheet workbench, go to Data / Tables, to the configuration of the table you want to rename.

2. Change the name of the table in the workbench as desired. Do not (yet) change the name of the worksheet.

3. SAVE the change. Note that this will result in errors if your configuration otherwise refers to the old table name (likely).

4. After the save is complete, correct any errors by updating your configuration to use the new table name and get your app working again. Still do not yet change the name of the worksheet.

At this point, you may stop. Changing the name of the worksheet to match the table name used by AppSheet is not strictly required, but you will likely want to change the worksheet name to avoid confusion in the future. To do so:

5. Rename the worksheet as desired. Doing so is likely to break your app until you complete the steps below.

6. Again in the AppSheet workbench, return to Data / Tables, to the configuration of the table you’re renaming.

7. For Worksheet Name/Qualifier, choose the new name of the worksheet.

8. SAVE the change. When the save is complete, the app should again be working, and using the newly-renamed worksheet.

Note that in the course of this process, the table configuration is likely to be reordered among the list of table configurations in the AppSheet workbench. This reordering is not significant.

In essence, the process above amounts to: (a) renaming an AppSheet table; and (b) connecting an existing AppSheet table to a different worksheet (that happens to be the old worksheet, but with a different name).

[ntrejo]

To add to what @Steve explained.

For step 4 (‘correct any errors by updating your configuration’) you may encounter that there are many expressions throughout your app (visible-if, require-if, computations, slices, views, etc)

You may find really helpful the automatic documentation generated by AppSheet, which you can download as pdf and perform a text search (Ctrl+F). In this way you can find where the old table name is used

In this thread you can find more info about Documentation.