Latest Contributions by AngieAllison

Marie,    If you notice post #68 That issue is fixed in version 3.3.2. yes i ran accross that today !!  Thank you for the quick response on those changes !!  I am totally up and running and i am positive the end users are going to love this.  So much easier to use than the old query widget.  Thanks again for your help.  We are goin gto use this as well as a way to PRINT data.  So i careted some searches that are by a facility id and coupied it out 10 or 12 times and then they can enter different facility id's, do the search and get the DATA into excel !!!  awesome !!  we have wanted to print data for a long time. ... View more

Marie,    Yes you should always use your own geometry service as esris gets a lot of traffic. Changing the spatialreference will depend on what spatialreference your basemaps are in. If you are using esris basemaps then NO. If you are using all of your own basemaps and they are in WKID 3418 then yes. Thanks for the info.  I am up and running now. Aside from the zoom to layer as Patrick talked about.  Thanks for this wonderfull widget.  The end users will love being able to create there own "reports". ... View more

Robert, do i need to set  <geometryservice>http://tasks.arcgisonline.com/ArcGIS/rest/services/Geometry/GeometryServer</geometryservice> to my own Geometry service or can i use this one? Also do i need to set this  <spatialreference>102003</spatialreference> to my own wkid which is 3418?? ... View more

Hello, I am using the latest compiled eSearch version widget 3.3.1 in a new ArcGIS API 3.3 for Flex site and I am experiencing different results with my searches than when using the previous eSearch version 3.0.4 in an ArcGIS API 3.0 for Flex site.  When I search for a polygon or point feature that returns enough points to zoom out to a scale threshold that the feature is not displayed at, the selected features are not showing up on my map.  The search results window or the data grid will display the attributes of the features found and you can mouse thru the data and the tooltip window will move around on the map, but not until you zoom in to the scale threshold of the feature you searched on will they be displayed.               Is there something that I missed in upgrading my site and widget to the latest version?  In version 3.0.4, when you would search for these same features they would be displayed on the map at any scale beyond the scale threshold that was set on the feature and I am looking for that same functionality so users will see the results immediately without having to zoom in to the scale dependency of that feature.  Thanks, and any help would be appreciated. I am having this same issue.  Did you find a solution? ... View more

omg am i backwards?  numbers get the quotes or text gets the quotes? so yeah ..........  SORRY I was doing them backwards,  I'm a dork.  Sorry to bother ... View more

Thank you Robert.  When do you anticipate that release? i am having another quirky thing happening.  I have a field Material that i could not get to run the query and i finally added the quotes to the value and it runs and it is definatley a text field omg am i backwards?  numbers get the quotes or text gets the quotes? ... View more

Marie,    In the next release you will be able to specify the Text Qualifier in the eSearchWidget.xml and this would allow you to use a single quote instead of a double and that would help for your data having the double quote in it for inches. Thank you Robert.  When do you anticipate that release? i am having another quirky thing happening.  I have a field Material that i could not get to run the query and i finally added the quotes to the value and it runs and it is definatley a text field ... View more

Marie,    The fact that your data has 2" the double quote is throwing excel for a loop... Normally the " is used as a text qualifier and the fact that your data looks like "2"","26007887", etc, etc it is an issue for excel. In excel if you set the Text Qualifier to none than you will see how it is suppose to work minus the double qoutes wrapping each column. ok thank you for all your hard work on these widgets ... View more

When i do the export to text it does not come out right so that i can Import into Excel.  It's like the seperators don't come out correctly or something? attached is the text file, the csv fiel and a word doc showing excel. i had to change the csv file to .doc to get it to upload. ... View more

Thanks Robert i will try it. ... View more

Also - the date value that you changed??  i am trying to do a greater than or equal to on the date and it seemed to be working the way i had it.  is it wrong??  Is it possible to do a "between" dates ?? Ok Robert I am in process of updateing all my widgets and Flex Viewer to 3.3 so i can use the full capability of this widget.  i still am not able to have 2 queries with domain values.  I am taking the date out for now just to eliminate that problem so here is the piece of the xml    <expressions>     <expression alias="Material" textsearchlabel="Search Mains:" isvaluerequired="false" autosubmit="false">      <values>       <value prompt="Material" field="MATERIAL" usedomain="true" isvaluerequired="false" autosubmit="false" >MATERIAL = '[value]' </value>       <value prompt="Diameter" field="DIAMETER" usedomain="true" isvaluerequired="false" autosubmit="false"operator= "AND" > DIAMETER = [value] </value>       <!--value prompt="Example: 01/01/2007 Install Date" field="INSTALLDATE" isvaluerequired="false" operator= "AND" > INSTALLDATE >= '[value] 00:00:00'</value-->      </values>      </expression>     </expressions> and attached is a picture of my widget. see how it is auto filling in the data?  i would think they would need to start out blank??  I dont understand what i have done wrong here. ... View more

