topic Re: Web App builder Search Widget Not projecting correctly in ArcGIS Web AppBuilder Questions

Web App builder Search Widget Not projecting correctly

AnjithaSenarath4 — Sat, 04 Jun 2016 15:40:14 GMT

My base map and my all layers use WKID :4326 (WGS84) projection. Everything is normal but when I search record from search widget using a feature layer... It project to wrong place. I think it is bug and how to correct it?

Re: Web App builder Search Widget Not projecting correctly

ShaharBukra — Wed, 14 Dec 2016 11:29:16 GMT

Were you able to find out what is the reason? ..

Re: Web App builder Search Widget Not projecting correctly

HillaryBjorstrom — Tue, 27 Dec 2016 15:36:51 GMT

Any answers on this

Re: Web App builder Search Widget Not projecting correctly

ShaharBukra — Wed, 28 Dec 2016 05:14:23 GMT

Hi, Hillary Bjorstrom, Anjitha Senarath‌

So i kind of debug ESRI js api code and saw that the param maxAllowableOffset do all the damage inside the file Search.js

Working	Not Working

The value of maxAllowableOffset was 'n' so i changed it to be 0, and only then it zoomed correctly

I've download the JS API to our IIS server and modify the Search.js [The path is [SERVER_NAME]\js_api\3.18\esri\dijit\]

file now look like this

It worked for us.

hope it will help you as well.

Shahar.

Re: Web App builder Search Widget Not projecting correctly

Anish_Adhikari — Tue, 14 Feb 2017 00:26:59 GMT

I sort of ran into similar problem. My layer was published with Feature access capabilities. The feature layer's projection was off slightly compared to the default mapping layer although they used same mxd's and had same projection. I was going to try Shahar's solution, but found out an easier way to suit my needs. So the simple solution that worked for me was to publish the mxd as mapping(default) and WFS enabled instead of mapping and Feature access. The search widget will work with the layer.

Re: Web App builder Search Widget Not projecting correctly

HillaryBjorstrom — Thu, 13 Jul 2017 15:26:14 GMT

i have also found that i had this issue specifically on features with joins. i had to remove the join.