Elevation Arcade Expressions no longer working

[fjramos]

Good morning,

I recently noticed that some elevation expressions I put on one of my hosted feature layers is no longer working properly. The expression is "Round(Geometry($feature).Z, 2)" & "Round(Geometry($feature).Z*3.28084, 2)". I found that expression online through one of the ESRI sites. It used to show in meters so i created a second one that multiplies the value by 3.28084 to convert it to feet. It worked great for a long time, but just a couple days ago the values popped up as "--" on Field Maps. Later that afternoon I checked AGOL and the values that were showing up as "--" on Field Maps are showing up as "748,417.04" six or seven digit values. The previously collected data also shows up in the same manner. I also  noticed that it happened after updating Field Maps, but whatever happened somehow affected AGOL pop-ups too. Any idea what could've caused this? Thanks

[tikola]

And my variant can be defined also a bit more. It happens only in AGOL MapViewer and it does not happen anywhere else in Esri ecosystem - that matches with Franks's case latest version above. FieldMaps, ArcGIS Pro, (old Classic Map Viewer if possible) etc. in any of those my issue does not exist. I have never tested it in Enterprise as I have no such server in hands. Other coordinate labels (X&Y) in my variant are done with exactly same function except there is of course a feature(geometry).X function instead of Z. In past also X&Y was effected but that got fixed a year ago which solved my need.

Now when remembering my case a year ago more it had something to do with projections. It happens if features and basemap are not in same projection or then it had something to do with local projections we use in Finland. When moving data to same projection as the basemap issue disappeared.

Need to refresh my memory a bit and test some data variants as currently my case seems that issue exist even if both data and basemap are in WebMercator - it was somehow projection related and I need to test bit more to refresh my memory.

Issue has nothing to do with external GPS devices as I have repeated it with hand drawn points in past. Currently though my points are from Leica FLX100 as the test was originally made for GNSS mapping needs.

Colin what happens on your computer if you open my link: https://arcg.is/1z8O544 ? I have tried it be open to anyone as it just contains basemap and two points.

As a comment to Frank I see no point of sticking ArcMAP for this issue as this thing easily works in ArcGIS Pro without issues.

[fjramos]

Thanks tikola, 

I'm going to look into our basemap, we use a web service url as our base map, maybe something simultaneously changed there that I wasn't aware of when the Field Maps updates happened and I blamed it on the updates. Ha! Thanks for the insight.

[fjramos]

Good morning Colin,

I did not make any changes, however this morning upon more inspection I did notice that it is device specific when the expression attributes display as "--". On our mobile work phones, Samsung S24+, the expression attributes display correctly. On my Trimble TDC600 (Android), they display as "--", might be a outdated hardware issue? Let me try erasing the expressions and creating new ones and I will update you with the result.

[fjramos]

No difference in adding a new expression, they still display as 6 digit values for the Z field. The screenshot of the mobile phone I shared on the original post was from my Samsung S24, which was displaying as "--" at first, but after the update I think it got fixed? I don't recall exactly, I just remember seeing it on both devices, then only on the TDC600 which I use to collect data. The only device still displaying "--" is the Trimble TDC600.

[tikola]

As a add to my previous post - if you open the link to my map it labels Z to 0 but if you go editing the labeling function in that map and click Run on that it gives you nicely the correct height. So even the feature(geometry).Z function works - it just fails to write that value to label.

I tried some coordinate system variants but no success - so I have not find a way to make this work yet. I will keep on trying to isolate the issue better. In nutshell - my variant is just that labeling height from geometry fails.

[fjramos]

Hi tikola,

The issue was my web service url base map. I changed the base map to an ESRI imagery base map to test it out and the expression Z fields on the pop up display correctly now. Thanks for the help! Now a fix for those Z value expressions labels would be great, ha!

[fjramos]

A few more bits of information to add as I keep investigating, nothing has changed in our datum web service base map. The Trimble TDC600 is locked to Android version 10, and our Samsung S24 are Android version 16 which was done Feb 2, 2026. I'm starting to lean into the Field Maps display issue is outdated hardware related to the TDC600, but I can't be 100% sure. However, I still don't know what would've caused the AGOL Z expressions to display into 6 digit integers.

[fjramos]

Another quick update, the Trimble TDC600 mobile device is now displaying the expressions correctly, all mobile devices are displaying Z values correctly as before. AGOL Web Map is still displaying Z values as 6 digit integers.

[fjramos · Accepted solution]

Okay so I just figured it out. I set the base map back to an ESRI imagery base map to test it and the expressions are no longer in 6 digit format and displaying correctly on AGOL Web Viewer now (see screenshots below). So I'm guessing something got fixed/modified in the background that has to do with base map configurations.

My initial idea of using our web service URL as a base map was to keep everything consistent to our local datum. It worked great up until now that I noticed this change.

Something else got fixed that was a insignificant issue that I pretty much ignored, and never asked about on the forums, that I'll share. When I first added those Z expressions, they would display backwards on AGOL Map Viewer for some reason. The MSL(ft) conversion expression would show up as meters and the MSL(m) expression would show up in ft on the AGOL Map Viewer pop ups. However, it wasn't too much of a big deal because on Field Maps the ft values displayed on the correct MSL(ft) field and meter values on the MSL(m) field, which was more important to me being able to see the elevations in real time in the field. When I would get back to the office and briefly review the elevations on AGOL Map Viewer, I knew the ft elevations were on my MSL(m) expressions and not the MSL(ft), that's why I left both MSL(m) and MSL(ft) fields on the pop-up.

Like I said, it wasn't too big a deal because my priorities was to be able to see the Z values in the field, then if I had to process the data to create a map, I would export the features into a shapefile and process the data in ArcMap. We are migrating to ArcGIS Pro soon, so that'll be a whole knew experience when it comes.

[ColinLawrence]

---

@fjramos wrote:

My initial idea of using our web service URL as a base map was to keep everything consistent to our local datum. It worked great up until now that I noticed this change.

This would be the best practice when working with high accuracy, its just unfortunate you were running into this issue. Have you tried again with your original map in your original coordinate system? I happened to see there were some patches that went out on AGOL recently that could possible impact this.