Latest Contributions by TylerBragg2

Re: Webform "Failed to Submit" after April 13, 2021 AGOL Update

@SunnyCorrao the case is still open with ESRI Support Services. It's been frustratingly slow and fruitless thus far. Nobody can seem to figure out the issue. My last update was on 7/8/21 via email from the technician working on the case. Here is what he said - "After collaborating with our internal resources, we have determined that this "Failed to Submit" behavior is a defect. I am currently logging this defect and will send the information to our development team. I will reach out soon with more information on the defect and steps for following its progress." I have no idea where we go from here or what the process is to fix a "defect." But I guess I'll just have to wait and see. I would have thought the behavior would be fairly easy to trace from their end, but evidently not. Tyler

I'd like to see this feature as well. I have a date field with conditional visibility based on a "status" field. When the user updates the status field to "Closed", they must enter the "date closed", and I would like for the date field to auto-populate based on today's date so they don't have to select it manually.

‎06-29-2021

@JamesTedrick are you able to shed any light as to where the webhook action takes place - on the server or the client? I have a survey where this issue has occurred multiple times, and it happened again this morning. This is a public survey where the survey is completed via the Survey123 web app - so surveys are ever submitted via the Survey123 mobile app. I have a webhook set up in Integromat to automate some processes with the submission data and there have been serval times where it appears there was no trigger for the process after a survey response is submitted. Since this keeps happening, I need to figure out what is going on and resolve the problem. I'm not sure where to look at this point to determine why there was no action. I have checked in Integromat, but there are no errors for this submission - it just appears as if it didn't receive any notification of a new survey submission because there is no record of it at all. There seems to be some confusion/disagreement as to where the webhook is generated. I assumed that it must be from the server, since that's where the webhook is configured (and also given that feature level webhooks are set up from the server as well), but I may have assumed incorrectly. Can you clarify? I think this will help me get an idea of where to look. Then there is the question of a webhook log - is there somewhere that has a log of each webhook action? Any help would be appreciated. Tyler

‎06-15-2021

This is interesting, because I'm primarily experiencing this with the webform, though I have experienced it with the mobile app as well. We have one survey where users (public) apply for new utility service with our municipal sewer department (through the Survey123 webform), and that's the primary one that seems to experience this problem. So given that this is coming from the webform and not the mobile app, what could be the cause of that? And does this new update do anything to fix it?

‎06-14-2021

That's not a bad idea at all. But, I'm thinking we could rule out connectivity issues as the cause because the webhook is not initiated at the mobile level; rather, it should be issued by ArcGIS Online at the feature service level(at least in my case, unless you are using Server, then from there). That's where a log file from AGOL would be nice so you can compare the submit time/date of the feature and the log file of webhooks to see if it skipped one. I'm thinking that's what's happening. But what you mention would be a good way to validate that. Or, I suppose there could be a blip with Integromat where it was NOT listening for a certain time period. Then AGOL could have sent the webhook but Integromat never saw it because it wasn't listening. In that scenario, Integromat wouldn't show it in the scenario history because it truly didn't receive it, even if it was because it "wasn't listening."

‎06-14-2021

I've been having this happen to me as well, and it seems to be more often in the last few months. I have a paid subscription to Integromat and have 28 active scenarios running at all times, some of them being somewhat complex, some being fairly simple. I actually had this happen last week and again today on a scenario that has been running for about a year now with very few problems. The user reported the problem to me but I can't seem to nail down the source, except that it must be in the webhook. I checked the history of the scenario in Integromat and there are no errors, and more importantly, no record of the trigger at all. I've tried to look on the Survey123 side and I can't seem to find a way to validate that the webhook trigger was sent to Integromat. Then the next submission of the survey will work perfectly.

‎06-14-2021

I agree with this. I've had several issues with Survey123 not sending webhook triggers to Integromat, and I've been trying to find a way to check a log. I'm guessing there isn't one. If not, there should be a way to check that. I'm sure it's logged somewhere.

