Latest Contributions by ZacharySutherby

Hello @SteveBrewer, In the diagnostic log the message "String or binary data would be truncated. The statement has been terminated." typically indicates that a value for a field exceeds the field length defined in the field. For example, if the field length for a text field is 5 and the value "Bananas" is submitted that would run into this message. Another thing to check is if you are using a submission_url in your survey check if any fields are set to non nullable and ensure the corresponding question in your XLSForm is submitting a value.

Hello @SusanMathai, Survey123 supports custom JavaScript functions that can be used to extract information from different API sources. If your Oracle database has an API that is accessible from Survey123 on the devices it's intended to be used on, you can interact with that API using a JavaScript function. I'm not sure if column attributes can be exposed in an Enterprise Geodatabase and ultimately Feature service, the folks on the ArcGIS Enterprise or Pro side may be able to help answer that question. But if that information can be present in a feature service you can use the pulldata("@layer") workflow to extract the information.

Hello @MillerDerek, The URL looks to be formatted correctly, one thing to check is the <<item name>> is encoded for example "Test survey" vs "Test%20survey". If it's a web designer survey you may need to use https://www.arcgis.com/sharing/rest/content/items/<itemID>/info/form.json?f=json&token= Are you obtaining your /generateToken from an automated API call or from the Survey123 website? One thing you can test is setting the referer to https://survey123.arcgis.com/surveys. You can also see the request if you access the Collaborate tab in the Survey123 website you can filter the network traffic based on .info and it should return the request that Survey123 makes. This note shouldn't play a role in the error observed, but I'll note not all surveys will have a webformInfo section in the .info file. If the survey was published from Connect it may or may not have it.

Hey @MillerDerek, There's a few aspects to this and depends on where you're looking to use the information. You can control "accepting responses" on both the Survey123 form item side and/or the feature service side too. So depending on where you're looking to control this depends on where you'll need to look. From the Survey123 form item side you have the ability to set a survey status in the Survey123 website to open or closed. Closed being not accepting responses and open being accepting responses. With this though it doesn't control anything on the feature service so the survey can be "closed" but the feature service could still be pulled into a web map and edited. This open/closed status on the Survey123 form item is stored in it's .info file which isn't exposed through the item properties like you see in the ArcGIS API for Python. You can access the .info file through the sharing/rest URL by accessing: https://<webContextURL>/sharing/rest/content/items/<surveyItemID/info/<surveyName>.info?f=json&token=<validAccessToken> The open/closed status will be under webformInfo -> settings -> openStatusInfo -> status On the feature service side you can also check if add/update/delete capabilities are set on the service. Not sure what your full use case is but if you're looking to use an open/closed status in the Survey123 field app, the field app doesn't support the setting from the website, but what you can do is use a custom JavaScript function (assuming the survey isn't to be shared publicly) to query the sharing/rest endpoint, obtain the status, then set up a constraint based on the status to prevent submission.

Hello @KerryKang, The feature service used for the pulldata("@layer") lookup may not have query enabled on it. As an admin in the org you have the ability to query all data but other users do not. Please check the "What features can editors see" setting on the service, if it's set to "Editors can't see any features, even those they add" or "Editors can only see their own features" your colleague may not have access to the data in the service.

Hey @RobertAnderson3, I've logged this feedback as something for us to investigate if it's possible to support in the future. Please feel free to reach out to Esri Technical Support to log an official Enhancement to track progress on the feature.

Hello @ModernElectric, The pulldata("@layer") function returns the result from the Query REST API, which will only return domain codes and not labels. To obtain the domain label a queryDomains API call would need to take place and match the code returned with the code in the response of the queryDomains request. I've logged feedback internally to investigate if this is something we can add to the pulldata("@layer") function in the future. At this time to return the domain label you can do a couple of things: - Use a custom JavaScript function to do the queryDomains REST API call and return the matched domain label - Duplicate your domain as a choice list in the choices worksheet of your XLSForm, set the question you are doing the pulldata("@layer") lookup to a select_one question so the result from the lookup matches a choice name in your choices worksheet, then in your original question you need to return the label use the jr:choice-name() function to return the label from your choice list.

