Intermittent errors - Ghosts from previous table designs

[RedVox]

At one point in the history of an app, I decided to rename a column.  The column name was referenced in a doc template, so I also made the needed changes to that template.  Now, when saving the app, about 10% of the time, I get an error message telling me that my template is referencing a column name that doesn't exist (the old name).  I've tried replacing the template, but that didn't help.

It seems to me that somewhere, within the app, there must be something that still holds the old column name.  Since it loads fine about 90% of the time, and since I have checked all the nooks and crannies and found no remaining reference to the old column name in any editable spot, I feel like this is a bug.  Is there any way to put my app through a rinse mode that will eliminate whatever historic references to the old column name that appsheet is hanging on to?

[Metworks_IT1 · Accepted solution]

Hi, do you have bots sending emails? if you click on the "go to problem", it should take you to the bot's task, check the template file and update it.

[Metworks_IT1 · Accepted solution]

Hi, do you have bots sending emails? if you click on the "go to problem", it should take you to the bot's task, check the template file and update it.

[RedVox]

This problem is happening AFTER updating the template file multiple times.

[Metworks_IT1 · Accepted solution]

in your app, go to settings - information - app documentation - at the very bottom of the page, there's a link that will generate the documentation for the app - search in there if there's any reference to the old column name.

Or use this link:  https://www.appsheet.com/template/appdoc?appId=__Your  app ID here___ 

Alternatively, I would remove the template files from your bots and recreate them.

Hope you'll figure where the error is coming from!

[RedVox]

Bingo!  Thanks very much.  By looking there, I found the reference in a disabled bot.  Hopefully deleting the bot fixes the problem.  

[RedVox]

Actually, I just had the problem again, and this time, the field name showing in the error does not occur anywhere in the documentation.