Latest Contributions by daveostrander

‎01-06-2021

I had a similar issue where I was writing submitted survey records to another feature service in NAD 83 state plane, and my points were being plotted incorrectly. I discovered that geopoint questions will always be in WGS84, and there is no way to convert them within Survey123. However, you can use webhooks to pass the point information to another feature service published in the desired coordinate system. There is a parameter to transform the data when doing an applyEdits operation using the ArcGIS REST API. The transformation can be automatically processed using webhooks and an automated services platform such as Power Automate or Integromat. Optionally, you could also leverage a geometry server service (Services>Utilities on your server's REST endpoint or by using https://utility.arcgisonline.com/arcgis/rest/services/Geometry/GeometryServer/project?) and use the built-in project operation using the ArcGIS REST API.

‎01-06-2021

@JamesTedrick stated, "You can query the feature (using the 'Make an HTTP request' action) that was edited to retrieve the full feature information." Previously the expected behavior when editing a submitted survey record was that only the updated fields would be included within the payload when a survey is submitted. However, it appears that this process has since been improved. All survey fields are now included in the payload, whether actively edited or not, and assuming the webhook setting to submit the survey data has been checked. The update was a good enhancement as it reduces the need to set up superfluous actions within a scenario or flow. I just wanted to point this out to the community since if the expectation is that it doesn't get passed in, that payload information could be overlooked.

‎11-02-2020

Hi James, "pulldata() functions are not designed to occur within other functions." Does this also extend to nested IF statements? I want to use the pulldata() function depending upon the input of a previous question. Thank you, dave-o.

‎10-02-2020

To verify, I am at version 3.10 and use the globalID in the web parameter to edit specific records.

‎10-01-2020

Thanks Ismael! It seems to work with a single survey, but in my experience, it fails when adding records to one survey and then editing records in a second survey.

‎10-01-2020

I was just alerted that the bug has now been logged as #BUG-000134259 regarding this issue. Also, it seems this bug only affects Microsoft Power Automate and not Integromat. Unfortunately, my employer requires that we use a government account only offered by Microsoft, so that doesn't exactly give me a workaround. Still, hopefully, this helps others looking to implement something similar. I hope this gets fixed soon!

‎09-30-2020

Hi Erica, I have just gotten word back on this issue from the amazing people at Esri technical support and they have confirmed that this is a software defect. I will post the BUG# once it has been logged, but it appears that it does correctly identify the submission as an update, but for whatever reason it does not trigger the webhook. Currently testing this to see if it occurs in other automation platforms, or if it is just isolated to Power Automate. The funny thing is that this exact workflow was suggested to me by Ismael Chivite. So, Ismael if you are listening I hope you can influence the development team to fix this as soon as possible, and definitely no hard feelings that it doesn't work : ) Thanks for your help with this Erica!

‎09-30-2020

This part is a bit frustrating because we have no idea how the software interprets these things since it all happens on the backend and somewhat out of reach. That said, having two surveys is key to a submit and review process since we wouldn't want the original submitters to have the ability to self-approve their submission requests. That was my thoughts as well, but from a logic standpoint it seems like opening the form in edit mode using an existing globalID should be all that is needed for the webform to realize that it is an edit, since that is the way it works using the single survey method. That was my thoughts as well, but from a logic standpoint it seems like opening the form in edit mode using an existing globalID should be all that is needed for the webform to realize that it is an edit, since that is the way it works using the single survey method. That was my thoughts as well, but from a logic standpoint it seems like opening the form in edit mode using an existing globalID should be all that is needed for the webform to realize that it is an edit, since that is the way it works using the single survey method. That was my thoughts as well, but from a logic standpoint it seems like opening the form in edit mode using an existing globalID should be all that is needed for the webform to realize that it is an edit, since that is the way it works using the single survey method.

‎09-30-2020

Yes, that is how it is set up! Survey1 triggers on new records only and Survey2 triggers on edit existing records.

‎09-30-2020

This architecture works with a single survey that has triggers for both submitted records and edit existing records.

‎09-30-2020

I have two surveys built on a single hosted feature layer in AGO with webhooks setup using the Survey123 connector in Microsoft Power Automate. The workflow is for the first survey to add new records to the feature layer, which triggers a webhook and sends an email with a link to open the second survey form and the previously submitted record in edit mode. This works! The next step is to make edits to the record and resubmit as part of an internal review process. Once submitted the edit event should trigger another webhook and send an email letting the original submitter know if their original submission was approved or not approved. This fails! It seems that the edit event never triggers the second webhook (i.e., I don't show any history in Power Automate of the run). The data is successfully edited, but the original submitter never receives the follow-up email. Is there a way to have two surveys that work off the same data and trigger webhooks based on add events in one survey and update events in the other? This would be highly useful so that the entire workflow could be automated, which is what is desired.

‎08-01-2019

Hi John, I think the premise of this idea is that Survey123 provides an elegant way to capture attribute data (i.e. using a form), but what is missing is a way to effortlessly capture a notes/comments field where a user might need to input a few sentences or a few paragraphs depending on the data being collected. Currently, that requires using the mobile device's on screen keyboard, a docked keyboard, or the built-in microphone. All of these options have their own drawbacks (i.e. typing using the onscreen keyboard is best suited for small amount of characters, a docked keyboard is not well suited for someone whom is standing/walking while collecting data out in the field, and the microphone to text option often makes mistakes, which are burdensome to fix). The Apple Pencil, on the other hand, minimizes this effort since it closely replicates filling out at form, which is what Survey123 is all about! A large swath of the adult population is used to/comfortable using pen and paper, so I believe doing that same task, only digitally, makes a whole lot of sense. I did discuss this at length with Ismael Chivite‌ since there is an API available for this very purpose called Interactive Ink. However, I believe in the end it wasn't something Esri could "productize", but I never received any specifics as to why. In the mean time I am using a companion app, called Nebo to convert handwriting to text, and then simply pasting that into my Survey123 forms. Obviously, it's not as ideal as an in app experience would be, but it does get the job done. Maybe some day it will be available natively within Survey123. If history can be my guide, Esri usually sees these things my way, it just takes them a little longer to get there ; ) Filling out digital forms with a digital pen, editing related tables in a feature service, publishing Surveys as related tables, peanut butter going well with chocolate etc....

‎03-14-2019

Hi James, Thanks for replying so quickly! I did look into the advice you provided: James Tedrick wrote: - In the Form's Settings page on the Survey123 website, do you see the MS Flow webhook entry? Yes, webhooks appear and use the correct urls. - Did you download the form before the webhooks are created? If so, you should re-download the form. Made sure to delete existing survey and re-download latest form. - You are not using the Inbox to open up the existing feature and add inspection records? This is actually an edit event, which we do not yet support webhooks being triggered on yet. I am not using the inbox, and sending the surveys at submission time. In reviewing things a little further I discovered that the web app version of Survey123 does trigger the webhook, sends the payload, and is received successfully by Integromat using my preferred data structure (FS1 > FSRelatedTable1, FS1 > FSRelatedTable2, FS1 > FSRelatedTable3). It seems that the issue lies in using the Survey123 field app. I have saved the internet posts/responses (saz files) using Fiddler, which I ran while testing: Survey123 web app against my more complex feature service (FS1 > FSRelatedTable1, FS1 > FSRelatedTable2, FS1 > FSRelatedTable3). This worked! Survey123 field app against my more complex feature service (FS1 > FSRelatedTable1, FS1 > FSRelatedTable2, FS1 > FSRelatedTable3). This failed! Survey123 field app against my simple feature service (FS2 > FS2RelatedTable1). This worked! I would be happy to share those saz files with you if you would like to review the http traffic recorded at survey submission time. Oddly enough, the field app test that failed did indicate that Integromat appears to accept the payload, but doesn't appear to first establish a connection with Integromat. In contrast, all of the other testing above that proved successful, Fiddler first logged a connection with Integromat first. In the failed test we seem to be missing the tunnel to Integromat. It is nice that at least there might be a way forward using the Survey123 web app, but for various reasons it would definitely be preferred to always run the Survey123 collection directly from the field app. Any thoughts?

‎03-14-2019

I am currently having an issue using webhooks with Survey123, where the payload does not appear to be sent at submission time. I am using an existing hosted feature service to create and publish my surveys, each survey is pointed at a separate related table within the feature service (i.e.1 feature class related to 3 different tables using 3 relationship classes at the database level; nothing nested, all tier 1 relationships). I am able to create the surveys without issue, publish them with no problem, and add records to related tables using Survey123, again without any trouble. I can see the data on the Survey123 website as it gets submitted, both in the table on the data tab, and in the action tab that comes up when you select the record in the table. However, the webhooks do not appear to ever be triggered when the survey is submitted, which is evidenced by not seeing any sort of failure or success messages within Integromat or Microsoft Flow. In contrast to the previous workflow, I have another hosted feature service that only contains a single related table. When I create/publish this survey in the exact same way as outlined above I am able to make use of the webhook without any issue. To be clear, all of the feature services mentioned in this post are hosted on ArcGIS Online, use non-versioned data, rely on GlobalIDs for the primary and foreign keys, have the foreign key's GUID fields added to the surveys with the XLSForm's field type set to esriFieldTypeGUID, and have the form_id set to the name of the corresponding related table. The only difference across both implementations, is that one feature service has multiple related tables, while the one that functions contains a single related table. It is vitally important to have the previously described workflow (i.e. relationships like FS1 > FSRelatedTable1, FS1 > FSRelatedTable2, FS1 > FSRelatedTable3), since each of the three survey types record very different data, contain a varying quantity of fields, and require that the payload data be converted into 3 very different PDFs, which then get emailed as attachments within our Integromat workflow. I have contemplated workarounds, but I am not interested in having multiple feature services for each type of survey, since the data being collected, while quite different at the table level, is very much aligned at the feature class level. This part of the project is the last piece of the puzzle (all other systems are a go), but without a functional webhooks component the whole project essentially collapses. Please help!

‎03-06-2019

Thanks John! I did go the webhooks route. The python script you created looks really impressive, though! Webhooks works well for us, since we are most interested in the instant gratification aspect (i.e. the survey payload is converted to PDF and then immediately emailed at submission time).

Online Status	Offline
Date Last Visited	‎08-07-2024 09:07 PM

My Ideas

Latest Contributions by daveostrander

Re: Get coordinates in NAD83

Re: Survey123 Tricks of the Trade: Integromat

Re: Continued issues with pulldata in web forms

Re: Survey123 Tricks of the Trade: Editing records in a web form

Re: Survey123 Tricks of the Trade: Editing records in a web form

Re: Survey123 Tricks of the Trade: Editing records in a web form

Re: Survey123 Tricks of the Trade: Editing records in a web form

Re: Survey123 Tricks of the Trade: Editing records in a web form

Re: Survey123 Tricks of the Trade: Editing records in a web form

Re: Survey123 Tricks of the Trade: Editing records in a web form

Re: Survey123 Tricks of the Trade: Editing records in a web form

Re: Add Support for Apple Pencil in Survey123 for ArcGIS

Re: Survey123 Webhooks not Triggering when Surveys are Designed to Submit Entries to a AGO Hosted Feature Service's Related Table

Survey123 Webhooks not Triggering when Surveys are Designed to Submit Entries to a AGO Hosted Feature Service's Related Table

Re: Export & Email features on Survey123 mobile app

Re: Understanding Survey123's custom URL Scheme

Re: Is there and example of using Power Automate t...

Re: Get coordinates in NAD83

Re: 2020 Census Data Availability

Re: 2020 Census Data Availability