Edge Delivery Services - Forms - not able to connect to google drive

[brwayne]

Hi,

Did anyone try out the forms solution for EDS.

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/edge-delivery/bu...

I'm trying it , but I'm stuck at the point, where the chrome extension tries to access my google drive to publish the files.

Always gives a 404 error.

Any insights will be helpful.

Thanks.

[Karishma_begumSh]

Hi @brwayne 

You're getting a 404 likely because of one of these issues:

1. Wrong folder structure – Make sure your Drive has fstab.yaml, form.html, and metadata.json in the root.
2. Drive sharing – Share the folder and files as "Anyone with the link" (Viewer).
3. Sidekick not linked properly – Check if fstab.yaml correctly points to your Drive folder.
4. Google account mismatch – Ensure you're logged in with the right account in Chrome.

Check the Console logs in DevTools for more detail.

Hope this helpful.:)

Regards,

Karishma.

[brwayne]

thanks, @Karishma_begumSh ,

only thing that worked was giving anyone view access.

This is not part of any documentation anywhere.

https://www.aem.live/developer/tutorial

or

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/edge-delivery/bu...

also, your first point says to have fstab form and metadata in drive. but isnt that supposed to be on the repo?

the documentation only talks about fstab.yml to be updated in repo. In any case, it atleast started accessing.

but then ran into some other issues, like file type not supported. since i was using google drive, i had to convert the docs to google docs, then it was able to access and i was able to edit and publish.

[kautuk_sahni]

@brwayne Just checking in — were you able to resolve your issue? We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!