Can I rename the Google "book" used by my app without the need to re-assign the table datasources?

I copied an app and Google, I am going to call it “book” since it is a collection of sheets. Instead of the copied “book” using the original name, it used the name of the first table. I seem to recall in the past when I copied an app and then renamed the “book”, the tables all had issues and I had to reattach the tables to the copied “book”.

It may not be a major problem but I have over 20 tables in this app and would rather not have to go through that pain. And I expect to have to do this many times as I acquire clients - copying the base app and date into a specific client application and locations.

So…is there some way I can rename the Google “book” that doesn’t require me to have to re-assign the renamed source to the application tables?

I have students change the names of the Google books all of the time. It doesn’t seem to affect the connection to the AppSheet app. AppSheet doesn’t seem to rely on the book name that we see in the Google sheets editor – though changing sheet names DOES cause errors.

Since google allows you to revert to earlier versions of a sheet with its version history you could try changing it and, if something goes wrong, go back to the previous version.

1 Like

Ok, I’ll give it a try. Maybe I did something slightly different in the past.

I hope I’m not giving you bad advice. Another approach might be to make a copy of the app and experiment with that. That way, even if something goes wrong, you don’t need to do anything to recover.

It is a copy I am messing with but expect to keep around. So if it goes sideways, I an delete and start over. I was just trying to save some pain upfront.

1 Like

I’d expect no problems. AppSheet itself refers to the Google workbook by an ID string that is independent of the file name and folder location, so you should be able to rename and even move the workbook without any reconfiguration of your app needed.


@Kirk_Masden @Steve

Ok, I renamed the sheet. It does appear that the Source is updated to the new name automatically…well in some places! Maybe just a matter of time for rest to catch up.

In each table, the Source Path under STORAGE section was automatically updated to the new name.

Screen Shot 2020-01-11 at 1.32.45 PM

However, in the summary view the source still shows the old name. Refresh, closing the app and even logging out didn’t resolve the source name there. I’ll see if resolves somehow over time.


That’s interesting. I hadn’t thought about how the “book” (that is, “source”) name might be represented inside of the AppSheet editor. It appears, though, that changing the name didn’t break the app so that’s good. Perhaps AppSheet just needs to improve the code that updates the name of the source to avoid displaying an incorrect name.

I suspect this is a flaw in that the Source for the summary view is set when the table is initially added but then doesn’t update when the name is changed. I’ll open a bug on this as it should be an easy fix.

A new table I added does show the correct name.