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; } } }

Selection Widget Updated Version

MarkHoyland

The Selection widget has a "Select by Attributes" and "Select by Location" option similar to ArcGIS.
Widget link: http://www.arcgis.com/home/item.html?id=20ed6af9ab204548bbf092d51b51fef8

Version 1.5 of the widget replaces version 1.0

Enhancements and fixes include:
*Each time a query layer was added it was also being added to the TOC. This has been fixed.

*When resizing the widget, the datgrid would not resize properly. This has been fixed.

*Uses paging for selection of unique value list. This means that ALL values will be parsed regardless of the ArcGISServer setting to limit responses. There is an option to ESC out of a large query. (This is only for the Unique list, not getting features).
I have included an ESRI TaxParcel Layer that has 18,000+ records. Get Unique Values on the PSTLSTATE field to see this in action.
Available on my example site. The URL is on the Widget download page.

*Aliases can now be used. It will now use the Alias as set in the Featureclass. You can also override the Alias in the SelectionWidget.xml config file.

*ArcGis layers that have joined tables will now work with fully qualified field names. (thanks Dasa for the idea)

*Styling for selection colours has been documented in the SelectionWidget.xml config file (example provided).

*Styling for datagrid has been changed. It can now also be styled in SelectionWidget.xml config file (example provided). (thanks Mehul for the idea)

*Changed initial uniquevalue query to use "text='%'" instead of "where '1=1'" for Mike.:)

*You can now override scale range for layers.

