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.

Encontre mais publicações marcadas com

Accepted answers

All comments

RobertScheitlin__GISP

Peter,

I do not see that at all... Version 3.0.5 did not have that issue and neither does 3.0.6 which you can test and see on my live preview site. If you do a traffic camera search on the live preview site it formats fine using dateformat="MM/DD/YYYY"

PeterHoffman

Robert,

I have attached a png file of the results - conveyed date and acquired date fields.

Peter

esearch2.png

RobertScheitlin__GISP

Peter,

Are you sure you replaced your SearchWidgetFixedDG.swf if you are using the compiled version? If you are using the uncompiled version do you have the SearchWidgetFixedDG.mxml in your projects modules list?

PeterHoffman

Robert,

Yes, I was using an old version of the SearchWidgetFixedDG.swf.

Thanks for your help.
The esearch widget is great and I use it extensively.

Peter

EdinZametica

I use version 3.0.6 with uncompile SearchWidgetFixedDG component, and I have a problem with auto open datagrid.
Data grid is always closed except when you move the mouse, then it opens ... I ask for help because the earlier versions were working ...

My config:

<widget left="0" right="0" bottom="0" url="widgets/eSearch/SearchWidgetFixedDG.swf" config="widgets/eSearch/SearchWidgetFixedDG.xml"/>

<?xml version="1.0" ?>
<!-- See Enhanced Search Widget Fixed Datagrid Setup.pdf for detailed explanation -->
<configuration>
 <autohide>true</autohide>
</configuration>

eSearchWidget.xml

....
<links></links>
   <zoomscale>25000</zoomscale>
   <autoopendatagrid>true</autoopendatagrid>
.....

Thanks Robert,
Edin Z.

RobertScheitlin__GISP

Edin,

The way that it is functioning in 3.0.6 is the way that the autohide datagrid was always intended to work. In previous versions clicking on a popup and some other odd events where causing the datagrid to appear and that behavior was fixed.

EdinZametica

Edin,

The way that it is functioning in 3.0.6 is the way that the autohide datagrid was always intended to work. In previous versions clicking on a popup and some other odd events where causing the datagrid to appear and that behavior was fixed.

Robert,

Just that I thought. When you make a search, the table does NOT go into the popup, when clicking on the relationship, rather it is automatically appeared table, and not now.

I preferred the previous version with automatic appearance of tables, but OK if it is not provided then nothing ...

Great thanks...

Edin Z.

Gabriel_J_Ortiz_Rico

Robert, you can't imagine the HUGE apportation you have done to the ArcGIS Server users community. Thank you for your dedication and for all your expertise. Thank you!! Thank you!!! Thank you!!! Your work is great!!!

I would like to comment you one small bug and also ask you three questions:

Possible bug: There is a customizable parameter that the widget is not interpreting properly (at least in 3.0.5 and I think in 3.0.6 is not corrected...) In spite of setting the nobufferoutlinecolor to: <nobufferoutlinecolor>Sin Color</nobufferoutlinecolor>, the widget shows the default label (No outline color).

And the questions:

