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; } } }

S123 Custom URL Scheme and Relevant Expressions

TonyViveiros

Hello...is passing field parameters from Collector to S123 no longer possible for fields with a relevant expression? This no longer works for me. I also checked previous surveys that worked but now do not (I haven't changed anything). I'm using S123 3.3.64 but also tested with 3.4.96 without any success.

Thanks.

Encontre mais publicações marcadas com

Accepted answers

Anonymous User

Hi Tony,

Yes that is correct, it is no longer possible to send values via custom url to questions that are not relevant when the form loads. We used to store values in fields that were not relevant, which was wrong and considered a bug as when sending the survey those values got stored in feature service. This was fixed in a recent release which means now the question must be relevant on load to store the value.

Phil.

All comments

Anonymous User

Hi Tony,

Phil.

TonyViveiros

Hello Philip,

I don't quite understand why this functionality was considered a bug. I've written the url scheme to pass the parameters from collector to s123 because I wanted those values to get stored in the feature service. My survey is a lot more cluttered now because this ability was removed. For example, we have a check s123 workflow that is used to audit forest renewal assessments. With a previous release of s123, the auditor would identify the trees on the site being assessed and compare those against what was originally assessed. Doing so only brought up the original surveyed tree numbers (passed via url) and a question for the auditor to record their tree numbers for the species selected. Now I have to show all originally assessed tree number values up front as partially illustrated below. This complicates the survey as most of the time only a few species exist at the site yet all these 0 values now get displayed on the survey for trees not present. This workflow is further described in the following ArcNorth News story.

Any suggestions on how I could simplify my survey to the way it was previously when this 'bug' existed?

Thanks.

Tony Viveiros

Impact of no longer storing values via custom url to questions with a relevant expression...a cluttered survey.

dougbrowning

Create a set of hidden fields - then pass the values to them (or use Notes if you want the user to see the values). Then base the relevants off these hidden fields. You can then even default the hidden in case values are not passed in.

TonyViveiros

Thanks for the tip Doug. That worked.

Tony

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.