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-for-FlexViewer Part II

RobertScheitlin__GISP

All,

I am pleased to announce the next release of my eSearch Widget.

http://www.arcgis.com/home/item.html?id=5d4995ccdb99429185dfd8d8fb2a513e

Version 2.5.1.7 - 4/19/2012
* Added ability to search (flat/standalone/no geometry) tables.
* This time all Zooming uses the same scaling (popup, datagrid, widget results, zoom to all).
* Added Relates icon/button to datagrids so that you can click on it in the datagrid to
open relates choice dialog.
* Move all skins to a skins package for cleaner organization.
* Links that are not associated with a field now work.
* Ability to disable the relates tab in the fixed widget is now configurable.

Najděte více příspěvků označených jako

Accepted answers

All comments

SamanthaEdwards

I am having a problem with the widget configuration automatically loading. The widget adds fine but the configuration is empty, thus leaving me with the message: no search layer defined. I've gone through all the pdfs but I'm obviously missing something. Any suggestions?

Thanks,
S

RhettZufelt

Are you trying to search a table without loading a layer also? I see the latest version has some errors if there are no layers defined.

R_

RobertScheitlin__GISP

That is because searching tables was always designed as a add on ability and not a standalone ability. Simply put the way I have the widget designed you can not have all tables and no layers as it stands right now (been that way since I introduced tables in the widget).

RhettZufelt

Makes sense, though I had not tried it before to know if it was always this way.

I was just trying to find ways to re-produce this error. This was one of them (most common seemed to be my syntax of the layer name/fields

).

R_

RhettZufelt

Really like the add/remove to/from selection option. A handy feature.

I did notice that if you switch to a different layer/table, then the selection is cleared.
Don't even know if it is possible without a huge re-write, but a nifty "enhancement" would be to allow it to add to the selection regardless of which layer/table it is from (I.e., don't clear the selection on layerChanged).

R_

RobertScheitlin__GISP

Rhett,

That could be useful but it definitely would involve a major re-write as each layer has different fields that are returned and thus a different datagrid is necessary and handling the multiple selections when allowing for the spatial search would be a nightmare.

EvanSepa1

When my search results populates the bottom table and fields contain blanks, the auto width makes these fields unnecessarily large.

Is there a way to configure the way the auto width controls blank fields? Setting the width to that of the header would be ideal.

See attached pic.

Thanks

temp.png

RobertScheitlin__GISP

Evan,

So all the rows have empty strings returned for those columns? The auto size columns code uses the column header if it can not find any data in the columns attributes...

EvanSepa1

My Mistake, it was a simple coding error . . . my field names were incorrectly included as "Middle_Name" instead of "Middle_Nam"

Thanks for your quick response . . . I have another question . . .

In the installation instructions you indicated to

- Add the following lines to the DrawWidget.mxml in the init function under this line 'graphicsLayer = new GraphicsLayer();'
graphicsLayer.name = "Draw Features";
graphicsLayer.id = "Draw Features";

In the regular Draw Widget folder the DrawWidget.xml only contains the following . . . Am I completely in the wrong place is this not where you intended?

<?xml version="1.0"?>
<configuration label="Draw and measure (default)">
    <distanceunits>
        <distanceunit id="km"/>
        <distanceunit id="mi"/>
        <distanceunit id="m"/>
        <distanceunit id="ft"/>
        <distanceunit id="yd"/>
    </distanceunits>
    <areaunits>
        <areaunit id="sq km"/>
        <areaunit id="sq mi"/>
        <areaunit id="ac"/>
        <areaunit id="ha"/>
        <areaunit id="sq m"/>
        <areaunit id="sq ft"/>
        <areaunit id="sq yd"/>
    </areaunits>
</configuration>

RobertScheitlin__GISP

Evan,

Those instructions are for the Enhanced Draw Widget (not the OTB one) and are also for the uncompiled source code. Notice the DrawWidget.mxml not xml. Anyway those instructions are obsolete and I will remove them for the next version.

EvanSepa1

Thanks for clarifying . . .

I'm looking for a reason why my feature layer won't respond to the graphical search.

