nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Enhanced Search not honoring zoomScale

JayGeisen

For some reason, when I click on a returned record in the eSearch widget, it zooms all the way in instead of honoring the scale I have set in the xml file. Any ideas why this might be (probably my doing I would bet)?

Vind meer berichten getagd met

Accepted answers

All comments

JayGeisen

Now that I look more closely, it appears that the zoom is set to "zoom to selected records" instead of a specific scale. Is this expected behavior? What might be causing this?

MikeKellison

Jay, I am having the same problem. Any fix yet?

JayGeisen

Nothing yet. I'm thinking this might be the default behavior (zoom to selected) maybe? It never used to be the case though. I actually kind of like the option to zoom to selected, but I wish it would honor the scale if one is specified. I'm wondering if anyone else is experiencing this?

DanielMx

I'm experiencing the same problem. I even changed:

private var zoomScale:Number = 5000;

in the SearchWidget.mxml

but not luck.

2022-02-03_13-29-21.png

RobertScheitlin__GISP

Guys,

This is fixed in the latest version with the addition of a new attribute in the SearchWidget.xml. look for usegeometry on the zoomscale for each layer. In both of your case you will not have to add this attribute because you are wanting it to use your scale and not the geometry.

MikeKellison

Works great now. Thanks Robert!

JayGeisen

Hey Robert,

I am still getting this behavior, regardless of whether I use version 2.4 of the eSearch or my current (version 2.31) one. If using version 2.31, I add in the code from 2.4 that specifies the usegeometry variable. Any ideas?

Thanks,
Jay

RobertScheitlin__GISP

Jay,

Are you setting the usegeometry="false" attribute?

This works fine:

        <layer>
            <definitionexpression></definitionexpression>
            <enableexport>true</enableexport>
            <name>Louisville Zoning</name>
            <url>http://sampleserver1.arcgisonline.com/ArcGIS/rest/services/Louisville/LOJIC_LandRecords_Louisville/MapServer/2</url&gt;
            <expressions>
                <expression alias="Zoning Code" textsearchlabel="Search Zoning Code [ Example: OR1 ]:" userlist="OR1,C2,OTF" >upper(ZONING_CODE) = upper('[value]')</expression>
                <expression alias="Zoning Type" textsearchlabel="Search Zoning Type [ Example: RESIDENTIAL ]:">upper(ZONING_TYPE) = upper('[value]')</expression>
                <expression alias="Zoning Name" textsearchlabel="Search Zoning Name [ Example: RES MULTI-FAMILY ]:">upper(ZONING_NAME) LIKE upper('%[value]%')</expression>
            </expressions>
            <graphicalsearchlabel>Use one of the graphical search tools to select Zoning</graphicalsearchlabel>
            <spatialsearchlayer>true</spatialsearchlayer>
            <titlefield>ZONING_NAME</titlefield>
            <linkfield linkprefix="" linksuffix=""></linkfield>
            <icon isfield="true" iconprefix="" iconsuffix=""></icon>
            <fields all="true" />
            <zoomscale usegeometry="false">10000</zoomscale>
        </layer>

JayGeisen

Yes, I added that line in the xml file and the following to the mxml:

if ((lyrList.zoomscale.@usegeometry) && (lyrList.zoomscale.@usegeometry == "true"))
 {
      zoomScale = Number.NaN;
 }else{
      if (Number(lyrList.zoomscale) > 0)
    zoomScale = Number(lyrList.zoomscale);
 }      
// if (Number(lyrList.zoomscale) > 0)
// zoomScale = Number(lyrList.zoomscale);

RobertScheitlin__GISP

Jay,

OK, I think I understand you to be saying that you are trying to take my updated code and adding it to an older version?... If that is the case than you are missing several other pieces of new logic that were added. A large portion of the clickSearchResult function has changed as well as other functions to support the fix I put into place.

JayGeisen

Yes, that is what I'm trying to do. I also tried using the 2.4 version of your eSearch in my 2.31 SFV. Under that situation, I am still not getting the desired result. I realize you don't want to get into supporting old versions, but is there any way to easily code a set scale into the clickSearchResult function until I can get my SFV updated to 2.4?

RobertScheitlin__GISP

Jay,

OK using the 2.4 Version of this widget in Flex Viewer 2.3.1 is not a good test as there is portions of the code in the last couple of releases that is dependent on Flex Viewer 2.4... Hence the 2.4 version of the widget. So my advice at this point is to look at the difference in the clickSearchResult function by opening the new 2.4 version and searching for isNaN(zoomScale). That might get you to all the right spots in the updated code base.

JayGeisen

Thanks, Robert. I will attempt to do that.

JayGeisen

Robert,

I got it to work in version 2.3.1. Thanks again!

Jay

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.