Latest Contributions by JohnathanHasthorpe

Hi Tucker Does you service have attachments? The reason I ask is that on submission, Survey123 will do an ApplyEdits and then an AddAttachments and this is why you would get two calls. In the future we will change this into a single transaction using apply edits with UploadID, but we are still working on this implementation. Thanks John ... View more

Hi April   This is in Connect – open up the survey xls and go into the settings tab. You will then see the column and will need to add the service item to it, in the format of: https://www.arcgis.com/sharing/rest/content/items/5c312f83a4d4420ba1d70441b9986eb3 Thanks John ... View more

Hi Scott The correct url is: .https://www.arcgis.com/sharing/rest/content/items/5c312f83a4d4420ba1d70441b9986eb3 This will ensure that you don't get the serviceItemId error. If you go into the the service url and then view it in JSON: Can you check the status of the of following property: "supportsApplyEditsWithGlobalIds" It sounds like this is set to false when it should be set to true - please confirm. To enable, you should make sure you follow the guidance here: Use Survey123 with existing feature services—Survey123 for ArcGIS | ArcGIS  You will need to check the layers in the feature service have a globalid column with a unique index. This will need to be done by looking at the data layers in desktop before publishing the service. In terms of the sync capability - this only works if enabled in desktop on publishing (not in ArcGIS Online). Thanks John ... View more

Hi Scott When defining the submission_url for a survey - you need to paste in the url of the service item, not the actual service url. Also, the error message you are getting indicates that the service does not have the property of supportsApplyEditsWithGlobalId set to true. For a feature service to support applying edits with Global IDs, the following requirements must be met: The layers in the feature service must have a globalid column with a unique index. The data cannot be versioned. A quick way of implementing the above is to enable the sync capability on publishing the feature service. Once you do this you should be able to publish the survey in connect. Cheers John ... View more

Hi Erick In relation to your comment: I have set the Survey to point directly at the related table. I have set up the bind:esri:parameters as suggested in this post: If you are pointing directly at the related table, then you don't need to use add queries into the bind:esri:parameters  column. You would only use the bind:esri:parameters if you were editing a feature layer  that had repeats, and wanted to edit both the feature layer and related table at the same time. As you are going straight to the related table, there is no related table to query. Please clear out the column and republish. Thanks John ... View more

Thanks April If you made a change to the survey that resulted in a schema change, then the service would be created with a new name. It looks like something may have gone wrong on re-publishing and the old service was not deleted. In terms of the new layers appearing, these are likely to be feature service views. I think you must have either created the initial survey in the web site (survey123.arcgis.com) or updated the sharing permissions in the web site, and this is why you are seeking this issue (Connect cannot delete views). Additionally, if the new form does not have anything under layers - then it will not be updating any of the feature services. What you need to do is update the submission url in the new form to point to the new feature service. The submission_url column in the settings tab of the survey form defines an existing feature service where your survey responses will be submitted. You need to provide the URL of the new feature service item (not the service url) and then republish. Please let me know if you need any further help. Thanks John ... View more

Hi Christopher - please update to the latest version of the native app (2.5) in order to access the fix. Thanks John ... View more

Hi Eric  This is a known bug related to the editing of repeats - the inbox should show the date modified time. We have an issue open to address this and will add your details to it. Thanks John ... View more

Hi Dan External selects are only designed to work with choice lists associated with a cascading select, and therefore only work with a select_one question type. Thanks John ... View more

Hi John To get this working, you would need to do pulldata against the feature service that your surveyors are updating. The service would need to contain a field for the true/false status, and this would be the value returned by the function. They would then use the survey to update the status on submission. However, unfortunately it is not yet possible to use pulldata against a feature service. We have an enhancement open for this, and will add your requirements to it.  In terms of resetting the values in the feature service every month. You could create a Python script that updated the field via the services rest end point, and then use windows task scheduler to run it at a specific interval. I'm not clear on your workflow, but if you are using repeats (i.e. a meter feature with related meter reads) you could use the inbox to view (in readonly mode) all previously submitted reads against the meter, and add a new reading directly from the inbox if required. Please let me know if you want any more information on this workflow. Cheers John ... View more

Hi Michael I was not able to replicate your issue. Can you share a bit more information on the the device and version of Survey123 you are using? Thanks John ... View more

Hi April I have a few questions: 1) Are you doing this in Connect? 2) What are the names to the 2 HFS in the same directory? 3) What was the update that you made to the survey and did you do this to the existing survey, or create a new version. Note that one survey form can only point to one feature service. If you look at the form item in AGOL you can see a link to the feature service that it is pointing to. If you want to submit to both the old and new feature service, then you will need to have two separate forms. Thanks John ... View more

Hi Christopher - this issue has been fully addressed. Please provide details of what you are seeing, on what version of the app and on what device. Thanks John ... View more

Hi Qualidade 1 and 2 are linked. Essentially you have applied an bind::esri:fieldLength of 3 to a couple of questions, and you hit the error because the survey is trying to submit an answer that exceed this limit. Removing the limit enabled me to submit without error - can you try this your end? Thanks John ... View more

Can you confirm that there is a token at the end of the url you are using to access the service, e.g //services5.arcgis.com/jMCHJcLe13FaKCFB/arcgis/rest/services/service_a596f962b6b94c07b0ffc58430c1bd29/FeatureServer?token=HIkrzVFWfjdk............ ... View more