Is simply having <spatialsearchlayer>true</spatialsearchlayer> enough to turn on the capability for graphical search on a layer?

RobertScheitlin__GISP

Evan,

The graphical and spatial searches are two different things. What do you mean that you can not get the graphical search to execute? Are you clicking the search button if you have the "enable multi-part graphics" checked?

EvanSepa1

I realize the spatial and graphical difference now . . . I just picked up the widget yesterday and I'm trying to apply it to my first flex application 🙂

I disabled spatial search. It's the graphical selection method that produces no results on my layer. I have multipart set to false. But turning multipart on and pressing search also provides no results.

I uploaded my work in progress.

http://gis.northfrontenac.com/cemetery/ArdochCommCemetery/

RobertScheitlin__GISP

Evan,

Try changing the spatialreference in your eSearchWidget.xml to 26918 instead of 102003.

RobertScheitlin__GISP

Evan,

I am not sure where the wkt in your map element came from but if you remove it and add wkid="26918", everything works fine (this is in your main config.xml).

RhettZufelt

Robert,

while on the subject, I see that there is a geometryserver AND spatialreference set in the eSearchWidget.xml.

Was wondering if these should match, or how they "interact" with each other. Does one override the other or what?

R_

EvanSepa1

Evan,

I am not sure where the wkt in your map element came from but if you remove it and add wkid="26918", everything works fine (this is in your main config.xml).

This worked. Thanks for all your help, much appreciated 🙂

RobertScheitlin__GISP

Rhett,

The spatialreference is the WKID that the buffering in this widget will use and the geometryserver is the url of the geometry service that the widget will use for buffering, simplifying, etc.

RobertScheitlin__GISP

All,

New Version now available.

Version 3.0.15 - 11/28/2012
* Fixed an issue when printing after a search and the search layer did not have individual
layer symbology specified in the eSearchWidget.xml
* Fixed issue where you could not use just tables in the eSearchWidget.xml
* Fixed issue where clicking the clear button before running a search produces an error.
* Fixed issue where new/add/remove selection button is not in the GUI when there is only
one layer configured.
* Removed the Zoom All button when the results are a table.
* Validate the returned geometry before attempting to zoom to all selected features.

RhettZufelt

Nice job. However, I will still get the null value error if I click the clear button before a search.

not sure if it will affect anything else, but I modified the clear() function to this and it "fixes" it:

    if (qFeatLayer){                     // My Change
        qFeatLayer.clearSelection();
    }                                    // End My Change
    graphicsLayerBuffer.clear();
    graGraphicsLayer.clear();
    clearMessage();

Also, I see we can now search for blank/spaces with the uniquevalues option, but will not populate the list with or select any nulls.

Thanks again, this widget just gets better and better,

R_

RobertScheitlin__GISP

Rhett,

Well I know I put those lines in there for checking if the qFeatLayer was null or not but I must have clicked undo at some point... As far as the blanks and nulls I will have to look into this, but really that should be handled by the data producer and should not have to be handled by the developer (i.e. there should be one of the other not both empty strings and nulls).

RhettZufelt

I agree that the null should be handled by the data producer. My issue is that I update my data from a join to an oracle database on a regular basis. Once you have rows in your feature class, you CAN NOT add a non nullable field to the feature class (so, why does it even give you the option? just so it can give you an error I guess). So, every time I update it, it sticks all the nulls in there.
Also, any time you add a feature, it automatically assigns a null to every field you don't populate (since I can't set to not accept nulls)

I had my script, after the updates, go in and converted all the nulls, and modified the fields to not allow them. However, it seems that each service pack (except for 5) breaks something in the arcpy package so I have to go re-do all my scripts again. Finally just decided to let ESRI tell me what I "want" and live with it. So, now I have both blanks and nulls.

personally, I don't think the nulls should even exist. Well, for that matter, they don't

. In other words selct for item <> "non null value" does not select nulls. Seems like if it isn't equal to "non null value" it should select it, but appearantly, it is not not equal to it either. So far I've never came across a case where I would prefer a null over a blank.

Maybe now that version 10.1 is out and I have sp5 on my 10.0 I can re-visit this without it breaking (doubt there will be a service pack 6).

