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 Widget URL Search Configuration

azgis

Robert,

I am getting an error in the MapManager after inputting the code changes that are specified in the Enhanced Search Widget URL Search Configuration pdf. The error is to the line of code as follows from private function mapLoadComplete function utimerComplete:

ViewerContainer.getInstance().widgetManager.getWidget(id);

The error is 1061: Call to a possibly undefined method getWidget through a reference with static type com.esri.viewer.managers:WidgetManager

Thanks,
Jim Faron

Vind meer berichten getagd met

Accepted answers

All comments

RobertScheitlin__GISP

Jim,

Did you miss the "Changes to the WidgetManager.mxml" on the bottom of page 2?

azgis

Robert,

No I didn't miss that. Inserted it on line 467, after the 'setAutoXY() function.

RobertScheitlin__GISP

James,

And your problems window in Flash Builder does not report any error?

azgis

Robert,

I did miss an additional error (for some reason flashbuilder repeats the same error, same line for over 10 times): in the WidgetManager, I get error 1120:Access of undefined property Widget in this code:

Widget.setState(WidgetStates.WIDGET_OPENED);

I changed the W in widget to lower case 'widget.setState', and that fixed it, but then got the error 1120:Access of undefined property BaseWidget in this code towards the end of your insert:

widget.setState(BaseWidget.WIDGET_OPENED);

RobertScheitlin__GISP

James,

Just change that line to :

widget.setState(WidgetStates.WIDGET_OPENED);

And you will be good to go.

I will get my errors fixed in the documentation. 😮

azgis

Robert,

I saw that toward the beginning of that insert you instruct the following:

widget = widgetTable.find(id) as IBaseWidget;
     //add back the container if exists
     //if using FlexViewer 2.1 than this line needs to be
     //widget.setState(BaseWidget.WIDGET_OPENED);
     widget.setState(WidgetStates.WIDGET_OPENED);
     wgtContainer.focusWidget(id);

So I changed the line in the else statement (where I was getting the error):

else
       widget.setState(WidgetStates.WIDGET_OPENED);
      widgetTable.add(id, widget);

The error is gone!

Thanks again for your help,

Jim Faron

JayGeisen

Robert,

How might one modify the code to allow different searches other than the first one in the config file? My current site (1.x) allows this, using code supplied by you (naturally). I actually tried modifying the 1.x code myself to do this in version 2.2, but then I happened across this thread and went with this. If you are taking requests, this would be high on my list. In fact, I'm not even sure I am too excited about moving my public site to 2.2 until I can get this worked out, since we now rely on the ability to link to various features through the URL search. Anyway, just thought I'd throw that out there. Thanks again for everything you do for the community.

Cheers,
Jay

RobertScheitlin__GISP

Jay,

What did a couple of your 1.x urls look like? Please be sure to post more than one and preferably searching different layers.

JayGeisen

Okay, here are a few.

1. http://gis.johnson-county.com/PIV/?parcelnum=1009427001

2. http://gis.johnson-county.com/PIV/?pollsite=county

NateRose

Robert,

I noticed you added an option for the data grid to show up after a search is performed in the March update. BTW I really like the data grid results format. Is there an option for the data grid to show up on page load using the URL Search Configuration?

For example, returning all records of a layer and having them displayed in the data grid on page load?

Thanks,

Nate

RobertScheitlin__GISP

Jay and Nate,

Your enhancement requests made it into the v2.3 release of the Enhanced Search Widget. Only thing is that the new version is ONLY for Flex Viewer 2.3. Time to upgrade.

JayGeisen

Thanks Again, Robert!

NateRose

Robert,

Thanks for the update. I added the code from the URL Search Config, initially I got an error while building the project in FB4 with duplicate functions in MapManager.mxml. I looked through the code again and found this additional maploadcomplete function so I commented this out so there was only one reference.

            private function mapLoadComplete(event:MapEvent):void
            {
                // ViewerContainer.dispatchEvent(new AppEvent(AppEvent.LAYER_LOADED));
            }

After I did that I'm getting an error saying this:

Encountered errors or warnings while building project LayerListWidget.mxml.
    MapManager.mxml: Access of possibly undefined property urlConfigParams through a reference
       with static type Class.
    MapManager.mxml: Attempted access of inaccessible method getWidgetId through a reference
       with static type com.esri.viewer:ViewerContainer.

My Enhanced Search widget is labeled "Search" so I changed the .getWidgetId("Enhanced Search"); to .getWidgetId("Search"); I thought this might have helped but I'm still getting the same error and it lists it through each widget in the error dialog.

Nate

RobertScheitlin__GISP

Nate,

Did you notice my comment that the new version is only for FlexViewer 2.3?

NateRose

Robert,

Yes, I first copied over the files to upgrade to 2.3 and then made the code changes. Does it look like an issue with the upgrade to 2.3?

Nate

RobertScheitlin__GISP

Nate,

Yep you must have an issue with your copy, there would not have been a mapLoadComplete function in the 2.3 version of the MapManager.mxml

NateRose

Robert,

I no longer had the 2.3 files so I downloaded the 2.3.1 flexviewer and it worked fine with no errors. When I put the "?search=Owner&slayer=0&exprnum=3&showdatagrid=true" parameters in the it loads the page as usual but runs no search.

If that is a compatibility issue with 2.3.1, is there a way to get 2.3 un-compiled? I don't see it on the download page for previous versions.