Hello @Polesig, Just to confirm are you able to get to the Android/data/com.esri.survey123/files/ArcGIS/My Survey123/Logs and there's nothing there or are you only able to get to the Android folder and not data? With Android 11 Google locked down access to apps data (the Android/data folder) and it became more constrained in Android 13. We have BUG-000165596 logged regarding sharing diagnostic logs in Survey123 not being able to get to the My Survey123/Logs and are investigating a solution. To work around the issue you can connect the device to a PC and access the folder from Windows File Explorer.

Hello @KellyTaylor, Would you be able to pass along the XLSForm for troubleshooting? You can also enable diagnostic logging prior to opening the survey, would it also be possible to obtain a log when the behavior occurs?

Hello @RHammers, It wouldn't be in a single line the calculation would need to go in it's own question so that value can be referenced in the event select_one question. The separate question can be a calculate question type that is not visible on the form and is only used to store calculations on the back end. Another good resource to see how to summarize data using pulldata("@layer") in XLSForm is the Query a feature layer sample available in Survey123 Connect.

Hello @SMH-Rio, It's not a connectivity problem it is a known issue in Survey123, we have an internal issue logged to address this in the future but unfortunately don't have a timeline at this time. It doesn't look like there is an official Tech Support BUG logged for this behavior. Please feel free to reach out to Esri Technical Support to log a BUG and track progress on the issue.

Hello @MaryGraceMcClellan, Here is a sample that calculates the vertex for a specified index, but this index can be hard coded vs dynamically passed in from the survey.

Hello @mikAMD, You would need to add a new field in your feature service and field calculate the concatenated value. The search() appearance can only use one field as the label in the choices worksheet.

Hello @RHammers, You can use pulldata("@layer") to query the feature service your survey points to and return the count of the number of records that match the specific event. For example, if someone selects Event C the pulldata("@layer") function would query the data and return the number of records that have the value Event C. You can then configure logic in your survey so that if that number is 25 or more then there's a constraint on the event select_one question preventing the user from submitting. Please see the Request parameters section of the Query a feature layer documentation for more information on how to return the count.

Hello @GaryBowles1, The quotation marks in your outStatistics string is throwing off the URL string. pulldata("@layer", "getValue", "attributes.field1", "https://gis.srcx.com/server/rest/services/APPS/APPS_RUN_LOG_BINGHAM_MR/FeatureServer?outStatistics=[{"statisticType": "avg","onStatisticField": "field1","outStatisticFieldName": "field1_avg"}]) You'll need to use something like: pulldata("@layer", "getValue", "attributes.field1", 'https://gis.srcx.com/server/rest/services/APPS/APPS_RUN_LOG_BINGHAM_MR/FeatureServer?outStatistics=[{"statisticType": "avg","onStatisticField": "field1","outStatisticFieldName": "field1_avg"}]')

Online Status	Offline
Date Last Visited	3 hours ago

My Ideas

Latest Contributions by ZacharySutherby

Re: survey 123 operation rollback survey wont send

Re: ¿How to send data from a form made with Survey123 to an Oracle database?

Re: Survey123 item property to determine whether the survey is accepting responses

Re: Survey123 item property to determine whether the survey is accepting responses

Re: Pulldata @layer works for my account (creator-admin), but not for a field worker

Re: Populate drop down list from AGOL layer with multiple fields

Re: PullData @Layer - Domain Description VERSUS Code

Re: Survey123 android app diagnostic file not created

Re: Survey123 Connect stuck on "Loading survey"

Re: Count specific responses and restrict survey submission?

Re: Linked webmap is not displayed in Outbox

Re: JavaScript snippet to get a vertex from a geotrace question?

Re: Populate drop down list from AGOL layer with multiple fields

Re: Count specific responses and restrict survey submission?

Re: @pulldata Query (Feature Service/Layer)

Re: survey 123 operation rollback survey wont send

Re: Attachments in Survey123 Field App

Re: Count specific responses and restrict survey s...

Re: PullData @Layer - Domain Description VERSUS Co...

Re: Populate drop down list from AGOL layer with m...