Latest Contributions by JamesTedrick

‎07-25-2023

An 'Update XLSForm template' tool is now available in Survey123 Connect. For more information, please refer to the 'Update template' section of the Survey123 documentation.

‎07-25-2023

Rangefinder workflows with TruPulse devices are now supported in the Survey123 field app.

‎07-25-2023

The Survey123 Connector in Power Automate now supports producing feature reports.

‎07-25-2023

With the June release, Survey123 now supports the location sharing functionality available in ArcGIS.

‎07-07-2023

Hi, the issue in your example is where you are retrieving the x & y values. In your example, the values are retrieved from the attributes of the geocode result; these are values stored in the geocode table/index and are not altered based on the request input. Instead, you should be retrieving the values from the location object, which is reprojected as part of the request made by Survey123. The attached file shows this difference.

‎06-20-2023

Hi @JudithLandry - Apologies for the delay, we just noticed this comment. I think I see the issue you are describing - to confirm, this is not when you are passing the entire repeat set into a function, but you are passing a field within the repeat into the function - undefined values are being stripped from the set of values?

‎04-25-2023

Hi @Kara_Shindle , The where clause should be applies at the repeat tag ${Services} , not an individual field - the where clause sub-selects features form the repeat.

‎04-24-2023

As mentioned in the Additional Syntax section of the report query documentation, you can use a where clause in the repeat tag to limit the repeat records that are printed in a repeat section. ${#Services | where="Categories='Cat1'"}

‎04-18-2023

Hi @slach , The default behavior of the form is to request the user's location; because the request for a user's location completes after the browser has loaded the form values specified in the URL, that is overriding the value you provided when the form was loaded. You can prevent the request for a location by providing a default value of null .

‎04-18-2023

Hi all, Given these reports of functionality impairment, we have reverted the update to the feature report system. We would appreciate your help in diagnosing this issue; if you have an case open with Esri Support, I have asked them to forward your information to us if you are willing. Otherwise, please reach out at [email protected].

‎04-18-2023

Hi all, Given these reports of functionality impairment, we have reverted the update to the feature report system. We would appreciate your help in diagnosing this issue; if you have an case open with Esri Support, I have asked them to forward your information to us if you are willing. Otherwise, please reach out at [email protected].

‎03-20-2023

Hi @Bec , From the screen shot it looks like you are using an older version of Survey123 Connect. The scroll bar issue you describe was addressed last year, along with a redesign of the groupings of community surveys.

‎02-22-2023

Hi @MohammadTawbi , To understand why the repeat is leading to an invalid query, more information on the feature service is needed. Can you review the Item Details page for the feature service and ensure that update is enabled and that users are allowed to see records (either the ones they own or all)?

‎02-22-2023

Hi @JohnStark , It is not possible to send an updated value with a URL to edit an existing record.

‎01-05-2023

Hi @Young_Clarence , I would refer to the Microsoft document on licensing for this - https://learn.microsoft.com/en-us/power-platform/admin/powerapps-flow-licensing-faq . Unfortunately, it isn't practical to have an Power Automate webhook connector that is generic (offered in the list of preexisting connectors) for connecting to ArcGIS Enterprise as the URL of the ArcGIS Enterprise portal is a key setting of the connector.

Online Status	Offline
Date Last Visited	Wednesday

My Ideas

Latest Contributions by JamesTedrick

Re: "Upgrade/Migrate" Older Version of Survey123 Connect Excel Form to a Higher Version - Status changed to: Implemented

Re: Rangefinder Offset Data Collection in Survey123 - Status changed to: Implemented

Re: Add support for feature reports in MS Power Automate (AKA MS Flow) - Status changed to: Implemented

Re: Survey123 Tracklog of Fieldworker - Status changed to: Implemented

Re: Custom Geocoder to Geopoint - Different WKID

Re: Extending Survey123 smart forms with custom JS functions

Re: Accessing related records in a Feature Report

Re: Accessing related records in a Feature Report

Re: Geometry defaults to users location instead of passed lat and lon coordinates

Re: Report Template Issue: parentLayer name

Re: Cannot export report anymore

Re: Survey123 Connect New Survey Window scroll bar not working as it should.

Re: Error 400 Cannot Perform Query

Re: Passing new field parameter and edit an existing record from Field Maps to Survey123

Re: Power Automate ArcGIS Enterprise Connector - Premium

Re: Survey123 Tricks of the Trade: Photos

Re: Web app error initializing form Error not an o...

Re: Survey 123 form Error: Initializing form... Er...

Re: Survey123 Calculation referencing a null decim...

Re: Understanding Dynamic Labels in Survey123 for ...

Wildfire Response GIS