Latest Contributions by ZacharySutherby

Hello @SFM_TravisBott,  You can use pulldata('@layer') for this workflow. You would have a select_one question with your groups then pass the selected group in the where clause of the pulldata('@layer') syntax to see if a record already exists with that group. If it does use a constraint to return an error, otherwise if it doesn't your constraint won't run and the user will be good to submit.  Please see the Query a Feature Layer sample in Survey123 Connect for some examples that use pullata('@layer'). The sample doesn't show this exact use case but can be derived from the sample.  I would suggest returning the objectId field as the check for existence or not, the syntax would be something like:  pulldata("@layer", "getValue", "results.objectId", "<Feature Service URL>, concat("group='", ${group}, "'")) Your constraint could then be something like string-length(${query})<1 ... View more

Hello @informaticacoopetarrazu,  You can create a Survey123 survey from an existing feature service in Survey123 Connect. Please see the Use Survey123 with existing feature layers documentation for more information.  When you have your survey you will need to use the Survey123 Inbox to complete this workflow. Please see the Prepare to edit existing survey data documentation for more information.  This video on modeling inspection workflows should be helpful for setting up your survey.  ... View more

Hello @TristanTaber,  I would suggest checking the data in the feature service. The web map should be pulling unique values from the data so there may be some mis matches within the data that when cleaned up should resolve the web map issue.  ... View more

Hello @najeebhall,  The existing images likely either don't have attachment keywords or are using a keyword that is different than the name of the image question in your survey.  Please see this Tech Support KB article for a workflow to update the attachment keywords. We also have a Python notebook that will assist with the process of updating the attachment keywords, but since it looks like you have more than 1 image question in your survey the notebook may not be the best approach.  ... View more

Hello @RyanOLeary,  You can use additional URL parameters in your pulldata(@layer) syntax to specifically pull the most recent record. All pulldata(@layer) does on the back end is query the feature service so you can use the orderByFields parameter to order by the creation date field. So it would look like:  pulldata("@layer", "getValue", "attributes.SomeAttribute", "<serviceURL>/0?orderByFields=creation_date desc", <whereClause>) ... View more

Hello @MonikaWheat88,  This could potentially be due to a value submitted being larger than the length of the field it's trying to submit to. A few questions: - Does this consistently happen for all submissions or just one specific submission?  - Has the survey been updated or republished since the behavior started occurring?  ... View more

Hello @NinoChkhartishvili,  Are the folks you are trying to share editing permissions with in a shared update group? Please see this documentation for more information on sharing survey ownership.  You can add collaborators and edit the survey design before publishing the survey.    ... View more

Hello @SeanDugan,  Based on the description it sounds like your colleague is trying to submit using the web app correct? In that scenario I would suggest using the browsers developer tools to capture the network traffic when trying to submit the survey and see what error is in the applyEdits request.  If you colleague is using the Survey123 Field App it would be helpful to obtain a diagnostic log when trying to submit a record from your colleagues machine. Please see this documentation for enabling diagnostic logs (You don't need to use the AppStudio console you can log to a file).  A few other questions that would help would be:  - What is your colleagues user type and role?  - Is only one colleague running into the issue or multiple?  - Is there a difference if your colleague tests on a different device like mobile phone or personal computer?  - Is your survey published to ArcGIS Online or ArcGIS Enterprise?  ... View more

Hello @RichardPasquale,  This likely happened because delete protection was enabled on the feature service and a change was made to the survey that required deleting the existing feature service and recreating it. When republishing you will know if Survey123 will delete the existing feature service and recreate it because it will display a message similar to this:  We have a defect (BUG-000150495) where Survey123 will get stuck when trying to delete the feature service when delete protection is enabled. This is why you see the new feature service created and the original one because Survey123 couldn't delete it.  To resolve the issue you can republish the survey again you should see a message like the one above but it will say "Request error" because Survey123 now doesn't know what feature service it should point to so it will then create a new one. After that republish completes you will see three feature services, you can delete the 2 previous ones if you don't need them your survey will point to the third and most recent one.  Please see this documentation for more information regarding what changes will require deleting and recreating the feature service: https://doc.arcgis.com/en/survey123/desktop/create-surveys/updatesurvey.htm   ... View more

Hello @KieferMarchel-Hoff,  We have a sample notebook that uses the ArcGIS API for Python to automate the process of exporting survey data with attachments.  The notebook won't generate a folder for each record in it's current configuration but has the foundation to be modified to meet your specific use case.  ... View more

Hello @AbiDhakal,  I would suggest reaching out to Microsoft support to verify if your subscription meets the prerequisites to create a custom connector.  Please see this documentation for more information on prerequisites for custom connectors.  ... View more

Hello @JessicaJThompson,  We do have a fix for this issue coming with our 3.17 release later this month. For the time being if you change your API URL in Connect to https://survey123qa.arcgis.com/api that environment has the fix on it at this time.  To change the API URL in Connect select the profile icon or hamburger on the top right and select Settings. Select the Services and add the qa after survey123 in the URL:    It is recommended that after Survey123 3.17 releases you switch the API URL back to the original https://survey123.arcgis.com/api. ... View more