I published a new article about data organization for teams. It is available in the AppSheet help docs. Check it out!
The article describes how to use a Google Shared Drive or an O365 SharePoint site to store data for your team. Using a shared data location can be helpful to ensure longevity beyond a single userโs cloud account. It also makes transferring apps between owners a breeze.
The article focuses on using a single shared drive for the whole team. The same process could be applied to use multiple shared drives as well.
Hi @Derek, in the reference article for setting the SharedDrives, the terminology to use is still TeamDrive.
https://help.appsheet.com/en/articles/2615244-working-with-google-team-drive
Where the root folder path as per the help article is:
/[TeamDrive]MyTeamDrive/appsheetdata
Last week, I have just connected my team to the SharedDrives using the above โTeamDriveโ as connection name and it was working fine.
However, I wonder if this connection using TeamDrive as the connection name would be depreciated in the future and what will be the impact to the connected Apps?
Hi @Heru,
That is a great question to raise. On May 31, 2019, the โTeam Drivesโ feature of Google Drive was renamed to โshared drives.โ
Backwards compatibility is always a priority when making updates to the platform. If the AppSheet terminology is updated in the future, the change will be made in a way to ensure existing root folder path definitions continue to work as expected.
@Derek, Last year when the name was changed from TeamDrive to SharedDrives, the functionality is the same, except for any excel files linked to other excel files and any links pointing address using a TeamDrive name - we have to change it manually to get the links back to functions.
Now, reading your response, I am happy since it clarifies my concern.
Thanks.
Hi @Derek, an update today as one of my new member team being set-up for the SharedDrives was having difficulties to connect to the drives using the root folder path similar to below with [TeamDrive]:
/[TeamDrive ]MyTeamDrive/appsheetdata
Until he report back and I just blindly test with a new connection root folder path with SharedDrives as the name, see below:
Unfortunately, it works.
So I imagine that the next time connection to be made to SharedDrives shall use this new [SharedDrives] as folder root path naming, at least, thatโs what I will tell my team to do.
Hi Heru,
Thanks for posting. Iโm surprised that using [SharedDrives] worked as that is not a supported keyword.
The supported process is described in this article. The syntax is:
/[TeamDrive]MyTeamDrive/appsheetdata
I would recommend looking for other areas where there could be an issue. Possible areas to check are the name of the Shared Drive and your team mateโs permissions on the Shared Drive.
There might be an issue, but I have to recheck and get back to you later.
When tries to use the syntax /[TeamDrive] as below:
He got a new folder with [TeamDrive] in his MyDrive:
People that already connected last week still can access the TeamDrive designated for AppSheet, only new people could not.
And I was reporting too early yesterday, actually [SharedDrive] did not work, and just producing a new folder like this in his MyDrive:
I will try to create a dummy account and report back to you.
Update:
He was able to connect to TeamDrive, with steps as follow: After remove appsheet access on their google account, logout from appsheet, clearing cache, log-in back again to AppSheet, make sure default folder changed, and try to copy one app.
Hi Heru,
Iโm glad your team mate got the connection to a Shared Drive working!
@Derek Can you please clarify the syntax that is working ATM? The docs are outdated.
[TeamDrive]
or [<Shared drive name>]
?/Shared Drives/Drive Name/...
becomes /[SharedDrives]DriveName/...
?[Shared drives]
with the root <Drive Name> as 1 path element i.e.
[Shared drives]/โฆ`?[
& ]
for root Shared drives
?And please update this document because that is the first place to look no the forums.
below is what I have been using:
A new folder with the app name will be created for each of the app - inside my Appsheet shareddrives forlder.
Is you Shared drive called APPSHEET
? Iโm still not sure if we should keep spaces or not; our drive is called Engineering Corporate Identity
for example. Iโve tried both versions though and neither worked.
Can you not just refer to full path for files/images in shared drive w/o moving the app to the same drive? We have many drives which I will need access to and links to folders doesnโt work.
Yes.
Iโve just tested this and you should be able to connect with the following:
/[TeamDrive]Engineering Corporate Identity
Hi @Heru
Thanks for the good tips.
I also tried it and it behaves differently depending on whether the folder already exists in Shared Drive or not.
As you mentioned, I can create a new app in a folder in Shared Drive.
A new application was created under My Drive with the name of Defalut folder.
ex)
My Drive > [TeamDrive]AppSheet > Sandbox-xxxxxxxxxxx
Hi, this is not working for me.
Changed my account settings as:
But every time I create a new app, It keeps generating a new folder inside My Drive named [TeamDrive]AppsheetRepo including app definition.
Any hint?
Hi @tsambruni,
The trailing slash may be unnecessary.
/[TeamDrive]AppsheetRepo/
โ
/[TeamDrive]AppsheetRepo
Youโre right, thanks!
Thank you so much for testing this!
I still cannot get it to work. Iโm using the full path /[TeamDrive]Engineering Corporate Identity/Icons/[Team Name].png
to an image but it never loads. I canโt figure out if itโs some sharing issue.
Can you access any images/files on shared drives other than the one your App data and the spreadsheet is in?
Yes, because I am the super admin.
That partially answers my questions.
What about relational databases, can you use more than one table and populate foreign keys or does it only work with flat/table style data? I am trying to replicate forms on another platform that has some data, I believe, is in different tables
You might want to see an explanation on data with this reference: