Latest Contributions by ElliottPlack__SHA_

Solid! Thanks for this inspiration @KenBouchard !! The solution is to first write an attribute expression, then call that in text box with a link the Survey123. I can confirm it also works with Survey123 field app URLs (FYI @Ismael ). I was unable to get this working in Field Maps on iOS when I had the entire URL and button generation in one Arcade expression, returning text (although this works fine on the web). Using your workaround, I wrote the following attribute expression for our Park & Ride usage survey:   // Define the Survey123 item ID var surveyItemID = "55555555555555555555555555555555"; // Create the parameters dictionary var params = { itemID: surveyItemID, "field:pnrSurveyed": $feature.COMMON_NAME, "field:bikeRackCount": DefaultValue($feature.BIKE_RACK_COUNT, 0), "field:bikeStorageCount": DefaultValue($feature.BIKE_STORAGE_COUNT, 0), "field:truckSpaceCount": DefaultValue($feature.TRUCK_SPACE_COUNT, 0), "field:motorcycleSpaceCount": DefaultValue($feature.MOTORCYCLE_SPACE_COUNT, 0), "field:kissRideCount": DefaultValue($feature.KISSNRIDE_GEN_SPACE_COUNT, 0), "field:INCOMING_GLOBALID": $feature.GLOBALID, "field:lotType": $feature.PNR_TYPE }; // Concatenate the base URL with the encoded parameters var surveyURL = "arcgis-survey123://?" + UrlEncode(params); return surveyURL;     Then, take note of the expression number of the url. In a new text box in the popup I added the following HTML (feel free to reuse):   <div style="padding: 10px;"> <a href="{expression/expr999}" target="_blank" style="display: inline-block; padding: 0.5em 1em; font-family: Avenir Next, sans-serif; font-size: 1em; color: white; background-color: #28a745; text-decoration: none; border-radius: 0.25em;"> Collect Survey in Survey123 Field App </a> </div>       ... View more

Ismael Chivite‌ very cool to see this advanced functionality in S123. One use case I am evaluating it for is preventing duplicate submittals based on a unique key in a parameter URL. This use case would mimic how, say, a Survey Monkey form can only be taken one time. I'd have to pull the previous data and check if a key exists already, then use some kind of constraint to prevent another submittal. Kind of out of box thinking here, but maybe it would work. Please tell me if you think this is possible: Background Public-facing web Survey123 form Typical Survey123 steps User clicks a Survey123 URL with parameters in an email that prepopulates a read-only text field in the form (effectively a foreign key) User fills out the web form. Prepopulated key resides in collapsed group. Submit, done. Duplication check steps User clicks the URL in the email again. Survey123 pulldata checks submittal FS to see if the prepopulated key is already in the service If the key is there, it prevents submitting the form my making an impossible constraint on a read only field in the survey, or perhaps hiding some group that contains the responses. ... View more

It appears that we're describing the same issue over here in this thread. I posted an example there of the problem. I'm happy to provide a schema if you can help diagnose the issue. ... View more

I have noticed this behavior as well. I thought it was an issue with the map service until I saw the popup works normally when clicking from directly on the map Here's an example web app where you can see the problem. Click on one of the polygons to see the popup. Then click on the info summary group to expand, and click on one of the features there. You can see the differences in the domains. I wonder if the Info Summary widget has its own popup configuration that is not (yet) user configurable. ... View more

Good news! A contributor on GitHub added a pull request that adds the multiple field functionality. ... View more

It turned out to be a browser cache issue. Reset it and it works now. ... View more

Thanks. Does the '' test work on integers or float/double variables? ... View more

Kelly Gerrow‌ Great news that the bug is being investigated! I reported an issue through a support case #02127148 that led to that bug being cited, back in June 2018.  ... View more