Latest Contributions by MichaelBrown4

‎04-09-2021

Looks like we see the error in Console, but everything is working correctly with our webhook. Thanks!

‎04-05-2021

It's going to a company webhook server we developed a while back. It's been working great for sometime now. I can send you the URL in a private message. I don't see any other errors in the console in the Network section. Thanks for the prompt response. I'll try and provide any additional info you need! Mike

‎04-05-2021

Hello, I am getting some errors from Survey123 regarding the webhooks. When I watch the Console in Chrome, it tells me that 'serverPostWebhook' url params is not valid. When I inspect the elements called out in the Console, they all point back to https://survey123.arcgis.com/share/v3.12/app-commons-v3.12.17.chunk.js Is this a problem with Survey123 or something on our side? We are running ArcGIS Enterprise 10.7.1 and the survey is published in the latest 3.12 version. Since sometime around 4/2/2021 I've found none of our forms have been sending Webhook payloads correctly.

‎03-26-2021

Awesome, thank you for the note on this. I've been eagerly awaiting using the feature layer for dynamic lists. I have many forms that are "identical" across many projects in a program I lead and we have to manually manage the pick lists for each form individually. Many times, the different forms have the same pick list (i.e. people's names) and when a new list item is added/removed/modified, it's a lot of re-publishing and coordination...inherently creating quality issues as things can get missed or incorrectly executed. My hope is to have a feature layer(s) where we can store all the list values, have a Survey123 form that manages said values, and ultimately have our forms read dynamically from that. Then our users can manage what values show in their choice lists themselves and we can use filters/queries on the feature layer to align to the appropriate project. Can't wait for May!

‎03-26-2021

Thanks for the info on this. In the meantime, I should be able to use the Python code I've seen posted to update the Media folder CSV file correct? Thanks again, Mike

‎03-25-2021

This has broken a few questions in many forms I have out for our teams to use. We have a select_one and a select_multiple pulling from a choice list that has values like "00", "09", "10", etc. I'm able to do the null/calculate field trick just fine for the select_one question, but not sure how I can fix the select_multiple. It should be creating a string like "01, 04, 10, 99" and is instead creating "1, 4, 10, 99". Do you have any suggestions on how to fix this? Besides me, others at my company had field teams and others working where these kinds of values get used in downstream automation workflows that essentially broke when this happened. Is this something that will be logged as a BUG going forward or something the users need to work around correcting? We need to decide if we should be investing in making changes to our automation code to handle this or if we can wait/limp along until a formal change is pushed out. Thanks for all your help and responses around this. Mike

‎03-25-2021

Thanks Zach, I've tried removing from the Media folder and re-publishing, but still finding that the Linked Content CSV is not being respected and not being used for the choice list values. The Field App is working correctly actually, it's the Web Form that is not working right, it continues to reference the Media folder CSV and not use the Linked Content CSV.

‎03-25-2021

I just recently started seeing this problem in the Field App, but believe the Web Form to be OK. I can't say if it's new or not, but my users just started reporting that the leading zeros are being removed from select_one and select_multiple questions. I tried a few things like setting the TEXT field type and using the =TEXT() function, but when I test in connect, I can see the values are coming in as integers still, with the leading zero dropped. See screenshot below. Is there another way to do this?

‎03-25-2021

I'm experiencing the same issue as the original poster. I have the exact same setup, using select_one_from_file and pulldata() that reference a linked content CSV and the web form does not update to reflect the latest updates to the CSV file on ArcGIS Enterprise. When I inspect the form loading in the web, I can see it's grabbing the CSV from the media folder, which is old and out of date, and not referencing the linked content CSV. Here is a screenshot of how the web form is still trying to pull from the Media folder even though there are no files there and I am using Linked Content.

‎03-25-2021

I'm trying to use a select_one_from_file and pulldata() with a linked content CSV hosted in ArcGIS Enterprise and I'm finding that the web form is not reflecting updates to the CSV file. Is this functionality possible? If so, is there a certain way I need to configure this to work? I am using the latest version of Survey123 (3.12). I can only get the web form to show the changes when I go to connect and choose to download the linked content CSV and then re-publish the survey. Any help would be greatly appreciated. Thanks in advance! Mike

‎01-06-2021

