I am working in Experience Builder Dev Edition 1.14 and have noticed an issue with the feature selection highlight outline. When the feature selection highlight outline is set in the Map Widget settings pane, the outline for the selected feature is drawn twice.
I have tested with multiple different WebMaps, and played with the outline transparency/the fill color, and still see the same error. When selecting features in a WAB application using the same WebMap, the error does not occur. And in ExB 1.13 the error does not occur. This leads me to believe there may be a bug.
This is a large concern for our organization because this is a public application with many users including consultants and surveyors who need accurate maps for permitting and other purposes.
Has anyone else experienced this behavior in Experience Builder? Are there any known workarounds to prevent the double outline?
A bug has been submitted regarding this issue: BUG-000167426. It is related to the NAD 1983 HARN StatePlane Washington South FIPS 4602 (US Feet) Coordinate System. Using this coordinate system with a Map Image Layer in Experience Builder developer edition 1.14 results in the highlight outline displaying incorrectly.
The issue does not occur in Experience Builder developer edition 1.13, or with the same coordinate system hosted as a Feature Layer.
@MarkW We are having this same issue.
I see you have mentioned a bug number. Your comment is well over a year+ old and a few versions behind what we are using, ArcEnterprise 11.5 using ExB v1.17. I looked and BUG-000167426 appears to be resolved. However, we are not using ExB developer edition, and we have end users reporting this issue. The GIS team has tested and were able to duplicate the issue. I am not seeing anything for regular ExB (not developer edition) is there a way to create a new bug ticket? Or can Esri suggest a work around for the problem?
Hi @VanessaSimps,
It looks like the bug was fixed at the June 2024 release. That should be reflected in ArcGIS Enterprise 11.4 and up, and developer edition 1.15 and up.
https://developers.arcgis.com/experience-builder/guide/release-versions/
It's possible that the fix did not get added to ArcGIS Enterprise and developer edition until an even later version. If the issue is reproducible at later versions I recommend opening a support case so we can test and submit a new bug if it reproduces.
The only workaround options I am aware of are the ones listed in the bug:
If those don't work for you or your users we might be able to find another workaround through further testing.