Latest Contributions by IsmaelChivite

‎12-02-2022

Hi @alyssajhnsn You will need to share your XLSForm for anyone to be able to help you. If you do not want to post your XLSForm file publicly in this forum, our Esri Technical Support team will be happy to help if you open a ticket.

‎12-02-2022

The Survey123 app will disable JavaScript functions whenever the user logs out of the app.

‎12-01-2022

Hi. I do not think that is possible. An image question is for photos/images. If you want to upload a file, such as a PDF file, you need to use the file question type. This can be a bit confusing with images because images are files, so you can also upload them to the file question type. But in the end, you can't have a question type that allows you to either take a photo with the camera and also allow you to browser for any file type.

‎12-01-2022

@cole_KTB Thanks! You will want to use the selected() function. Check the selected(question,value) section in this blog: https://community.esri.com/t5/arcgis-survey123-blog/survey123-tricks-of-the-trade-xlsform-functions/ba-p/893567

‎11-29-2022

This may help: https://community.esri.com/t5/arcgis-survey123-blog/survey123-tricks-of-the-trade-working-with-uk/ba-p/1038895 In short: Build a CSV file with the pump stations and their corresponding lat/lon values Display all pump stations in a list Use pulldata() to get the X/Y values of the selected pump station Use the XY values to populate a geopoint question (you can choose to show or hide the geopoint question in the form

‎11-23-2022

@MichelleWilliamsERM The XLSForm specification does not allow you to add to questions with the same name. In your XLSForm design, make sure that you have no repeated question names. In your specific case, you got lucky because the duplicated name includes an image type of question. Lucky, because you can rename the image question in your XLSForm design and proceed. If your duplicated question name was present in other type of question, such as text, date, integer, etc. you would not be able to rename it. Separate from the above, you are getting the error 'Fields not found in the feature service:0'. This error message is caused by a software defect in the October 2022 release. This is planned to be addressed in the December 6 update. In the meantime, you can use the workaround described here.

‎11-23-2022

Hi @JohnWatermolen_PWI I gave this is a quick test and worked as expected. Simply get the URL of your survey and paste it into a WhatsApp message. Get the URL from the Survey123 website (Collaborate tab) as shown below: Then paste that URL into your message. I tested this using both the Whatsapp in my phone as well as the desktop version. Works great.

‎11-23-2022

@erica_poisson @ryank Try adding the orderByFields parameter at the end of your feature layer URL: pulldata("@layer", "getRecord","<your_featurelayer_url>?orderByFields=CreationDate DESC", "1=1") For the above to work, you will want to make sure that: Your featurelayer URL, as usual, includes the layer index at the end Your feature layer has query capabilities enabled You can use either getRecord, or getValue. Here are some examples. This expression uses getValue to get from a US counties layer the most populated county name. pulldata("@layer", "getValue", "attributes.NAME", "https://services5.arcgis.com/jMCHJcLe13FaKCFB/arcgis/rest/services/US_Counties/FeatureServer/1?orderByFields=POPULATION DESC", "1=1") Below, the same thing, but we get the entire record as a JSON string, which we can later parse with pulldata("@json") pulldata("@layer", "getRecord", "https://services5.arcgis.com/jMCHJcLe13FaKCFB/arcgis/rest/services/US_Counties/FeatureServer/1?orderByFields=POPULATION DESC", "1=1") Hope this helps!

‎11-22-2022