RobertScheitlin__GISP

Nate,

I don't think that the search=Owner is correct.

search=x x is suppose to be the actual value that is searched for.
&exprnum=3 so this means you have 4 expressions defined in your xml file then right? Expressions numbers start at 0 as most all enumerations do.

YujingWu_0-1655992274048.png

NateRose

You are right on the "exprnum=3", should be 2 since I have 3 layers. As for the search=Owner, its an attribute in the CULPR field. Maybe this will help you see what I got going on. Still nothing when I change it to "exprnum=2" though.

<expressions>
             <expression alias="Status" textsearchlabel="Search Status (Owner/Renter) [ Example: Owner ]:">upper(CULPR) = upper('[value]')</expression>

<expression alias="Improvements" textsearchlabel="Search by Improvements [ Example: Y or N ]:">upper(Improvement) = upper('[value]')</expression>

<expression alias="Price" textsearchlabel="Search Price Range By Code [ Example: A($0-10,000), B($10,000-20,000), C($20,000-50,000), or D($50,000+)]:">upper(classcode) = upper('[value]')</expression>
            </expressions>

RobertScheitlin__GISP

Nate,

Hmm... If Owner is an attribute of the CULPR field than shouldn't the exprnum be 0? Because expression 2 is tied to the classcode field.

?search=Owner&slayer=0&exprnum=0&showdatagrid=true

NateRose

I thought from reading your pdf that the exprnum is the number or layer's you have setup for searching.

I tested the parameters that you posted after clearing my browser cache and still nothing. The search for "Owner" works fine in the Search Widget itself also. That's what's odd.

RobertScheitlin__GISP

Nate,

Now you have me confused...

Each layer can have multiple expressions defined for it so exprnum=2 would mean the 3rd expression for the particular layer you are specifying in the slayer.

So this code means:

?search=Owner&slayer=0&exprnum=0&showdatagrid=true

In layman's speak means:
Search the first layer defined in the SearchWidget.xml using the first expression defined for that layer, using a search value of "Owner"

Does that help?

NateRose

Robert,

Sorry for the confusion. I meant the number of expressions when I referred to the layers. I only have one layer setup and three search expressions.

I attached my SearchWidget.xml, maybe this will help.

If I have it set to slayer=0 and exprnum=0 as you mention it should work. Still no search on page load. I'm gonna try another layer and/or expression just to see if there is an issue with that.

Thanks for your time with this.

Nate

SearchWidget.zip

RobertScheitlin__GISP

Nate,

Do you not have a crossdomain.xml on your server? I would gladly test this for you but I can not as long as you don't have a crossdomain.xml at http://maps.co.stearns.mn.us/crossdomain.xml

RobertScheitlin__GISP

Nate,

Do you have the eSearch widget preloded as instructed in the pdf?

i.e.

<widget label="Enhanced Search" preload="open"
             icon="assets/images/i_search.png"
             config="widgets/eSearch/SearchWidget.xml"
             url="widgets/eSearch/SearchWidget.swf"/>

NateRose

Robert,

I do have the Search window set to preload.

<widget label="Search" left="100" top="50" preload="open"
                icon="assets/images/i_search.png"
                config="widgets/eSearch/SearchWidget.xml"
                url="widgets/eSearch/SearchWidget.swf"/>

I didn't have a crossdomain.xml file setup but I looked it up quick and built one at "C:\inetpub\wwwroot" so hopefully it works based on the esri documentation. It's accessible from the path http://maps.co.stearns.mn.us/crossdomain.xml.

Here is the app path:
http://maps.co.stearns.mn.us/TaxForfeit/bin-debug/index.html

RobertScheitlin__GISP

Nate,

You have missed some portion of the instructions some where because I can add your layer to my eSearch Widget and now that you have a crossdomain.xml in place this url:

http://gislap134/FlexViewer2.3/index.html?search=Owner&slayer=0&exprnum=0&showdatagrid=true&debug=true

Executes the search for me.

NateRose

Robert,

Thanks for testing it. I double checked the code vs the instructions and everything looks good so I'm going to start with fresh 2.3.1 viewer and update the code in that. I'm thinking maybe everything didn't get updated properly during the upgrade from 2.2 to 2.3. I'll let you know what I find.

Thanks again,

Nate

NateRose

Robert,

I'm running into the same problem with the new project as before. I started with a original copy of the 2.3.1 version of the viewer and updated the necessary code listed in the URL Search Configuration documentation but it still won't bring up any search results on page load.

Would you be willing to take a look at the code to see what might be going wrong? I've checked it over and over, but must be missing something since you tested the layer out in your copy.

Thanks,

Nate

url_search_files.zip

RobertScheitlin__GISP

Nate,

You missed this line in the MapManager.mxml instructions.

Update this function:
protected override function partAdded(partName:String, instance:Object):void
{
super.partAdded(partName, instance);
if (instance == map)
{
var cssStyleDeclaration:CSSStyleDeclaration =
styleManager.getStyleDeclaration("com.esri.ags.components.supportClasses.InfoWindow")
cssStyleDeclaration.setStyle("backgroundColor", getStyle('contentBackgroundColor'));
styleManager.setStyleDeclaration("com.esri.ags.components.supportClasses.InfoWindow",
cssStyleDeclaration, true);
//My Add
map.addEventListener(MapEvent.LOAD, mapLoadComplete);
//End My Add
}
}

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.