We have some workflows where we use Survey123 to submit and then edit a record, where different QA managers or similar update information about the submission in dedicated forms for their step of the workflow. To be clear, all forms in the workflow edit the same record from the same feature layer. We have been using the Username field type in all of these forms to track who the "last submitted user". We do this because we have code that touches the record/data very quickly after form submission (webhook) and cannot rely on the last edited user to see who that user was. For some time, this has been very reliable and every time a user submits a form in each step of the workflow, their username is populated correctly. Just recently, seemingly about mid-December 2020, this is no longer working as it used to. Instead, the Username is not updating after the initial form submission. Meaning, we capture the username of the original submitter just fine, but each of the subsequent forms that submit/edit this record do not update this field and we just see that original submitter in the data. It's as if the Username field type does not update if there is already a value in there. I can confirm if I set the value to NULL then load the form, it will grab the username. ## Update ## I did some additional testing and found that this bug occurring when I use the "version=latest" url parameter in the web form. The Survey is published in version 3.9. Setting the the version parameter to "version=3.9" gets rid of the bug...the username updates to the current user submitting the form. We are using ArcGIS Enterprise 10.7.1 Any help would be greatly appreciated. Thanks! Mike

‎08-25-2020

Thanks Albertus, but I believe there is a problem with that scenario. Both the form and feature layer need to be shared to the Group so the user can use and submit data through the form. Because my feature layer is used elsewhere with full permissions in other forms, the feature layer has full Add, Update and Delete permissions. In your scenario, the Add Only user could come across the feature layer and if they desired, delete or update a record outside of the Form...say in Data view of the Feature Layer page or similar. In order to make it so the users in the Add Only group can never delete or update a record, I have to create a View of the Feature Layer, set edit permissions on the Feature Layer View to be Add Only, and then share that with the Add Only group and connect the Survey to it via the submission url.

‎08-25-2020

I am using ArcGIS Enterprise 10.7.1 with a hosted feature layer. My issue does sound very similar to that Bug. My on difference may be that I am using the submission url and setting Editing permissions on the Feature Layer View used in the submission url.

‎08-21-2020

I have multiple classes of users in my system where one class of users should only be allowed to submit new records through Survey123 and another class of users can edit those submitted records in Survey123. I also have another class of users that can only view this data, but that's probably not relevant... I'm trying to restrict the one class of users to only be allowed to add new records to an existing feature layer used by Survey123. My process is to create a Feature Layer View with edit rights restricted to "Add Only" and use that as the submission url in the Survey123 form used by this class of user. The Feature Layer the View is created from is used in another Survey123 form (also using the submission url) used by my other class of users who have full permissions to Add, Update and Delete records. The above scenario is not fully working for me as it is not uploading Attachments when the Feature Layer View editing is set to "Add Only". If I set it to "Add and Update" the Attachments get uploaded correctly. I had some minor communications with Esri staff who said the editing permissions should be set within the Survey123 Form's configuration, not set on the Feature Layer itself, however, since I am using an existing feature service (submission url) this is not possible. Does anyone have a solution for this? Thank you in advance Mike

‎08-21-2020

Thanks Xander Bakker‌, I had seen that, but not had a chance to try. My preference would be to avoid the relationship class because there is a complicated web of how different feature classes can overlap and relate to each other. I'll give this a try.

Online Status	Offline
Date Last Visited	‎10-24-2023 12:07 PM

My Ideas

Latest Contributions by MichaelBrown4

Re: Survey123 Webhook Issues?

Re: Survey123 Webhook Issues?

Survey123 Webhook Issues?

Re: pulldata() and select_one_from_file from linked content CSV in web form

Re: pulldata() and select_one_from_file from linked content CSV in web form

Re: Survey123 Choice values get stripped of leading zeros

Re: Updating csvs in AGOL for select_one_from_file and pulldata in Survey

Re: Pulldata .csv Leading Zeroes Ignored

Re: Updating csvs in AGOL for select_one_from_file and pulldata in Survey

pulldata() and select_one_from_file from linked content CSV in web form

Username field type not updating when recorded is edited

Re: Allow user to only add new records (with attachments) to Survey123 when using an existing feature layer ( Submission URL)

Re: Allow user to only add new records (with attachments) to Survey123 when using an existing feature layer ( Submission URL)

Allow user to only add new records (with attachments) to Survey123 when using an existing feature layer ( Submission URL)

Re: Attribute Rule Delete Trigger to Update Another Feature

Re: Survey123 Choice values get stripped of leadin...

pulldata() and select_one_from_file from linked co...

Username field type not updating when recorded is ...

Re: Allow user to only add new records (with attac...

Re: Embedded Survey123 Web Form works for some but...