Latest Contributions by IsmaelChivite

‎04-12-2022

‎04-12-2022

Now available in Beta. Check details at: https://community.esri.com/t5/arcgis-survey123-blog/survey123-april-2022-now-available-in-beta/ba-p/1161436 Tentatively scheduled for general release in July 2022

‎04-12-2022

Thanks for submitting this idea. We will extend pulldata() as suggested to help you collect information about: Device model an operating system used to collect data. This will work in the mobile app and also the web app. For web surveys, we will report the web browser and operating system in use. Survey123 app version (already supported) Survey version (as specified in the XLSForm settings worksheet) and survey title Information about the logged-in user: First name, last name, full name. Username and email are already supported. This is tentatively scheduled for our May 2022 release.

‎04-11-2022

Unfortunately, Apple does not allow multiple versions of an app to be made available in their app store. If the device does not have Survey123 3.12 installed already, it will not be possible to install it now.

‎04-11-2022

I have not done that before, but I would try first populating the link in the popup using an Arcade expression. the Trim function should be able to help.

‎04-11-2022

Hi. Having your web survey run embedded within a dashboard should not add any variation. If your pulldata functions work well within the survey123 web app, they should run the same when embedded in your survey. I did not see any pulldata() calls in the XLForm attached above.

‎04-11-2022

Hi @Katie_Clark If you are using a custom JS function to query a layer, you will need to pass the token from the logged-in user. You can get the token with pulldata("@property", "token") and then use that in your JS logic. The only thing to keep in mind is that if your logged-in user is connecting to ArcGIS Enterprise, the token will not be valid against an ArcGIS Online layer from the Living Atlas of the World. Alternatively, if you want ArcGIS Survey123 to handle the token business in your behalf, you can try the new Beta pullata("@layer", "getRecordAt") function. You will find more info about this function in the last section of https://community.esri.com/t5/arcgis-survey123-blog/survey123-april-2022-now-available-in-beta/ba-p/1161436 As with custom JS functions, the pulldata("@layer") functions will not be able to use an ArcGIS Enterprise token against an ArcGIS Online secure layer.

‎04-11-2022

Hi. I have not been able to reproduce the behavior you describe. I published your form and tried it in the field and web apps. All worked as expected. I used version 3.14 to publish and test your survey. I also attached below another way to do this. I hope it makes sense. It achieves the same thing, but with a slightly different approach. The property address is only shown when needed. If the mailing and property addresses are the same, the property address is automatically populated with the mailing address.

‎04-11-2022

I suggest you add a geopoint question to your survey and set the default column to null. If you do not want to display a map in your survey, also set the appearance to hidden. I hope that helps.

‎04-08-2022

Hi. If I understand correctly, you want to dynamically populate a list in Survey123 with values from a non-ArcGIS system. The short answer is: not directly. You can dynamically populate a list from an ArcGIS feature layer using the search appearance. @BrettStokes describes this in: https://community.esri.com/t5/arcgis-survey123-blog/dynamic-choice-lists-using-search-appearance/ba-p/1060838 If you manage to update records from your non-ArcGIS source into an ArcGIS feature layer, I think you could have a good solution.

‎04-08-2022

You could also try the pulldata("@layer","getRecordAt") function. It is still in Beta, but you may want to explore it. Check details here: https://community.esri.com/t5/arcgis-survey123-blog/survey123-april-2022-now-available-in-beta/ba-p/1161436 This function works only in the Survey123 web app and requires you to use the latest version of Survey123 Connect to publish your form. Essentially, you can query a layer with the boundary of your city using the provided location. If you get a record back, you let them submit. Otherwise you show an error message. Please note that as of April 2022 this function is in Beta. However, you can start testing it and providing feedback.

‎04-08-2022

