I am currently trying to create a bot in my appsheet that takes the info provided by the user and creates a label in Google Sheet for printing, although the bot is able to create de Sheet and it is acessible via Google Drive, when trying to open it via appsheet itself it gives the error: Remote Server: File not found.
The template and the generated files are hosted on Google Drive, the spreadsheets are hosted on Microsoft, i followed Google article on how to create files with a bot.
Sorry for the bad English as it is my second language.
Hello @zatti,
Please allow me to research on this and I will get back to you shortly!
Hello @zatti,
Based on the screenshots you provided, the issue is a path mismatch between where the bot is saving the file and what your “FileName” action is writing into the spreadsheet.
AppSheet’s file handling is very sensitive to folder depth. When your data source is on a different provider (Microsoft) than your file storage (Google), the app loses its “automatic” relative pathing.
The Problem
In Image (3), your File Folder Path is blank. This means AppSheet is saving the file to the default folder (usually /appsheet/data/YourAppName-NumericID/Files).
In Image (1), your expression is: CONCATENATE("/Master/Files/", "ENTRADAMAD_", [UNIQUEID], ".xlsx")
The leading slash / and the extra folder /Master/ are likely the culprits. AppSheet treats paths as relative to the app’s root folder. If the file is physically at Files/Label.xlsx but the database says /Master/Files/Label.xlsx, the “Remote Server: File not found” error occurs because the app is looking inside a folder named “Master” that doesn’t exist in the eyes of the File Store.
The Solution
1. Standardize the Bot’s Folder Path
In your File Creation task (Image 3), explicitly tell the bot where to put the file so there is no guesswork:
-
File Folder Path**:** Enter
"Files"(with quotes). -
Disable Timestamp**:** Keep this ON (as you have it) to ensure the filename matches exactly what you calculate in your action.
2. Fix the Action Expression
In your Run FileName Action (Image 1), update the expression to remove the leading slash and the “Master” directory (unless you specifically created a folder named “Master” inside your AppSheet data folder):
Corrected Expression: CONCATENATE("Files/", "ENTRADAMAD_", [UNIQUEID], ".xlsx")
3. Verify the “File Store”
In Image (3), your File Store is set to “Default”.
-
Because your spreadsheet is on Microsoft, “Default” might be trying to point to OneDrive.
-
The Fix: Click the dropdown for File Store and explicitly select your Google Drive connection. This ensures that even though the data is on Microsoft, the “File” column knows to look at Google Drive to retrieve the document.
I hope it helps!!
2 Likes
Hi @Shourya_Tomar!
Thanks for the return, so, since yesterday i tried to do somethings to make it work, so let me share with you what i found out:
- Appsheet doesn’t let me save to Onedrive, or select Google Drive as the Default on File Store, please refer to picture 1;
- After some trial and error, i decided to download that .xlsx and upload it to Google Drive, changing the Data directory from Onedrive to Google Drive (just for that one spreadsheet), after that change, it immediately started working trying to open the file via appsheet;
- Regarding file storage, there is absolutely no option to set the default file provider, only supporting Google Drive, as not only there is no way to set the default provider within the bot (Image 1), there is also no option to set the default folder on the appsheet default, trying to put something like //Onedrive/Master, just creates a folder in Google Drive called Onedrive/Master/, although, in the Data tab, when opening the table settings it shows being stored in //Onedrive/, please see picture 2.
Again, thanks for your help! This issue is solved.
1 Like
Here’s the doc:
This makes no sense at all.
Flat-out wrong.
What’s with these asterisks?
Wrong. The location of the spreadsheet plays no role in the default file save location. The default location is chosen according to your app’s login provider.
Here’s the doc:
@Jose_Arteaga, someone needs to review @Shourya_Tomar’s posts before they go out. Bad information is worse than no information, especially in the age of AI that might ingest and regurgitate it to others. @Shourya_Tomar is an official representative of Google and should not be posting misinformation.
3 Likes
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.