‎05-17-2021

@DanteLee - I still have an open case with ESRI Tech Support and we have not come to a conclusion yet. I'll post when we come up with something.

‎04-27-2021

I grabbed some screenshots of the errors: Below is the error I get when launching the survey from the web map popup that I use in Field Maps. This is described in item # 2 above. This was actually generated on the desktop from Map Viewer Classic, but I get the same error when launching it from Field Maps. If I simply launch the Survey123 web app from my AGOL home page, shown here: Then close the survey123 web app, I can successfully launch the survey from the web map popup and access the survey with no problems, shown here: Notice the Icon and my name in the upper right of the screenshot above. After I've launched the Survey123 web app from the browser it recognizes me as being logged in and allows me to access the survey. I generated these errors from the desktop, but again, I'm getting the same problem from a mobile device.

‎04-27-2021

I have been experiencing a problem with Survey123 not recognizing users as being logged-in in several scenarios. These surveys have been established and working for more than a year, and this problem has come up in the last few months. There are two scenarios so far, and they are as follows: I have a several surveys embedded in different dashboards, all of which are configured to open in edit mode within the dashboard. One example is a Yard Sale Permit. The survey itself is open to the public, and the public uses this survey to submit an application for a Yard Sale Permit. The dashboard is for our staff to view the permit information and makes necessary modifications. In order for the staff to view the dashboard, they must log in to AGOL, then open the dashboard. The problem is that the embedded survey does not recognize them as being logged in and generates an error that will not allow them to submit edits. (When a user is logged in, their user name and picture icon is present in the top-right of the survey window, but this is not showing up). However, if the user opens the survey123 web app from our org's AGOL home page first, the embedded survey loads just fine and will allow them to make edits and submit with no problems. This was not a problem until just a few months ago. We are using Windows 10 with the Google Chrome browser. I haven't tested with other browsers at this time. I have a map for use in the Field Maps mobile app, and I've configured the pop-up to contain a link to a survey that opens in the web form in edit mode. Again, this was working fine with no problems until a few months ago, and now when the user (who is logged into the Field Maps app) launches the survey from the pop-up, they receive an error that they don't have permissions to access the survey. Again, when this happens, there is no username or picture icon in the upper right of their survey. However, if you open the browser and go to our org AGOL home page, log in, then launch the survey123 web app, then go back to Field Maps and launch the survey, it functions properly and the survey shows them as being logged in. I have tested this with Chrome and Samsung Internet and experience the same issue. It appears that there is some problem with the user's credentials getting passed to the Survey123 web form in both desktop and mobile environments, and with different browsers. I've searched the community forum, and have yet to find anyone with this same issue. I did find a thread that talks about a similar problem and suggests making changes to the Chrome settings for "Same site cookies" and "Preloading pages for faster browsing," but I've tried changing both of those settings to no avail. Here's the thread: Embedded Survey123 Web Form works for some but not others . There were two suggestions in this thread, neither of which seem to solve the problem for us. I hope I've explained this problem well enough, but I'd be happy to answer any questions that may help to find a solution. I can also provide some screen shots if needed - I just didn't have them at the time of writing this question. Thanks. Tyler Bragg

Online Status	Online
Date Last Visited	a week ago

My Ideas

Latest Contributions by TylerBragg2

Re: Webform "Failed to Submit" after April 13, 2021 AGOL Update

Re: Setting the date field to today sets the date without user interaction

Re: Webhooks not triggering randomly

Re: Webhooks not triggering randomly

Re: Webhooks not triggering randomly

Re: Webhooks not triggering randomly

Re: Provide Webhook Logging

Re: Webform "Failed to Submit" after April 13, 2021 AGOL Update

Re: Survey123 web form not recognizing logged-in user when opened from Field Maps or Dashboard in Chrome (desktop and mobile) and Samsung Internet

Survey123 web form not recognizing logged-in user when opened from Field Maps or Dashboard in Chrome (desktop and mobile) and Samsung Internet