Latest Contributions by AprilChipman

This is what I see when I click 'Organization' -> 'Edit Settings' and then the 'General' tab on the left. The App Launcher does not include Survey123, but asks for an App Item URL. This is what I see when I click 'Organization' -> 'Manage Licenses' ... View more

I am the Administrator of the Portal. ... View more

I didn't think Survey123 required an additional license...? ... View more

Survey123 is not in the App Launcher.  ... View more

I've been having a similar issue and have started a case (#02451807) with ESRI Tech Support. It seems to depend upon how many surveys go through the Integromat scenario, but sometimes I have to verify the connection once a day and sometimes it will last several days. I don't think it's worked properly for a week straight yet. I have other Integromat scenarios using the same and different AGOL connections, and none of them have any problems. ... View more

I created the map in the current Map Viewer. I can try to share it. ... View more

Yep - you're right! I changed my Router to look for the 'eventType' and now my filter is working correctly. New submissions and edited submissions are sending different emails. I have also created a webhook link the the body of the email to open the survey via the web and can edit the data. I'm starting to feel pretty fancy!  But, I'm still only getting the edited data back instead of all data. I guess now is when I should add in the HTTP module to collect up all of the data from the survey, instead of just the edited data? Anyone have a suggestion on what that looks like? Thanks! ... View more

I have tried creating a workflow of just sending emails of edited data, rather than including feature reports, to minimize the steps that could be causing problems. I've created a filter of new and edited data so that I can deal with them separately in the HTTP and Gmail modules.  I can get new submissions to make their way through properly, but edited surveys are sent along both paths and I end up with two emails. I tried to follow the comments of Dominic Roberge and Tijs Lips on this topic: Survey123 Tricks of the Trade: Integromat (https://community.esri.com/groups/survey123/blog/2019/06/04/survey123-tricks-of-the-trade-integromat ), but am just not able to wrap my head around what they did to get it all working. ... View more

Thanks for asking, Jim! I had stopped trying and testing, but this afternoon I took an old test Survey123 Connect and added a scenario in Integromat. This survey was created and published in 3.2, but I updated it today to "always use the latest version". When published, the survey already had the Inbox enabled. First submission worked great - I submitted a survey and got an email with the appropriate attributes in the appropriate places. (wow! It's like I know what I'm doing or something!)  So, I then tried editing a survey from the Inbox in the app. Again, it all worked. I received an email with all of the attributes in the right places, including the updated information I edited. WooHoo! So, I then tried editing a survey from the Data tab on the Survey123 website. Although I still got an email (and no Integromat errors, which I had been getting), the only information in the email was the attribute that I edited. I did not get any of the existing data via email through Integromat. I double checked in the Data tab on the website and, sure enough, all of the unedited data still exists in the attribute table. Is that how the 'watch survey edits' webhook is supposed to work? Or should it still send all of the attributes through Integromat with the edited attribute? Thanks again! This app and tools are improving our workflows so much - it's amazing! ... View more

I've been thinking about this and trying to create a similar workflow... Would it be possible to use an existing feature class to create a Survey123 form that will then edit/update attributes based upon a map in Collector? (I don't feel like I'm explaining this well, so I'm going to try to walk through the steps.) There are 20,000 meters. 8,000 of them need to be changed to a new type (or inspected, depending upon the particulars for your project). I have a basemap with a layer of all the meters and a layer of the meters that need changed. I would like the field crews to be able to use Collector to see the meters that need to be changed. In Collector, they can select a meter to be changed/inspected and then subsequently use the link in the pop-up to open Survey123 to the form that will auto-populate some of the meter information. There would also be a field in that form, say 'Status' with a domain of 'To Be Done' and 'Completed', which the field crews can edit as necessary to change the symbology of the feature in the Collector map (as well as update all sorts of information in an Operations Dashboard). An additional use of this map and form would be for the field crews to select a meter that *isn't* in the layer to be changed, but should be (we all know that data integrity causes those problems), and use it's pop-up to link to the same survey form. But, instead of editing an existing feature, this time a new feature will be added to the layer of meters to be changed. (I've done this part already with device inspections, so I'm pretty sure it's possible to incorporate it into the meter change out workflow.) ... View more

I get the same error, but only when a Survey123 feature is *edited* rather than submitted. When I try removing the Data field, I get an error. But the whole flow seems to work just fine when a new survey is submitted.? ... View more