Latest Contributions by ZacharySutherby

Hello @noahfpi,  `zh-cn` and `zh-hk` are the correct language codes, please see the Supported languages documentation for more information. The message returned is just a warning and comes from the library used to convert the XLSForm.  ... View more

@DougBrowning  This is a strange one we typically see icon issues on Windows but this is new on a mobile OS. What model iPad is it?  Is the device deployed through an MDM solution or is it bare bones OEM iPad OS?   Would you be able to provide a diagnostic log when navigating the repeat / selecting questions to see if there are any graphics messages in the logs?  For "...that loses all its buttons" does the app initially start with the icons then eventually they disappear or are the icons always missing from initial launch?  ... View more

Hello @SteveBrewer, On the settings for the feature service you can set the "What features can editors see" setting to "Editors can't see any features, even those they add".  ... View more

Hello @dwold,  With the search() appearance you don't need the choice_filter column. You'll need the event names as a field in your objectives layer then user the search parameters to filter the choices based on the objective.  Your syntax would look something like search('objectives?url=...featureServer/1', 'matches', 'event_name', ${aar_admin_event}) See the search() documentation for more information on the different parameters for the search() appearance.    ... View more

Hello @TomReyes @Cristian_Galindo @AbraaoAlves @EuSau,  The ability to create() and publish() surveys has been added to the 2.3 release of ArcGIS API for Python. These updates should also be available in the ArcGIS Pro 3.3 release planned in the near future as well.  We are currently working on notebooks that we'll add to our Survey123 Developer documentation that showcase the functionality as well as an Esri Community Blog on the functionality.  ... View more

Hello @KerryKang,  In the Collaborate tab of the Survey123 website, for the "What can submitters do?" option is it set to at least "Add and update records (read access enabled)"? By default Survey123 will set "Only add new records" which would mean your public users would be able to submit but not edit.    ... View more

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.  ... View more

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.   ... View more

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.  ... View more

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.   ... View more

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.  ... View more

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.  ... View more