topic Re: Odd rendering of selected feature in ArcGIS Web AppBuilder Questions

Odd rendering of selected feature

LonSharp — Mon, 11 Mar 2019 18:52:16 GMT

I hope I'm posting this in the correct location...

I'm seeing an odd behavior in my Web Appbuilder applications in Portal 10.6.1.

When clicking on a feature that has pop-ups enabled, the selection outline is off. Way off. Not just shifted, but inaccurately drawn (see image below: the selection should follow the red parcel boundary). It only occurs at large scales. When I zoom out (beyond about 1:2400), it renders the selection correctly.

This is happening for all layers with pop-ups, in all Web Appbuilder applications. These are dynamically rendered vector layers, not cached.

As far as I know it's new behavior since we upgraded from 10.5.1.

Any thoughts?

Re: Odd rendering of selected feature

RobertScheitlin__GISP — Mon, 11 Mar 2019 19:07:04 GMT

Lon,

That behavior is because the version of WAB that ships with Portal 10.6.1 was generalizing the geometry. This is fixed in 10.7 Portal released later this month.

Re: Odd rendering of selected feature

LonSharp — Mon, 11 Mar 2019 19:58:17 GMT

Thanks Robert.

Hopefully, going from 10.6.1 to 10.7 will be a lot smoother than the trouble I had going from 10.5.1 to 10.6.1.

Re: Odd rendering of selected feature

ClaireGrysko — Thu, 09 May 2019 15:20:15 GMT

We are on ArcGIS 10.7 and W.A.B. 2.12 and are still experiencing the same issue. If this is indeed fixed in 10.7, is there something additional we need to account for or check to solve this problem?

Re: Odd rendering of selected feature

RobertScheitlin__GISP — Thu, 09 May 2019 15:32:54 GMT

Strange. I was suppose to be addressed in 10.7. You will need to open a support ticket then.

Re: Odd rendering of selected feature

ClaireGrysko — Thu, 09 May 2019 20:59:12 GMT

Thank you! We will do just that.

Re: Odd rendering of selected feature

RogerDunnGIS — Mon, 18 Apr 2022 18:22:17 GMT

What were you able to find out from Esri Support? I am having the same issue, even when I set env.js.deployVersion to 2.7 (without changing any other files and folders). See attached screen shot.