In the last few updates I believe Appsheet changed how it deals with Google drive paths. Previously I've had to set the path to a specific pdf as
appsheet/file/xxx.pdf
in order for the application to recognize it. But just today one of the users told me they couldnt open all the PDFs, and with some checking I realized the path has to be
file/xxx.pdf
Anyone else noticed this, or was there an announcement about this somewhere?
You're definitely onto somethingโthe behavior of file paths in AppSheet has quietly shifted recently, and you're not alone in noticing it. Here's a breakdown of what's going on:
---
๐ What Changed?
Previously, when referencing files in your appโs Drive folder, paths like appsheet/file/xxx.pdf worked fine.
Lately, users (including you!) are finding that only the file/xxx.pdf prefix works reliably.
AppSheet has updated how it interprets relative paths in file-columns and automation-generated attachments, essentially dropping the appsheet/ segment when accessing content.
๐ข Is This Official or Intentional?
AppSheet hasnโt explicitly announced this change in their release notes or documentation. But similar path-related updates have occurredโlike Google Drive URL handling, which officially shifted away from drive.google.com/uc?... links in early 2024 .
So while the change you're seeing isn't documented yet, it's consistent with ongoing refinements to file integration.
๐งฉ What You Need to Do
1. Update your file paths
Everywhere you previously used:
appsheet/file/xxx.pdf
replace it with:
file/xxx.pdf
Now, AppSheet will recognize and open the files correctly.
2. Check automations and actions
If youโre using bots, "Open File" actions, or URL formulas that generate PDF or image links, make sure they use the file/ prefix.
3. Regenerate previews or republish
To ensure changes take effect:
In AppSheet, regenerate the schema.
Republish or let users perform a full app sync.
โก Why This Matters
The appsheet/ prefix was always a quirky implementation detail and not well-documented. Removing it streamlines the path systemโand while helpful in the long run, it's caught many people off guard.
โ Suggested Path Forward
Normalize your paths nowโupdate any hardcoded appsheet/file/... references.
Test all linked files to confirm they open.
Monitor your users' experience, and be ready to update automations and UX elements if issues reappear.
๐ Final Note
You're absolutely right to flag thisโit highlights a gap in AppSheet's feedback loop when they make infrastructural changes. We may see an official note in the near future, but in the meantime, switching to file/... is the best way to stay ahead and prevent broken links.
Hi @shinze
From my humble perspective, it has always been file/xxx.pdf
This is deducted from the default app folder:
And from this, the relative path to your file:
For reference:
Images or files that do not load - AppSheet Help
User | Count |
---|---|
20 | |
16 | |
4 | |
3 | |
2 |