What are the resrictions on Linked Content in Survey123 Connect?

[Scott_Sambell]

Hi.  I'm trying to create a workaround for the issue of JavaScript functions not being able to be used in forms shared to other organisations (which, itself, is a workaround to the issue of hyperlinks not working in Survey123 webforms)

I have decided to try to publish a copy of the form on the AGOL portal that the users are hosted on, but when i look for the hosted CSV which i need to add as linked content, its not there.  I looked around online but can't find the rules with restrictions with linked content.  Do they have to be owned by the owner of the form or just be in the same org and group? 

Thanks!

@IsmaelChivite any ideas?  I've really gone down a rabbit hole on this workaround 😬

[CodyPatterson]

Hey @Scott_Sambell 

In my experience, the CSV must be owned by the owner of the Survey to work with it. If you are the administrator, you may need to change the owner over to you for testing. I believe that it won't appear as an option until ownership is transferred over.

Cody

[abureaux]

You shouldn't need to be the owner of the survey and the hosted content. My account hosts all constant on our Portal (e.g., CSVs for External Selects in S123). My other developer uses all these CSVs in their designs.

The only key should be that the CSV is shared appropriately. If you don't see it in Connect, then it likely isn't shared properly.

[CodyPatterson]

Hey @abureaux 

Thank you for sharing that, I think most of my situations have been owner-shared, so it always falls into the category of your second paragraph, more than likely just hasn't been shared properly!

Cody

[Scott_Sambell]

Thanks for the responses Cody and abureaux. 

I ended up publishing the form and the CSV on the users' portal and setting up an FME process to keep the CSV on the items' portal and the original CSV on the users' portal in sync. (they have to be real time synced for this system to work). Thankfully, i didn't have to also publish and maintain a replica of the hosted feature layer on the users' portal, as it is possible to point the form at a feature layer on another portal as long as it is shared in the same group - but you cannot use a hosted CSV as linked content if it is hosted on a different portal to the form. 

This has been a crazy workaround but it seems to be working now.