June 2026 Update: Unable to stack points

[ChristinaNeal]

With the recent update, our team is now experiencing issues with stacking points within one of our layers. We receive an error that says: "Something went wrong. Edits could not be saved: Layer does not support z values while feature has z values." This was never an issue prior to the update. Do we have to modify how our layer is published now or is this an experience builder bug?

[MikeVolz]

Are the points being stacked in Experience Builder or are the points being stacked in GIS desktop software (ArcGIS Pro) and then just viewed s stacked points in Experience Builder?

[ChristinaNeal]

They are being stacked in experience builder.

[CraigGillgrass]

@ChristinaNeal are you able to reproduce this in either Map Viewer or the Web Editor?

[ChristinaNeal]

I just tested it and received an error in both Map Viewer and Web Editor.

[CraigGillgrass]

thanks @ChristinaNeal I will take a look and reach out if I run into any issues with reproducing it.

[Jianxia]

@ChristinaNeal, Thank you for letting us know. It appears this may be a regression from the ArcGIS Online update last night. Could you please share a reproducible sample with us, or contact Esri Support to submit the issue? As @CraigGillgrass mentioned , we aim to narrow down the source of the problem - whether it is specific to Experience Builder or related to an underlying component that could affect other ArcGIS apps as well.

[CraigGillgrass]

@ChristinaNeal can you contact me at [email protected] so we can work through this issue?

[Ethan_Bassett]

I am having a similar problem since the latest update. In Experience Builder I move points of one feature layer A to match the location of points in another feature layer B. Anytime I attempt to move A to match a point from B, I get the same error message: "Something went wrong. Edits could not be saved: Layer does not support z values while feature has z values." Feature layer A does not have z-values enabled, but B does. That being said, this was not a problem until the most recent update. 

[ChristinaNeal]

I opened a ticket and met with Esri Support today. The bug # is BUG-000185874 and it is currently "In Review."