*Link field now has a prefix/suffix option in the SelectionWidget.xml config file (naming convention the same as Robert SCheitlin's esearch widget)

*Shape_area and Shape_length can be used in the fields.

Link to previous thread :http://forums.arcgis.com/threads/24151-Selection-Widget-for-SFV2.2-(with-a-query-builder)

Find more posts tagged with

Accepted answers

All comments

tanyabisen

Hi again Caroline,

I think I might have solved my problem.

When I was pulling in the url for the layer in the SelectionWidget.xml file, I was using the FeatureServer service instead of the MapServer service from my rest services directory. (The layer I am using is editible also.)

When I tried using the MapServer url I got the unique values list to populate.

Hopefully this fix will be as easy for you!

Ashlee

Dear All,

    I am unable to configure this widget. I configured the xml and when I click the feature its unable to retrieve the unique values.Following is the map service I am using : http://agis.pipetrakit.com/ArcGISPetroIT/rest/services/GAILDABPL/MapServer/29

This is what I have configured in the XML.
<layers>
     <layer>
            <name>Benchmark</name>
            <url>http://agis.pipetrakit.com/ArcGISPetroIT/rest/services/GAILDABPL/MapServer/30</url>
            <minscale>500000</minscale>
            <maxscale>10</maxscale>
             <fields>
                <field name="BM__NO_" alias="BM__NO_"/>
                
            </fields>
            <titlefield>Benchmark No</titlefield>
            <linkfield linkprefix="http://www.test1.com." linksuffix=".txt">URL_FIELD</linkfield>
            <infowindowfields>
             <field name="BM__NO_"/>
                <field name="LATITUTE" alias="Latitude"/>
                <field name="LONGITUDE" alias="Longitude"/>
                <field name="DESCRIPTIO" alias="Description"/>
   </infowindowfields>
        </layer>

Please anyone help me on this.

Thanks,
Tanya

DeanSeales

Hello,

I am trying to use this widget in Flexviewer 2.5; however, in spite preload="open" the widget does not open.

Thank you for your assistance...

PeteLovell

First off, thanks much for developing this excellent widget. I'm having a similar experience to Jared (post #29) where I am using the Selection widget on numerous layers, some of which provide unique values and others of which do not when I am entering a query. I didn't see a response to Jared's post so was wondering if anyone else had experienced similar difficulties and found a solution. Thanks!

EricGardecki

I'm using the version of this widget that is attached to a post above...the one for FV 2.5 (and date/time fix). I'm having the same problem as someone from a different thread (http://forums.arcgis.com/threads/24151-Selection-Widget-for-SFV2.2-(with-a-query-builder) was having. The layers that are used in the query in the Selection widget are being added to the TOC. This is causing messy issues with my popups. In that thread it says that it was fixed in the code but obviously I'm still having the issue. I'm only able to use the compiled version. Is there a different version I should be using? Has this truly been fixed?

Thanks

AngieAllison

Let me know if these updates work

Complied with Date fix and:
FLEX SDK 4.1 and AGS FLEX 2.5

date and time is still not working correctly. what i am seeing on the screen has all strange dates in the selection results. the top one i had says 12/31/1969 but the data is actually null?????
Thus the exported data is wrong as well.

AngieAllison

Hello, I believe the issue of the unique fields not showing up is due to how the query works. I believe the field that you are having issues with is a non-string field. If that's the case and you are working with the uncompiled version:

in utils/PagingQueryTask.as around line 184, you want to change query.text = "%" to query.where = "1=1"

I'm almost positive that change is reflected in the versions with the date and time fix found here:
http://forums.arcgis.com/threads/30179-Selection-Widget-Updated-Version?p=157653&viewfull=1#post157653

http://forums.arcgis.com/threads/30179-Selection-Widget-Updated-Version?p=157654&viewfull=1#post157654

http://forums.arcgis.com/threads/30179-Selection-Widget-Updated-Version?p=157756&viewfull=1#post157756

Let me know if that fixes the issue

it has not fixed the issue i have very strange dates in the queried data.

HaroldBostic

what is the exact issue you are facing

AngieAllison

what is the exact issue you are facing

the date fields do not display correctly, first it had the long numbers, so i updated the version - then it had fictisious dates - even where there should be null values. then i tried the version with the date and time fix and it has ficticious dates and times.
see attached. the first one is correct in the facility id install date should be null but on the 2nd and 3rd versions it puts in some strange date even for null values. the first one has that long number in it.

In your first image, what should the correct dates be? Are you using the compiled or uncompiled version? Is that particular map service available publicly so I can test it. How are the dates entered into the database? What is the backend database?

AngieAllison

hbostic;206896 wrote:
In your first image, what should the correct dates be? Are you using the compiled or uncompiled version? Is that particular map service available publicly so I can test it. How are the dates entered into the database? What is the backend database?[/QUOTE

in the images the first row should be null and the second row should be 1/1/1977. iam not sure if it is compiled or uncompiled. i got the zips from this forum. they look like they are compiled. i dont know how to use the uncompiled. mapservice is not public. enter the dates from a calender in arcgis desktop.. we are on SQLServer 2008R2.

AngieAllison

EVEN stranger yet. this picture is of a piece of pipe that was NOT converted into arcgis but edited and placed in Arc and it has the date before - says 1/23/2012 and should say 1/24/2012

SELECTIONDATE.jpg

AngieAllison

I can not get these dates to come in right no matter what syntax i try. they are showing the day before because of UTC i am guessing. have other widgets working with this format
<field name="INSTALLDATE" alias="date" dateformat="MM/DD/YYYY" useutc="true"/>
but this one will not and the null values come in with 12/31/1969 ?? any help is appreciated.

JaredCollier

I am curious about the proper url syntax in the linkfield to open a .pdf stored on our in house network. Web browsers can be set to open the pdf in the browser or in the Acrobat program. In our situation we need the pdf to open in Acrobat and at the file location not in a temporary location on the computer the user is clicking from. Previously we used this format in a WebADF application "file://///MachineName/folder/folder/file.pdf"

In the SelectionWidget.xml I can get the string to show up on the info window but it is not clickable. Below is my linkfield string example that shows up without being clickable:

<linkfield linkprefix="file:////machinename/inetpub/wwwroot/Flexviewer2.5_SelectionWidget/">Hyperlink_Formatted</linkfield> (Where Hyperlink_Formatted field looks like this "INFO/file.pdf")

Any suggestions as to what I am missing?

AntGiles

Mark,

Sorry to bring up an old point but I am trying to implement your widget into my application built on the following:

Flex Viewer v2.5 ArcGIS Server 9.3.1

The widget works great and as expected apart from the get unique values, which you have previously mentioned requires Server 10 onwards and I can see this in Firefox as an AMF request is sent to the server.

As I am working with the un-compilied code is there anything that can be changed to work against Server 9.3.1 (did your previous version get unique values before server 10 was released?)

Any help would be much appreciated

Regards

Anthony

CarrieMunill

This is an older widget I know, and possibly a long shot, but has anyone been able to get this widget working in Flex SDK 4.6 and ArcGIS Viewer for Flex 3.0? Perhaps a better question might be: does anyone have an uncompiled version of the Selection Widget that will work in Flex SDK 4.6 and ArcGIS Viewer for Flex 3.0 out there and is willing to share? I am having the same issue that some others in this thread have experienced, namely the Unique Values list is not populating. My data is on an ArcGIS Server 10.0, and problem is happening with a couple of the example data sets as well (but not all of them).

Actually what happens is that it populates correctly the first time I click Get Unique Values but every time thereafter returns nothing. ("Processing: 0 of 1131" flashes briefly but the list does not populate.) Get Unique Values runs when I double click the field name for the very first time as well to add it to the selection query and the unique value list populates, but only that first time. I can manually type in the query and the rest of the functions work no problem, despite the fact that it was compiled for a different version. I have to shut down and restart FlashBuilder to get it to work again (one time, and then it's back to not populating the list). I've done a little bit of digging and wonder if it is related to paging in general (or the fact that "dispatchEvent" (found in the SelectionWidget.mxml and PagingQueryTask.as) has been deprecated)? I do need to be able to query (or select) on multiple fields within a single layer (similar to the Query Builder in Desktop).

Any suggestions would be much appreciated, thanks!

Carrie

mburge

Mark,
Is there an uncompile version of this widget? And what is the latest version? Is there a 2.5 version? Thanks

mburge

Mark,
Is there an uncompile version of this widget? And what is the latest version? Is there a 2.5 version? Thanks

mburge

Sorry, meant to say "uncompiled".

mburge

Mark,
Does 2.5 version have an uncompiled component? If so, where can I find it to download? Thanks

JeffersonFerreira_Ferreira

Dear Colleagues;

Please, let me ask you a question (apparently simple) about the Selection Widget. Maybe 'cause my "middle-of-the-road" english understanding or 'cause the lack of familiarity with sql spatial operators, Im facing difficulties to distinguish between "that are completely within" and "that are is (fully) inside". For me this statement appear to have a grammatical error in "that are is...". I've searched a lot at the internet but cant find this specifically issue. If you could clarify me I'll be grateful.

Thanks

JeffersonFerreira_Ferreira

Hi all;

No problems with the operation of the tool. However when we opened for the first time an error message appears. The Error #2124 window appear (see attached file), then we close and the tool works normally. What could be happen? Any suggestions?

Untitled.png

RhettZufelt

I am trying to get the selection outline color to match that of my eSearch widget. The coding is very similar, but does not seem to work correctly in the SelectionWidget.

If I don't change it in the config.xml or hard code in the mxml, I get the default browinish color. If I change it in the config.xml or the mxml, it turns to a green color, no matter what I set it to (red, black, white, etc. always is the same green color). In the eSearch widget I set it to 0x00FFFF and get a nice light blue outline.

Has anyone figured out how to make this change "take effect" in the SelectionWidget?

Any ideas,

R_

RobertScheitlin__GISP

Rhett,

This is because the selection widget uses a feature layer in selection mode and the default selectioncolor is yellow which is applied as a filter that blends with the symbol color. To fix this just make these changes in the selection widget:

//New function
            private function removeGlow( fl:FeatureLayer ):void
            {
                var len:int = fl.numChildren;
                var dObj:DisplayObject;
                for ( var i:int = 0; i < len; i++ ) {
                    dObj = fl.getChildAt( i );
                    if ( dObj.filters ) {
                        dObj.filters = [];
                    }
                }
            }
            //Updated function
            protected function featureLayer_selectionHandler(event:FeatureLayerEvent):void
            {
                removeGlow(event.featureLayer);
                
                dispatchEvent( new Event( 'featurelayer_selection', true ) );
                
                var flEvent:SelectionFeatureLayerEvent = new SelectionFeatureLayerEvent(
                    SelectionFeatureLayerEvent.LAYER_RESULTS,event.featureLayer);
                dispatchEvent(flEvent);
                
                if (event.type == FeatureLayerEvent.SELECTION_CLEAR)
                {
                    this.showInfoWindow(null);
                }
                
            }

RhettZufelt

Thanks again Robert, works like a charm.

No wonder I couldn't figure it out. Guess I should have tried a color that blends with yellow to make cyan 🙂

R_

MikeDahm

Any plans for this widget to be updated for Flexviewer 3.0?

JeffersonFerreira_Ferreira

Anyone have an idea about the error #2124?

RhettZufelt

I have updated this part of the init() function and it seems to be working fine in 3.0: Keep in mind that I am no pro by any means, but this seems to work.

     for (var i:int = 0; i < lyrList.length(); i++)
     {
      var lyrURL:String = lyrList.url;
      var lyrLabel:String = lyrList.name;
      
      var featureLayer:FeatureLayer = new FeatureLayer(lyrURL);
      featureLayer.name = lyrLabel;
      var l1lst:XMLList = (lyrList.maxscale as XMLList)
      var l2lst:XMLList = (lyrList.minscale as XMLList)
      
      //Override the min and max zoom scale if they are in the config   // not sure why couldn't test directly but had to create varable first???
      if (l1lst.length() > 0 )
       featureLayer.maxScale = lyrList.maxscale;
      if (l2lst.length() > 0 )
       featureLayer.minScale = lyrList.minscale;
      
      featureLayer.addEventListener(LayerEvent.LOAD, featureLayer_loadHandler);
     }
     
.........
........
........
     //ViewerContainer.dispatchEvent(new AppEvent(AppEvent.DATA_CREATE_INFOWIDGET, data, infoReady));
     AppEvent.dispatch(AppEvent.DATA_CREATE_INFOWIDGET, data, infoReady);

I still get a couple warnings about "Data binding will not be able to detect assignments to length" for the end of SelectByAttributes.mxml and SelectionResults.mxml but it is working.

R_

JeffersonFerreira_Ferreira

I have updated this part of the init() function and it seems to be working fine in 3.0: Keep in mind that I am no pro by any means, but this seems to work.

     for (var i:int = 0; i < lyrList.length(); i++)
     {
      var lyrURL:String = lyrList.url;
      var lyrLabel:String = lyrList.name;
      
      var featureLayer:FeatureLayer = new FeatureLayer(lyrURL);
      featureLayer.name = lyrLabel;
      var l1lst:XMLList = (lyrList.maxscale as XMLList)
      var l2lst:XMLList = (lyrList.minscale as XMLList)
      
      //Override the min and max zoom scale if they are in the config   // not sure why couldn't test directly but had to create varable first???
      if (l1lst.length() > 0 )
       featureLayer.maxScale = lyrList.maxscale;
      if (l2lst.length() > 0 )
       featureLayer.minScale = lyrList.minscale;
      
      featureLayer.addEventListener(LayerEvent.LOAD, featureLayer_loadHandler);
     }
     
.........
........
........
     //ViewerContainer.dispatchEvent(new AppEvent(AppEvent.DATA_CREATE_INFOWIDGET, data, infoReady));
     AppEvent.dispatch(AppEvent.DATA_CREATE_INFOWIDGET, data, infoReady);

I still get a couple warnings about "Data binding will not be able to detect assignments to length" for the end of SelectByAttributes.mxml and SelectionResults.mxml but it is working.

R_

Is it for the error #2124??

RhettZufelt

I do not get any errors. Just a few warnings about length not being bindable.

R_

JeffersonFerreira_Ferreira

I do not get any errors. Just a few warnings about length not being bindable.

R_

There are many people receiving this error #2124. The widget works fine, every first open it presents this message. I reviewed all the xml and mxml and can't identify what could be wrong.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

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