Latest Contributions by wcozzens

Thanks for that information James. When you have over 50 people using a survey, and you need to push out a minor but critical change (like a domain value) it can be a real problem getting all these users to download the new version. If you have a major change to the schema where the form update on the user's device is going to be required, then it can be an absolute nightmare, if not impossible to get them all to update, and everything goes sideways. Users that don't update their forms are filling out surveys that they cannot submit, they get frustrated and despise using the application, and everyone looks bad... especially the GIS people pushing this application on them. It's hard to argue with them, they are not necessarily tech-savvy people and if a form needs to be updated, then the application should walk them through that process. Many of the people using apps like this are "old school" and view this as an intrusion on their way of doing things (with a pencil and clipboard) so it better work - seamlessly - otherwise they will reject the entire concept of using Survey123 out of hand. In addition, many users may be contractors outside of our organization, so just contacting them via email or phone is to update their survey can be a real challenge. I wanted to push this discussion back to the top since we're dealing with this issue right now. I don't know if anyone at ESRI can appreciate the scope and magnitude of this problem unless you're managing multiple surveys with 50+ people in the real world. I understand there's multiple problems to consider when trying to come up with a solution here, but this is a serious issue that really needs to be addressed asap. It's already been a long time and I don't think this problem is being taken seriously enough, otherwise it would have been fixed by now. ... View more

Hi James, Thanks for the reply. Got it working, just had to make sure we had the proxy.config URL(complete with "\SubmitJob" at the end) to the published Geoprocessing service added in C:\inetpub\wwwroot\proxy to pass the authentication through. In the Integromat HTTP module the only thing necessary was the same proxy URL to the Geoprocessing task, and Method=GET. I unchecked all other options in the HTTP module and that seemed to make it work.  ... View more

Hi Ben, Would it be possible for you to post a screen shot of the working Cloud Convert function you're using in Integromat to change the filename? I have the same scenario running as you, but I cannot figure out how to rename the file that gets exported from Cloud Convert. Thanks! ... View more

Same here - ArcGIS Online org account. Reauthorizing the account in Integromat works temporarily, but it will expire again in about 2 weeks. ... View more

Ismael Chivite wrote: Hi Ken Morefield     I think it will be better if you create the token dynamically when the scenario executes.  In your case, since you are not triggering your scenario by watching a Survey123 survey, you need to manually get the token through the REST API. Okay - but what if you ARE triggering your scenarios by watching a Survey123 survey? What is the process required to prevent the ArcGIS Connection token from expiring every two week?  ... View more

While the above method works to get the Scenario running again in Integromat, the token expires again in 2 weeks. Is there a solution that will refresh the token automatically when using the Survey123 "Watch Survey" module in Integromat? It would be great is somebody could paste clear instructions for doing this, I've seen other more complicated replies for doing this using JSON but it doesn't seem like this should be necessary if using the Watch Survey module, isn't there a simple solution? ... View more

Thanks very much James, that worked! ... View more

Please check again, the same issue is back ... View more

Yes, me too. The same issue we had a few days ago is back. ... View more

The same issue is back again. ESRI - can you just remove the credit charge and put it back the way it was until you resolve the issued permanently? I'd call this a severe problem with high impact. ... View more

Has there been any improvements made to address this issue? As noted above there is no way to populate other fields in the form based on the username if the survey was started when offline. I've noticed in the latest version that users are required to login before submitting a survey, but the username field is still not being populated when the form is submitted. Any idea when this may be addressed? Thank you. ... View more

We also are using custom roles. I just checked on "Feature report" in the Premium Content section from the Role Privileges page and that did not fix the problem. However, from the Credits page I enabled both credit budgeting tools and show each member's available credits and that seemed to work - I don't get the error when printing a feature report from Survey123.  ESRI - can you please clarify the new requirements for printing feature reports? ... View more