Marie,    So in Version 3.0 there is some issue you are going to have to work around. You need to use uniquevalsfromfield instead of domain as using domain in 3.0 will force you to have a value for each domain field. The next issue you will have to Just deal with in version 3.0 is that once you have chosen a value from the dropdown list the search will automatically be executed (this was fixed in latter releases). I am going to assume that your diameter field is numeric and not a string and I adjusted your expression for that assumption. Here is a corrected configuration for your layer:         <layer>             <definitionexpression></definitionexpression>             <enableexport>true</enableexport>             <name>Water Mains</name>             <url>http://gis-01/ArcGIS/rest/services/MAP_DOCS/dmww_water_server/MapServer/23</url>             <expressions>                 <expression alias="Material,Diameter and Install Date" textsearchlabel="Search Material:" isvaluerequired="false">                     <values>                         <value prompt="Material" uniquevalsfromfield="MATERIAL" isvaluerequired="false">MATERIAL = '[value]'</value>                         <value prompt="Diameter" uniquevalsfromfield="DIAMETER" isvaluerequired="false" operator="AND">DIAMETER = [value]</value>                         <value prompt="Example: 01/01/2007 Install Date" isvaluerequired="false" operator="AND">INSTALLDATE >= date '[value] 00:00:00'</value>                     </values>                 </expression>             </expressions>             <graphicalsearchlabel>Use one of the graphical search tools to select Water Mains</graphicalsearchlabel>             <spatialsearchlayer>true</spatialsearchlayer>             <titlefield>FACILITYID</titlefield>             <fields all="false">                 <field name="DIAMETER" gridfield="true" />                 <field name="FACILITYID" gridfield="true" />                 <field name="MATERIAL" gridfield="true" />                 <field name="INSTALLDATE" gridfield="true" dateformat="MM/DD/YYYY" useutc="true" />             </fields>             <links/>             <zoomscale usegeometry="true" zoompercent="1.6"></zoomscale>             <autoopendatagrid>false</autoopendatagrid>             <queryattachments>false</queryattachments>             <relates/>             <symbology>                 <simplelinesymbol color="0x00ff00" alpha="0.8" width="2" />             </symbology>         </layer> Also - the date value that you changed??  i am trying to do a greater than or equal to on the date and it seemed to be working the way i had it.  is it wrong??  Is it possible to do a "between" dates ?? ... View more

Marie,    So in Version 3.0 there is some issue you are going to have to work around. You need to use uniquevalsfromfield instead of domain as using domain in 3.0 will force you to have a value for each domain field. The next issue you will have to Just deal with in version 3.0 is that once you have chosen a value from the dropdown list the search will automatically be executed (this was fixed in latter releases). I am going to assume that your diameter field is numeric and not a string and I adjusted your expression for that assumption. Here is a corrected configuration for your layer:         <layer>             <definitionexpression></definitionexpression>             <enableexport>true</enableexport>             <name>Water Mains</name>             <url>http://gis-01/ArcGIS/rest/services/MAP_DOCS/dmww_water_server/MapServer/23</url>             <expressions>                 <expression alias="Material,Diameter and Install Date" textsearchlabel="Search Material:" isvaluerequired="false">                     <values>                         <value prompt="Material" uniquevalsfromfield="MATERIAL" isvaluerequired="false">MATERIAL = '[value]'</value>                         <value prompt="Diameter" uniquevalsfromfield="DIAMETER" isvaluerequired="false" operator="AND">DIAMETER = [value]</value>                         <value prompt="Example: 01/01/2007 Install Date" isvaluerequired="false" operator="AND">INSTALLDATE >= date '[value] 00:00:00'</value>                     </values>                 </expression>             </expressions>             <graphicalsearchlabel>Use one of the graphical search tools to select Water Mains</graphicalsearchlabel>             <spatialsearchlayer>true</spatialsearchlayer>             <titlefield>FACILITYID</titlefield>             <fields all="false">                 <field name="DIAMETER" gridfield="true" />                 <field name="FACILITYID" gridfield="true" />                 <field name="MATERIAL" gridfield="true" />                 <field name="INSTALLDATE" gridfield="true" dateformat="MM/DD/YYYY" useutc="true" />             </fields>             <links/>             <zoomscale usegeometry="true" zoompercent="1.6"></zoomscale>             <autoopendatagrid>false</autoopendatagrid>             <queryattachments>false</queryattachments>             <relates/>             <symbology>                 <simplelinesymbol color="0x00ff00" alpha="0.8" width="2" />             </symbology>         </layer> yes i saw that on the diameter u are correct.  i did try the uniquevalsfromfield="MATERIAL" and it takes a long time to load the values.  Thanks for your answeres i will look at upgrading to the newest version.  is that 3.3? ... View more