The Survey123 April 2022 update will include a handful of focused fixes and support for Bulgarian language. Our plan is to make this release available on April 21. You can now access it through the Survey123 Early Adopter website. You will find instructions to load the beta version of the Survey123 website and web app in your browser and the Beta versions of Survey123 Connect and the field app. The Early Adopter forums are open for your feedback as well. Survey123 Website and web app BUG-000144856 When filtering single choice questions in the ArcGIS Survey123 website by unique values, blank drop-down entries are displayed in place of removed choice options. BUG-000147917 Survey123 web app does not enforce the count-selected(${image_question_name}) constraint for an image question with multiline appearance if the survey title contains any upper-case letter when publishing the survey for the first time. ENH-000140973 Provide a confirm button in Survey123 website in a mobile device while filling a geopoint in survey to make it similar to Survey123 Field application BUG-000137843 When the ArcGIS Survey123 web app returns the error message, "Error: Initializing form...", due to failure to load the CSV file, the error message does not fit in the dialog window. BUG-000147360 Performing statistics on a nested repeat layer outputs unexpected results if the main record does not have any nested related records ENH-000138984 Allow user to retrieve the number of unique values from a field in a survey report Survey123 Connect and field app BUG-000145239 Unable to download public surveys with anonymous access disabled in ArcGIS Enterprise has been fixed. BUG-000147656 The ArcGIS Survey123 field app does not show the existing values properly for a select_one question with the autocomplete appearance and a default value has been fixed. BUG-000147935 A question field with an autocomplete appearance within repeat navigates to the name of the choice, instead of a label has been fixed. BUG-000147451 Relevant expressions using fields based on previous questions with default values in Survey123 field app do not populate as expected has been fixed. BUG-000147571 Default value used in choice filter fails to load choice lists on subsequent repeats with autocomplete appearance has been fixed. Relevant or calculate expressions that null a value and do not get updated in the feature layer has been fixed. Leading zeros being truncated when submitting from the Inbox has been fixed. An issue causing images collected with the Spike app not displaying correctly has been fixed. An issue with .mp4 attachments being uploaded with the incorrect content type has been fixed. An issue with select_one_from_file selections not being visible in the Inbox when choice labels are integers has been fixed. Added ability to connect to a GNSS receiver using an output baud rate other than 4800. Tech preview: pulldata("@layer") Many of you have requested that we enable the use of custom JS functions in public surveys. For security reasons, that is unlikely going to happen. Having said this, we are identifying common uses of custom JS functions with the intent of bringing those as built-in functions. In this way, we make authoring easier on you and also allow execution in public surveys. Overwhelmingly, the most common reason why we see you using custom JS functions is to query layers. This includes spatial queries such as point-in-polygon and attribute queries. We want to support this by extending the pulldata() function: pulldata("@layer","getRecordAt","<URL>,<LOCATION>,<WHERE filter>) pulldata("@layer","getRecord","<URL>,<WHERE filter>) The output of the pulldata("@layer") operations is a JSON object representing a single feature. Using pulldata("@json") you can extract the attribute data you want and use that in calculations, constraints or expressions to control the visibility of form elements. Here is a live example showing how you can use a point-in-polygon query to calculate a value. The new pulldata("@layer","getRecordAt") function allows you to query a layer without the need for custom JS code Here is another live example showing how you can you use pulldata("@layer") to make sure the user adds a point within a particular polygon. You can use pulldata("@layer") in constraints. For example, to prevent users from submitting locations outside of your area of interest This new pulldata("@layer) function is at this moment only supported in the Survey123 web app. You will need to author your form in Survey123 Connect and test your work in the Survey123 web app. The preview in Survey123 Connect will ignore at this moment your pulldata("@layer") syntax. Although this feature is not officially supported yet, your pulldata("@layer") calls will work fine with the released version of the web app once your survey is published. Learn more about pulldata("@layer") through the Early Adopter documentation. If you have feedback, please use the forum in the Early Adopter Program. Subject to your feedback, we plan to add for support pulldata("@layer") in Connect and the field app in May/June October/November and officially document and support this feature in the July 2022 update before the end of 2022.

‎04-08-2022

Hi. To add to @ChristopherCounsell 's answer: This blog post describes some techniques to create unique values. It may help. If you survey is meant to work online, you can also use a custom JS function to query your survey layer and figure out if there is already a record with the same project number. The code is here: https://github.com/IsmaelInRedlands/Survey123-Tricks-of-the-Trade/blob/main/getRecord The custom JS function would be ideal for your constraint (again, for online workflows only). For details on using custom JS functions, check this blog. Be aware that using custom JS functions is not allowed in public surveys. We plan to include the getRecord JS function above as a built-in function within Survey123 later this year. This will allow you to use this type of query in public surveys without the custom JS function limitations.

‎04-08-2022

@jcarlson @CN @CN wrote: I'm thinking this is likely possible but not sure on the syntax. Say one has two S123 groups, I would like both to be set to the appearance "compact" at load but would only want 1 group open at anytime. So if group1 is expanded, group2 is compacted, if group2 is open, group1 is compacted. Any assistance is appreciated if supported. Thanks. Tip: If you move your relevant expression to the body::esri:visible column, you will control the visibility of the question without affecting its values. When a relevant expression is false, the question is hidden and nulled-out. When that same expression is moved into the body::esri:visible, the question is hidden, but the values will remain untouched. For more details see Question visibility section in this help topic.

‎04-05-2022

Hi. If using Survey123 Connect, you can create a constraint to reject addresses that have not been selected from the candidate list. Here is an example showing how to do it. In theory, you could also use the geocoding score and discard anything with score less than 100, but in my experience the technique above is more robust. You will want to set the appearance to hidden for rows 3 and 4 when you publish your survey. I left hidden out in the example so you can see how it works.

Online Status	Offline
Date Last Visited	4 weeks ago

My Ideas

Latest Contributions by IsmaelChivite

Re: Allow users to edit their submitted data (without the Survey123 App) - Status changed to: Closed

Re: Calculate location from a feature service (without javascript) - Status changed to: In Product Plan

Re: Grab OS and software versions - Status changed to: In Product Plan

Re: Downloading Survey123 for older iOS versions (iOS <13)

Re: Can I limit characters passed through a url parameter to survey123?

Re: pulldata() working in connect and web form, but not in dashboard

Re: Javascript function returns code:499, token required - how can I query the feature layer?

Re: Calculated field calculates more than once, I think

Re: Disable GPS location

Re: Change the data from third-party API into option "choose one list"

Re: Stop survey if geopoint in specific location

Survey123 April 2022 now available in Beta

Re: Add a unique constraint to a field in Survey123

Re: Using Relevant to Collapse (Compact) One Group When Another is Opened

Re: Constrain input for geocode appearance field from locator

Re: Auto complete function for multi select questi...

Re: Survey123 Inbox not returning repeat data

Re: Creating a unique ID in the Survey123 web desi...

Re: How to add two or more relevant to select_mult...

Re: Is it possible to allow users to edit records ...

Wildfire Response GIS