On December 6, 2022 we will release a new update to ArcGIS Survey123. A Beta version of this update is available for testing. Here are the highlights: High priority fixes in Survey123 Connect and the Field App • BUG-000153696 Survey123 Connect fails to publish a survey with error "Fields not found in the feature service: 0" when using an existing feature service if a question label doesn't match the field alias in the feature service. • BUG-000117385 Coded integer values in a feature service created by Survey123 Connect for ArcGIS are not appearing in the web app attribute table. • DE-000005891 ENH-000127565 Enhance Survey123 Connect so that the “repeat _count” field is not added to the schema and therefore not required in the feature service. • BUG-000151353 Select_one questions in a webhook output are a numeric type only when submitted from the ArcGIS Survey123 field app. • BUG-000151226 Using dynamic labels in groups with the table-list appearance fails to display the select-one question dynamic label in ArcGIS Survey123. • ENH-000135042 Allow for Survey123 Mobile App to send users back to the log in page after password is changed when using Portal for ArcGIS accounts configured with IWA. • Fixed a bug in which the incorrect week number was displayed during day light saving time when using the week-number appearance. • Improved app navigation in right to left language display. You can download the Beta version of Survey123 Connect and the field app from the Early Adopter website. You will also find forums to post your feedback. All the fixes above will be in our December 6 update. Survey123 web designer enhancements Author multi-lingual surveys. Use Survey123 web designer to translate your surveys into multiple languages. Multi-lingual survey support is available already in Survey123 Connect. With this update, you will also be able to do it from the web designer using a visual interface. Multilingual survey authoring from the Survey123 web designer is a very strong candidate for the December 6 release. We are looking forward to your feedback for further functional and UX improvements. CAPTCHA: An experimental feature at the moment. A candidate for the December release. We have organized a live session to test these web designer features on November 29. Find more details here. If you cannot join us, learn how to access the Survey123 Beta website from the Survey123 Early Adopter community. Report automation: Create report in Microsoft Power Automate The Survey123 Microsoft Power Automate connector includes a Create report action. This allows you to automate report generation using Microsoft Power Automate. If you want to test this new action, join us for our November 29 sneak peek session. We also plan to make this available in early December through the Survey123 Early Adopter community.

‎11-21-2022

Please check for a solution here https://community.esri.com/t5/arcgis-survey123-questions/fields-not-found-in-the-feature-service-0/m-p/1230556#M45974 This problem is caused by a software defect introduced in 3.16 (planned to be addressed on Dec 6, 2022).

‎11-21-2022

Hi. Using the new pulldata("@layer") function you can count the number of records submitted to a survey (granted that your survey layer has query capabilities enabled). With that, you can build a constraint to prevent further submits, and show a message indicating that the survey is closed. Check out this video on minute 22:10, as it describes how to do it. Also some additional help in this blog, and this help topic. The above is not quite the same as 'closing the survey', but it may do it for you.

‎11-18-2022

@ChristopherKreuter If your survey does not have photos and you are using ArcGIS Online, 20K records within 48 hours is not out of the ordinary. If your survey allows respondents to send photos, audio or file attachments, please contact your Esri account manager or send an email to [email protected] referencing this Esri community thread so we can discuss in more detail the specifics.

‎11-18-2022

@ZacharyHart Geo-Calculations using pulldata("@layer") only work while online.

‎11-18-2022

@iHack I understand your concern. I would be concerned too! 🙂 Instead of having Make update the record through the survey layer, you can create a separate layer view just for the purpose of updating. In that way, you can keep your survey layer public with permissions to just add (queries disabled), and then allow updates only through that separate layer. In Make, your target URL for the updateFeatures operations would be that of the layer with update capabilities. To keep things secure, you will want to secure that layer and have Make generate a token to access it. Check the generateToken operation. I hope this makes sense. It adds more complexity to your Make scenario and forces you to create a new layer view, but it will be more secure.

‎11-18-2022

Hi Erica. Thanks for posting. I can reproduce the behavior you describe. This issue is under investigation. We can't provide a tentative date for its resolution for now, but once we know better we will post here. In the meantime, it would be great if you could open a Tech Support Incident, just so this is logged using the official channels as a BUG.

Online Status	Offline
Date Last Visited	Friday

My Ideas

Latest Contributions by IsmaelChivite

Re: Form Logic Error - Hidden Repeat

Re: Javascript functions disabled after some time

Re: Survey123 Question accept file upload or camera input

Re: Survey123 Tricks of the Trade: hidden, relevant and body::esri:visible

Re: Create a new Survey123 record entering an address or a pump station number

Re: Survey123 3.16.106 issue | Repeat has same name as item in the repeat | _image added to the image name

Re: Survey123 and WhatsApp

Re: Survey123 Tricks of the Trade: pulldata("@layer")

December 2022 Beta release of Survey123 available for testing

Re: ArcGIS Survey123 Connect version issues

Re: Can I Turn Off Survey Programmatically?

Re: What are the limitations to submissions to a form

Re: What's new in ArcGIS Survey123 Web Designer (October 2022)

Re: Survey123 Tricks of the Trade: Make (previously known as Integromat)

Re: Voice Control of QuickCapture in iOS 16 does not seem to work

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