1/. Is possible to limit the width of the text input box in an expression? I mean... the input text box in an search expression spans from one end of the widget window to the other, and I would like to put two search conditions IN ONE LINE, in order to have all 4 search conditions at view in the widget, so that the user does not have to scroll down. If this is not possible, would it be possible to control the height and width of the widget window? (maybe this is documented, but I didn't find out how).

2/. If I have 4 search criteria within one search expression, is it possible to leave blank one of the search criteria and execute anyway the search as if it was populated? It would be like using a wildcard (% ? *). In my application the user has to execute a query using 4 criteria what should be transformed in a WHERE parameter1='a' AND parameter2='b' AND parameter3='c' AND parameter4='d'. What I want to do is to execute this query even if there is no value in the parameter3 or parameter4 (that is, selecting any value in parameter3 and in parameter4).

3/. The third question is about security. I suppose that all the SQL sequences commited through the widget use the REST or SOAP exposed services which, I suppose, are cleaning and sanitizing every SQL sentence before executing it in the backend. I know that this matter is related more with the whole ArcGIS Server environment rather than with the widget, but if you or others could talk a little bit about this subject it would be great.

Thanks again for sharing with the community.

RobertScheitlin__GISP

Edin,

So your enhancement request is that the fixed data grid would show itself when a search is exectuted and remain visible until the user mouses over and then out?

EdinZametica

Edin,

So your enhancement request is that the fixed data grid would show itself when a search is exectuted and remain visible until the user mouses over and then out?

Robert,

Respect,
That's there

Edin Z.

RobertScheitlin__GISP

Gabriel,

Bug with the label being ignored is fixed for next release (thanks for reporting this).

No there is way to much code in the widget that does the sizing of the inputs and autoscrolling when you tab to another input etc. You can define the widgets size and that is a basic (all widgets) configuration of adding the width and height attributes to the widget in the main config.xml in the widget tag.
I will add this as an enhancement request. Currently there are checks made to ensure all fields are filled before executing the search. The draw back to this being changed is that the search will no longer be able to be triggered by pressing the enter key as I will not know if the user pressed enter unintentionally or not.
I don't have knowledge of the background sanitizing processes done by ArcGIS Server or if any even exists. But when you define the SQL in the xml you limit what SQL injection could occur.

Gabriel_J_Ortiz_Rico

Thank you Robert. The problem is that in spite that you define the SQL statement in the XML, there are a number of techniques to append another actions to such predefined SQL by the use of different characters (one of the most resourceful is the use of ; ) This is the basis of the SQL injections, actually.

My asking perhaps should have to be diverted to another part of the forums, but it is interesting to consider this aspect. With this new technology we often expose information led by the huge possibilities and often we don't give a thought to the hidden hazards.

JORGELAGOS2

Jorge,

There is no way to completely hide the relates tab if you are using the fixed datagrid. There is the disablerelatestabinfixed attribute on the floatorfixed element as covered by the documentation.
<floatorfixed disablerelatestabinfixed="true">fixed</floatorfixed>

Hello robert thanks that did it. Now, is there any way to do a eSearch that will return all the values on a layer? I have a field named ProjectNumber. I would like to have all the Projects returned so later I can display them in the datagrid from where I can sort and access them?

I am partially accomplishing this with the regular Query widget which allow me to query 1=1 to obtain all the records but I really would like to access them from the datagrid.

Thanks

Jorge

RhettZufelt

Hi Robert,

Since this seems to be the latest "enchancement" thread for esearch, I have one for you.

The autofit columns to data in the fixed DG is a great feature. However, it seems that it will only autofit to the column width of the attribute data, and not the column heading itself. For some of my fields, I have a longer field name than any of the data so the column sizes itself to where the column name doesn't fit. I can add extra spaces to the end of the field in the config.xml to "fudge" it, so there is a simple workaround as long as my column heading is at least as long as my shortest attribute.

[ATTACH=CONFIG]17138[/ATTACH]

Would be slick if the autofit included the column heading length as well.

R_

untitled1.jpg

RobertScheitlin__GISP

All,

New version available:

Version 3.0.7 - 8/21/2012
* Tab labels are now configurable in the Fixed data grid (use the SearchWidgetFixedDG.xml).
* Fixed nobufferoutlincolor label being ignored in the eSearchWidget.xml
* Fixed show and hide animation on Fixed Datagrid.
* Fixed datagrid (if autohide) will show when a search is executed and hide with results are cleared.
* If multi field expressions are used, now all fields DO NOT have to be filled.
* Fixed PopUp Attachment Issue.

RobertScheitlin__GISP

Rhett,

Version 3.0.7 should work better with the column label size issue you were seeing.

RhettZufelt

Great, I will give it a go.

Also, when using the float DG, is there a configure/change somewhere to determine where the floating DG opens up? By default, it seems to open in the center of the screen, which is also where the zoom to and showHighlight is, so it covers it up. Have to manually move the float DG off to the side every time to see the popup and selected feature.

Thanks again,

R_

RobertScheitlin__GISP

Jorge,

Just the way you did it in the QueryWidget just use 1=1 in the expression for the eSearch.

RobertScheitlin__GISP

Rhett,

Nope that is not configurable. And it is not on my list either, but I will consider it.

RhettZufelt

Looked around some trying to figure it out.

What mxml would that be controlled in?

R_

bbollin_1-1738282522817.png

RobertScheitlin__GISP

Rhett,

It is a bunch of places in the eSearchWidget.mxml.

PopUpManager.addPopUp(myfloatdg,map,false,PopUpManagerChildList.POPUP)
                            PopUpManager.centerPopUp(myfloatdg);

Gabriel_J_Ortiz_Rico

I get this error: error #1009 when trying to search with this expression:

<expression alias="PolÃgono, Parcela, Recinto" textsearchlabel="">
 <values>
    <value prompt="PolÃgono: (ej. 19)">POLIGONO = [value]</value>
 </values>
 <values>
   <value prompt="Parcela: (ej. 111)">AND PARCELA = [value]</value>
 </values>
 <values>
   <value prompt="Recinto: (ej. 9)">AND RECINTO = [value]</value>
 </values>
</expression>

Please note that all the fields are numeric. I also tried a simpler search expressiÃ³n with only one condition:

<expression alias="PolÃgono, Parcela, Recinto" textsearchlabel="">
 <values>
   <value prompt="PolÃgono: (ej. 19)">POLIGONO = [value]</value>
 </values>
</expression>

The result was the same: error #1009. No matter if you populate all the textboxes or not. Always get error.

I also saw a different behaviour depending of the data type of numeric fields. In the case of the simple expression POLIGONO = [value] if the field is Long Integer I get this error:

[RPC Fault faultString="Unable to complete operation." faultCode="400" faultDetal="Unable to complete Query operation."]

However, if the field is type Double, the search is executed without problems. Is someone else finding this problems with this numeric data types?

Thanks for your help.

RobertScheitlin__GISP

Gabriel,

With your multifield expression you need to be sure to add a space in frontt of each and (as I have in my examples) or your expression will be submitted looking like this to the server: POLIGONO = 12AND PARCELA =34AND RECINTO = 3 instead of POLIGONO = 12 AND PARCELA =34 AND RECINTO = 3. So my next question is are all three fields numeric? If not then you need single quotes for strings. I will do some testing on a long field type today.

UPDATE* I have tested a LONG type field and had no issue with the search.

Gabriel_J_Ortiz_Rico

Yes, Robert, all the fields are numeric. I did test with the space and without space, and always get the same error. In fact, the expression works with and without the refered space before the AND operators whenever the fields involved are type double. When I include the search in a LONG INTEGER is when I get the error.

If I have 4 fields: municipio (long integer), poligono (double), parcela (double), recinto (double). All my expressions work perfectly with all the conbinations of the double fields. Several multifield searches works without problems. However, the simplest expression across the long integer field produces the error (even if isn't a multifield expression). That is, it works perfectly until I include a long integer field.

I will do more testing but I am running out of options...

RobertScheitlin__GISP

Gabriel,

What version of ArcGIS Server and What service pack are you using? I recall esri had an issue with some field types that was resolved in a service pack.

Gabriel_J_Ortiz_Rico

ArcGIS Server 10.0 and in that server I have applied only SP3

RobertScheitlin__GISP

Gabriel,

Yep, I would get up to SP 4 or 5, 4 is what I am running and I tested a long int and it worked fine.

EdinZametica

Robert,

Version 3.0.7 is just what I need, Great, Thanks..., Respect...

Edin Z.

RhettZufelt

Robert,

I have the 3.0.7 version (love the Alt/click option BTW) running now.

I have a table joined to a polygon dataset, select to show only matching values, then publish to service.

I then have the esearch searching the polygon data, and returning to the grid values from the polygon data as well as from the joined fields.

Everything seems to be working fine unless I try any kind of sort. If I have this in the code

sort="asc|1|string"

I will get the error. If I have no sort tag in my field, then everything is working fine unless I click on a column heading to make it sort, then I again get the error.

[ATTACH=CONFIG]17167[/ATTACH]

Have also noticed that once I try to sort and get the error, any time I hover over the resultsState on the widget I get a similar error:

[ATTACH=CONFIG]17168[/ATTACH]

Do not get this error on hover or click of either DG, but only on the resutState window.

Also, can not reproduce on dataset without joined fields.

R_

untitled2.jpg

untitled1.jpg

JORGELAGOS2

Jorge,

Just the way you did it in the QueryWidget just use 1=1 in the expression for the eSearch.

Sorry Robert but I don't know how to code 1=1 in the eSearch?

In the Query was:
   <query>1=1</query>

but in the eSearch the code

    <expression alias="Project Railroads" textsearchlabel="Enter NAME or FEATURE_ID below">
    <values>
           <value>NAME like ('%[value]%') </value>
    </values>
</expression>

How can I replace 1=1 in this search expression?

Thanks again

Jorge

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Entrar
Registrar

Links Rápidos

Todas as Comunidades
Publicações Recentes
Conteúdo Seguido
Ajuda da Comunidade

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