R_

RhettZufelt

Thought maybe since I had both in there it was causing an issue so I tried both.

With all blanks it will populate the dropdown with a blank option.
Will nulls and no blanks or spaces, there is no null option.

R_

RobertScheitlin__GISP

Rhett,

What type of field is the nulls in? I have tested a FC with a string field with nulls and the uniquevalsfromfield works fine (Adding the null to the list).

Update: I have now tested on a String field with a mix of " ", nulls, and various strings and it works fine. I have also tested a double field with numbers and nulls and the null option is listed in the drop down. Are you sure your FC data has <null>? Are you using every row in the FC with nulls or something?...

RhettZufelt

Not sure what is going on here.

OSE_ID (Type: esriFieldTypeString, Alias: OSE_ID, Length: 15 ) 
testnull (Type: esriFieldTypeString, Alias: testnull, Length: 50 )

I have reduced it down to two fields for testing. I have tried with only blanks, only spaces, or only nulls (and combinations) in the OSE_ID field, and it will not put the space, blank, or null in the picklist.
However, I have all three (blanks, spaces, nulls) in the testnull field and it seems to be working perfectly. It adds a blank value (which selects both blanks and space), and a null (which selects all nulls) and the all (which selects all, including blanks and nulls). (the OSE_ID field was existing in the featureclass, the testnull I added with ArcMap.)

Not sure what is going on with my data and the OSE_ID field, but it appears to be related to my data.

Will have to look into it more come monday.

Also, is there some way to put a dateFormat tag somewhere to make it possible to use the uniquvaluefromfield with esriFieldTypeDate?
If I try to use this option on a date field, it populates the list with the huge numbers (ms from start date/time I believe) and not the formatted date. As such, all searches for a date will fail as it seems to submit the ms value for the query, but the data in the field is actually DD/MM/YYYY. (It works, of course, if I put my date in a text field, but it doesn't sort properly when done this way.)
As is, it will select any null values in the date field, and if you select all, it gets them all. Just can't get individual dates that are not null.

R_

Update: thought maybe since I didn't have any values with data in the testnull (other than blanks, spaces, and nulls), that might be why it is working. Just added some data to some of the values, still working as designed, not sure what is up with my one field.

RobertScheitlin__GISP

All,

A new version is now available.

Version 3.0.16 - 12/3/2012
* Fixed an issue with blanks (when using isrequired="true") and empty strings be treated
as equal when using uniquevalsfromfield.
* uniquevalsfromfield can now use a datefield and use the dateformat and useutc attributes.

RhettZufelt

Nice. Have not had a chance to really test it, but haven't broken it yet 🙂 Definatly worth another point....

I did notice the config.xml example still has this line:

 <disablebuttons>result</disablebuttons><!--possible values one or more not all four search types comma separated text,graphic,spatial,grid,datagrid -->

I see the pdf has been updated, just thought I'd point out that the "result" option is not in the xml example.

R_

MattShetzer

Robert,
I'm using your Esearch tool (v2.5.1.7), and have noticed when I use the numberformat attribute it actually truncates the number. I need to round the number as I want the value shortened to be consistent with the precision attribute for the popup.

I've reviewed your enhancement notes\configuration documents, and don't see it in there, therefore I didn't update my version.

Is it possible to round values using the esearch tool.

Thank you in advance.
Matt Shetzer

RobertScheitlin__GISP

Matt,

So many fixes and enhancements have occurred since 2.5.1.7 as the last 2.x API version of this widget is at 2.9.0.1.... But you are correct there is no configurable option to have the number round. You can make a change in the code to account for this but if you are using the compiled version then there is nothing you can do. As you probably know I do not enhance old versions of my widgets.

MattShetzer

Thanks Robert for the quick reply. We are getting ready to upgrade to API 3 in an month or two, and I will upgrade to the latest esearch widget at that point. If I could request that in a future enhancement. The biggest reason is the different display of the same data from the popups.

Thanks for all you do, and supplying an impressive search tool.

Matt Shetzer

Připojte se ke konverzaci

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

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