nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Better separation of surveys from different portals in survey123 connect

MarcelBeckmann

We are working with 3 Portals (Development, Staging and Production) and sometimes with ArcGIS Online for public access. Therefore we publish our surveys to different portals with survey123 connect. When switching from one Portal to another, I still can see the surveys from the portal where I am coming from. Some Surveys are even double in my survey overview. So I do not know which survey is from which portal!

I would be super convenient to see which Survey is from which Portal. Either by grouping them in the overview or by taps. Or anything else.

And also the xlsx-Forms. It would be really handy to also keep them separate portalwise. So you can keep different development stages of different Portals.

Najít více příspěvků označených jako

Connect

Status: Otevřít

Komentáře

MarcelBeckmann

Just came another "Problem" when sharing a survey to different Portals: I want to use an existing Feature Layer with my survey. So in the xlsx-Form I can provide a form_id and an submission_url. At least the submission_url is of course different for different portals. That is another reason why it would be super handy to have different xlsx-Files for different Portals.

AnthonyRyanEQL

If you have many xlsx files for each environment, then managing changes across them would/could be a nightmare (in my case it could be up to 7 portals (3 AGOLS & 4 Enterprise))

We use python and Azure DevOps pipelines to publish our surveys, and the code updates the xlsx file with the target url to the portal being deployed to. We find having one set of files easy to manage.

MarcelBeckmann

Hey @AnthonyRyanEQL,

thank you for the hint. Unfortunately I am not a professional software developer. At least not yet.

Anyways the usage of python and Azure DevOps pipelines sounds very interesting. But how can I imagine this? You host one xlsx file and the python scipt in a git repository, the python script opens the xlsx file and manages the portal-specific stuff like submission_url and the pipeline publishes the xlsx against the portal of your choice?

If you could lay out a bit more details this would be great. Thank you.

MarcelBeckmann

Another annoying thing is, when I want to publish the same survey against multiple Portals, I always get the following ErrorMessage when Publishing to a different Portal: Item does not exist or is inaccessible.

Then I have to rename/delete the .itemInfo File of my survey as described in this post: https://community.esri.com/t5/arcgis-survey123-questions/getting-error-400-item-does-not-exist-or-is/td-p/1285815

Připojte se k diskusi

Přihlaste se pro psaní příspěvků, sledování obsahu a další. Jste tu noví? Zaregistrujte se zdarma.