Latest Contributions by SteveCole

‎03-31-2026

My opinion is that this is a Survey 123 idea because this gets to a licensing issue with Survey 123 rather than a functionality issue. I don't think ESRI will change it because it will cut into their profit margin. This same basic issue also plagues the feature report functionality in S123 and I think there have been some Ideas regarding that for awhile now. The unpublished public survey is the workaround which works for many applications but obviously not all.

‎03-27-2026

Ultimately we just live in ESRI's world and are subject to their whims so I would not solely rely on ArcGIS Ideas for change. Here is an ESRI post which describes how they want to be informed about accessibility issues.

‎03-16-2026

I've given up on this because there's always some facet of ESRI tech that isn't up to parity and it's usually a crippling factor for what I want to do. From what I recall, you have to create and publish report templates in Pro using the process outlined in this ArcGIS Blog post. Further down in the EB Help for the Near Me Widget you'll see the Print Reports section which links to the above and some other info to cobble it all together.

‎03-12-2026

You said you've already logged it so this is a little moot but someone from ESRI made a post yesterday about How to submit accessibility issues to Esri Technical Support

‎03-12-2026

Assuming your data frame is defined using AR North State Plane, right-click on your layer that originated from the CSV file and choose Data -> Export Data. Choose the "Use the same coordinate system as : THE DATA FRAME" and specify the output location. Add the newly exported layer to your data frame. Open the attribute table and add two new attribute fields for the State Plane X, Y coordinates. Right click on each newly created attribute field and select the Calculate geometry option. For the X coordinate, choose the X coordinate of point option and use the coordinate system of data source. The units should default to feet. Repeat for the Y coordinate using the Y coordinate field you added.

‎03-10-2026

I recall seeing this during some S123 searches. I've marked it as the solution because it looks like the best approach given the current options. Thanks..

‎03-06-2026

Getting my feet wet(ter) with Survey 123 and not quite sure how to implement input validation for a specific section of my form. The form is for field data collection along sampling transects. As you see below, the user specifies the overall length of the transect, and the length of the transect that would be within wetland. Once the wetland length of the transect is known, I use a calculation to subtract the specified wetland length value from the total length value to derive the wetland buffer length. This all works but if I enter a wetland length greater than the total length of the transect, it will calculate a negative number as shown in my screenshot. I've added a constraint on the wetland length input but my understanding is that constraints are actually triggered when attempting to submit the survey rather than as real time data validation. Any suggestions? FWIW, here's my XLSForm:

‎02-24-2026

Yes, that does work. It's not as streamlined as an option while building the map tour but it does work. It's made more complicated because ESRI has multiple versions of its basemaps-. It appears as though the basemap that is used inside the Map Tour Builder is the vector tile version but that is different than the topographic basemap found in the standard Map Viewer. Anyways, for my immediate need, I followed your alternative. I still support my idea, though.

‎02-23-2026

The basemap used during a map tour doesn't change between the overview and a specific stop along the tour (using a custom extent rather than the default view extent). It would be nice to have the option to change the basemap that is in use at any given stop along the map tour. Many ESRI basemaps give a clean look at the full extent of the map tour but lack detail, if a more zoomed in extent is chosen. The ability to swap basemaps to the imagery basemap or one of the others (or custom / organization basemap) would add more context to the user working through the map tour.

‎02-20-2026

Alycia, while I disagree with the substance of your reply, I appreciate you offering the context for the current situation. Census data (with which I am working with) seems to be precisely the use case FOR the use of graphs inside the details section. I'll attach a copy of a report my JS API application generates as an example of what I'm trying to replicate and how the graphs work within the on feature context. Based on your description of the current state of affairs, there's no point in my attempt to replicate this. Experience Builder export doesn't support this type of output export & suggests using custom report templates instead. Now you're telling me that it won't support that either. So now I'm stuck, still supporting a JS API application that we want to get off but can't.

‎02-19-2026

I presented my use case in this unreplied post but I'm developing a print template for use in Experience Builder so I can export the results of the Near Me widget in the style and format of what I currently use with the JS API and I need to insert a chart into the detail section of a report template but that isn't allowed- they can only go everywhere BUT the detail section and this makes absolutely no sense.

‎02-18-2026

You're not missing it- it doesn't exist. Welcome to the new and improved Near Me widget! That isn't a workflow I have needed but I think the way to implement it in EB would be to use the Add Data widget so that your users can upload the shapefile and add it as a layer onto your map. Next, you would use a Data Action so that a selected feature can then be used as the input geometry for the Near Me widget analysis. This will get you your analysis results at which point you'll learn the the onscreen results can't be exported as a PDF in the same format as they're presented onscreen (only as CSV with all fields) but that's a gripe for a different thread.

‎02-11-2026

Clearly not the answer I was hoping for but that is the way it goes. Thank you for finally clarifying that.

‎02-10-2026

Here is the CSV with the data I am attempting to graph. Nothing earth shattering.

‎02-10-2026

You've linked to the EXPERIENCE BUILDER documentation. But this is the Storymaps documentation, which has decidedly less information and certainly no limitation information. Here is the ArcGIS Blog post about charts and Storymaps which, again, lacks specificity about limitations or restrictions. I'll concede that the chart functionality available in Storymaps or Experience Builder is likely built on the same foundational tools but that in no way guarantees that the user has access to the full suite of functionality of any given tool/widget (instant app vs Experience Builder, for example). This is precisely why I harp on the documentation. I'll post a CSV in a second reply momentarily..

My Ideas

Latest Contributions by SteveCole

Re: GIS Request Management - Survey123 user type

Re: Make disabled buttons 508 compliant

Re: Near Me widget - Can I personalize the PDF report export?

Re: Accessibility Issues: Ensure [role="img"] elements have alternative text

Re: Need help converting a csv with lat long to a shape file with state plane

Re: Input Data Validation involving Note

Input Data Validation involving Note

Re: Add ability to change basemap for Explorer Map Tour

Add ability to change basemap for Explorer Map Tour

Re: Add ability to insert chart into detail report section

Add ability to insert chart into detail report section

Re: Near Me Widget / Experience Builder

Re: Chart Limitation Documentation

Re: Chart Limitation Documentation

Re: Chart Limitation Documentation

Re: Accessibility Issues: Ensure [role="img"] elem...

Re: Need help converting a csv with lat long to a ...

Re: Input Data Validation involving Note

Re: Near Me Widget / Experience Builder

Re: Cannot Get Labels behind Polygon