Latest Contributions by ZacharySutherby

Hello @GISUser74305830,  I am not reproducing this issue on my end, are you publishing your survey from the latest 3.13.251 version of Survey123 Connect? ... View more

Hello @LuisGarcia6,  Please see our Work with the Survey Manager sample available in our documentation for information on how to connect to your Survey123 surveys via Python.  ... View more

Hello @anonymous55,  There is an example available in ArcGIS Survey123 Connect that demonstrates how to use a JavaScript function to query a feature service and pull the data into the survey.  Here is another example that queries a hosted feature layer in Living Atlas and returns information from the service.  All that would need to be done is to switch the feature service URL with the one you are interested in, update the where clause when making the query, and add a token if your feature service is secure.  ... View more

Hello @Rice_GIS,  It is recommended to encode URL parameters. Encoding replaces invalid characters with the percent sign followed by their hex equivalent. Please see , https://doc.arcgis.com/en/survey123/reference/integratewithotherapps.htm#ESRI_SECTION1_7E0A66ACA8504EDE8CB0171C3C8A5760 for more information ... View more

Hello @PeterDelgado, That error seems like the report API is trying to generate the report and failing on generation maybe not so much on the initial API call. If you try running the report directly from the Survey123 web UI is the same error returned or does the report generate successfully there?  If the report generates successfully from the Survey123 web UI try setting the referer to https://www.arcgis.com.  ... View more

Hello @GrantZ,  Using regex(.,'[0-2][0-2][0-2]') would be one way to reach the regex you are looking for.    ... View more

Hello @GISUser74305830,  It looks like the XLSForm provided is using a submission URL and the survey may have been built based on an existing feature service. Just to confirm are the relationships between the parent layer and related tables 1:M based on globalID to GUID? Please see this documentation for more information.  ... View more

Hello @elpinguino,  Do you also have esriFieldTypeString set for the bind::esri:fieldType on the image question? If so is there a reason why it's set to String?    @BrettClark If you have nothing set in the bind::esri:fieldType do you still see the image not show up in the report?  ... View more

Hello @mroberts_troy,  Thank you for passing along the sample XLSForm and CSV! I've tested on my end with Connect 3.13.251 and I am seeing the pulldata() function bring in the correct information:  Just to confirm are you using the same version of Survey123 Connect? You can find the version by selecting the little hamburger on the top right (or your profile icon if you're signed in), and the version will be on the bottom right of the pane that pops up.  If you are using the latest version of Connect back in that menu that popped up when you selected the hamburger if you select Settings > click and hold on the title "Survey123 Connect Settings", this will pop up a Beta tab. In the Beta tab there is a toggle for "Itemset tools" if you enable that back in your survey along the bottom ribbon you will see an Itemsets button. Selecting that Itemsets button, on the bottom right you should see Tables/Views, in that box do you see the name of your CSV (rolespulldata) and if so do you see the CSV data in that table?  ... View more

Hello @JakeMatthys,  The way webhooks run in ArcGIS Survey123 is after Survey123 sends the applyEdits request to the feature service it then sends a request to the webhooks payload URL. This request to the webhook payload URL would be independent from your ArcGIS Enterprise organization and wouldn't show up in any ArcGIS Enterprise logging.  Depending on who your webhook provider is I would suggest checking out the logs for the webhook and see if either you are not seeing any run history for those specific records, or if there was an error in webhook execution. Both Integromat and Power Automate have run history logging and would be a good place to start.  If there are no run history for those specific records that could potentially indicate that Survey123 failed to send a request to the payload URL and would require more troubleshooting. If that seems to be the case I would suggest reaching out to Esri Technical Support and they will be able to assist with troubleshooting.  It would be good to know:  - If there is a pattern in the records that seem to not trigger the request?    - Is it the same user sending the records?     - Is it around the same time?     - Is there some consistency between the data in the records?    - Is it specific to a certain device?   -  Are the records being submitted in remote areas with limited cell service?  - If your ArcGIS Enterprise environment is behind a firewall are your field users using a VPN to connect?     - If so the request to the webhook should be made through the VPN, is it possible to obtain the web traffic from the VPN?  ... View more

Hello @vijaybadugu,  If you enable "Require update to the latest version of this survey" in the options for the survey in Connect the user will not need to refresh the My Surveys page to be prompt for the update, when the select the survey they will be prompt they will need to update the survey in order to continue.  ... View more

Hello @CeydiMendoza @JakeMatthys,  One option would be to use a custom JavaScript function to query the feature service and identify if the record entered matches any records in the feature service. From there you can put a constraint on the question you don't want duplicates to let the user know if that value has been entered already or not.  We have a JavaScript sample available in Survey123 Connect that demonstrates how to query a feature service. ... View more