Identify Widget 3.4: No Results Found Message

[DanielJohns]

The 'No Results Found' message keeps popping up when after identifying features. Results are returned (see attached image), but the message keeps popping up. If I remove a record it will update the results and display the number of records found.

[ATTACH=CONFIG]26931[/ATTACH]

Due to the thread text length limit, I could only included certian sewer layers.

<?xml version="1.0" ?> <!-- encoding="UTF-8" --> <configuration>     <identifylayeroption>visible</identifylayeroption>     <identifytolerance>10</identifytolerance>     <defaultzoomscale>5000</defaultzoomscale>     <keepidentifyactive>true</keepidentifyactive>     <returngeometryforzoom>true</returngeometryforzoom>     <enablelineselect>true</enablelineselect>     <enableextentselect>true</enableextentselect>     <enablepolyselect>true</enablepolyselect>     <enablecircleselect>true</enablecircleselect>     <enableellipseselect>true</enableellipseselect>     <enablemouseovergraphicsinfo>false</enablemouseovergraphicsinfo>     <enablemouseoverrecordinfo>true</enablemouseoverrecordinfo>     <enablegraphicclickinfo>true</enablegraphicclickinfo>     <usemaptime>false</usemaptime>     <infoautoclosemilliseconds>2000</infoautoclosemilliseconds><!-- 2 seconds -->     <autoactivatedtool>mappoint</autoactivatedtool><!-- possible values are extent or polygon or mappoint or polyline or nothing -->     <excludebasemaps>true</excludebasemaps>     <disablepopuplinks>false</disablepopuplinks>     <disablelayerdropdown>false</disablelayerdropdown>     <disablealllayerschoice>false</disablealllayerschoice>     <replacenullswithemptystring>true</replacenullswithemptystring>     <labels>         <zoom2message>Click to Zoom to Point</zoom2message>         <identifylabel>Identify</identifylabel>         <resultslabel>Results</resultslabel>         <descriptionlabel>Use the identify tool to identify features on the map:</descriptionlabel>         <pointlabel>Identify by Point</pointlabel>         <linelabel>Identify by Polyline</linelabel>         <rectlabel>Identify by Rectangle</rectlabel>         <polylabel>Identify by Polygon</polylabel>         <circlelabel>Identify by Circle</circlelabel>         <ellipselabel>Identify by Ellipse</ellipselabel>         <clearlabel>Clear</clearlabel>         <loadinglabel>Loading...</loadinglabel>         <removeresultmessage>Remove Result</removeresultmessage>         <idfrom>Identify From</idfrom>         <noresultsfoundlabel>No Results Found</noresultsfoundlabel>         <resultsfoundlabel>Results Found</resultsfoundlabel>         <alllayers>All Layers</alllayers>         <layersremaining>layers remaining:</layersremaining>     </labels>     <useproxy><!-- Enter the label of the MapService from the main config.xml -->         <!--<proxymapservice label="Imagery" />          <proxymapservice label="Streets" /> -->     </useproxy>               <!-- Sewer Layers -->  <layers onlythese="true"> <!--   <excludelayer name="AerialHybrid_2009" /> --> <!--   <excludelayer name="AerialHybrid_2011" /> --> <!--   <excludelayer name="AerialLayer_2009" /> --> <!--   <excludelayer name="AerialLayer_2011" /> --> <!--   <excludelayer name="BaseLayers" /> --> <!--   <excludelayer name="Routes" /> --> <!--   <excludelayer name="Notifications" /> --> <!--   <excludelayer name="CostSharingLayers" /> -->      <layer>    <name>Sewer Manhole</name>    <id>11</id>    <url>http://server/svr/rest/services/UtilityLayers/MapServer</url>    <fields all="false">     <field name="Rim elevation" />     <field name="As-built #" />     <field name="As-built link" popuponly="true" />     <field name="Manhole # (as-built)" />     <field name="Status" />     <field name="Owned and maintained by" />     <field name="Comments" />    </fields>    <layer>    <name>Sewer Tee, Tap or Cross</name>    <id>18</id>    <url>http://server/svr/rest/services/UtilityLayers/MapServer</url>    <fields all="false">     <field name="Type of fitting" />     <field name="Size" />     <field name="Material" />     <field name="As-built #" />     <field name="As-built link" popuponly="true" />     <field name="Status" />     <field name="Owned and maintained by" />     <field name="Comments" />    </fields>    <links>     <link includeinresults="false" field="As-built link" alias="Copy As-built"      tooltip="Copy As-built">      <linkprefix></linkprefix>      <linksuffix></linksuffix>      <iconfield></iconfield>      <iconprefix></iconprefix>      <iconsuffix>assets/images/dwgIcon.png</iconsuffix>     </link>    </links>    <zoomscale>15000</zoomscale>    <forcescale>true</forcescale>   </layer>   <layer>    <name>Sewer Locate Wire</name>    <id>20</id>    <url>http://server/svr/rest/services/UtilityLayers/MapServer</url>    <fields all="false">     <field name="Type of locate device" />     <field name="As-built #" />     <field name="As-built link" popuponly="true" />     <field name="Owned and maintained by" />     <field name="Comments" />    </fields>    <links>     <link includeinresults="false" field="As-built link" alias="Copy As-built"      tooltip="Copy As-built">      <linkprefix></linkprefix>      <linksuffix></linksuffix>      <iconfield></iconfield>      <iconprefix></iconprefix>      <iconsuffix>assets/images/dwgIcon.png</iconsuffix>     </link>    </links>    <zoomscale>15000</zoomscale>    <forcescale>true</forcescale>   </layer>         <layer>    <name>Gravity Main</name>    <id>29</id>    <url>http://server/svr/rest/services/UtilityLayers/MapServer</url>    <fields all="false">     <field name="Size" />     <field name="Material" />     <field name="Rating of pipe" />     <field name="Upstream Invert" />     <field name="Downstream Invert" />     <field name="As-built #" />     <field name="As-built link" popuponly="true" />     <field name="Status" />     <field name="Owned and maintained by" />     <field name="Comments" />    </fields>    <links>     <link includeinresults="false" field="As-built link" alias="Copy As-built"      tooltip="Copy As-built">      <linkprefix></linkprefix>      <linksuffix></linksuffix>      <iconfield></iconfield>      <iconprefix></iconprefix>      <iconsuffix>assets/images/dwgIcon.png</iconsuffix>     </link>    </links>    <zoomscale>15000</zoomscale>    <forcescale>true</forcescale>   </layer>   <layer>    <name>Force Main</name>    <id>32</id>    <url>http://server/svr/rest/services/UtilityLayers/MapServer</url>    <fields all="false">     <field name="Size" />     <field name="Material" />     <field name="Rating of pipe" />     <field name="As-built #" />     <field name="As-built link" popuponly="true" />     <field name="Status" />     <field name="Owned and maintained by" />     <field name="Comments" />    </fields>    <links>     <link includeinresults="false" field="As-built link" alias="Copy As-built"      tooltip="Copy As-built">      <linkprefix></linkprefix>      <linksuffix></linksuffix>      <iconfield></iconfield>      <iconprefix></iconprefix>      <iconsuffix>assets/images/dwgIcon.png</iconsuffix>     </link>    </links>    <zoomscale>15000</zoomscale>    <forcescale>true</forcescale>   </layer>   <!-- End of Sewer Layers -->     </layers>          <symbols>         <simplefillsymbol color="0x448ccb" alpha="0.4"             style="solid">             <outline color="0x448ccb" alpha="0.8" width="2" />         </simplefillsymbol>         <simplemarkersymbol style="circle" size="12"             color="0x448ccb" alpha="0.8" xoffset="0" yoffset="0" angle="0">             <outline style="solid" color="0xffffff" alpha="0.8"                 width="1" />         </simplemarkersymbol>         <picturemarkersymbol url="assets/images/i_info.png"             height="30" width="30" xoffset="0" yoffset="0" />         <simplelinesymbol color="0x448ccb" alpha="0.8"             width="2" />     </symbols> </configuration>

[DanielJohns]

Daniel,

   I am not sure I can fix your issue with the widget without access to your specific data. Not being able to see the http traffic that the service is returning and whether the map service request is failing or the widget is failing to process properly, has me in the dark. I took a stab at a potential issue tracking the logic in my code with the 3.4.1 release, but as you said you are getting the same result...

Robert,

Thank you.

We recent upgraded to 10.1, SQL 2012 and rebuilt our sde (moved to dbo.schema) database and webservices, so there's a good chance it could be a configuration issue causing the problem. I was able to get my debugger updated and working again, so I will trace the code to see where it's pulling that message.

[DanielJohns · Accepted solution]

Okay I got it working. I did some debugging and was able to determine that items were only being added to the 'identifyArrayCollection' in the 'projectResults function'. The 'noResultsFoundLbl' was being enable from within the 'onResult function', since the 'identifyArrayCollection' was shown as length = 0. I added your segment of code below, to the end of the 'projectResults function' and it updates the results label as desired.

On a side note, your eSearch widget calculates the number of returned results as expected (with not modifications).

if(identifyArrayCollection.length == 0 && numServicesIdent <= 0){  showMessage(noResultsFoundLbl, false);   timedClose2(); }else if(identifyArrayCollection.length > 0 && numServicesIdent <= 0){  showMessage(resultsFoundLbl + " " + identifyArrayCollection.length, false);  timedClose2(); }else{     disableTimer2(null);     showMessage(loadingLabel + " " + layersRemaning + " " + numServicesIdent, true); }

[RobertScheitlin__GISP]

Daniel,

   Ahh... That is why I did not see it in my testing. You are running into that issue because one of the map services is running on an older ArcGIS Server that has a bug that I have a workaround for. Thanks for the info.

As far as comparing the eSearch and the Identify widget, that is like apples and oranges... The eSearch uses athe Query base task and only has to worry about on map service and the Identify uses the Identify base task and has to go to the server for each map service in the map.

[DanielJohns]

Daniel,

   Ahh... That is why I did not see it in my testing. You are running into that issue because one of the map services is running on an older ArcGIS Server that has a bug that I have a workaround for. Thanks for the info.

As far as comparing the eSearch and the Identify widget, that is like apples and oranges... The eSearch uses athe Query base task and only has to worry about on map service and the Identify uses the Identify base task and has to go to the server for each map service in the map.

Question, if I recreated all my services after upgrading to 10.1 how could it detect an old ArcGIS Server, could it possibly be something embedded in the mxd I used to publish the service?

We killed our old server and remapped all data sources to the new server (went from running SDE services e.g., 5151 to using SQL direct connect).

[MichaelVolz]

Daniel:

Did you recreate the mxds that are the source of your services from scratch?  I ask because I have found that services still find references to old servers even if no layers are pointing to that data source anymore (I was getting locking issues with file geodatabases that were not being used).  I'm not sure if this is why it is referencing a retired server, but I would think it is a possibility.

[DanielJohns]

Daniel:

Did you recreate the mxds that are the source of your services from scratch?  I ask because I have found that services still find references to old servers even if no layers are pointing to that data source anymore (I was getting locking issues with file geodatabases that were not being used).  I'm not sure if this is why it is referencing a retired server, but I would think it is a possibility.

I'll recreate them again and see if that fixes it. So the best approach would be to add them from the new location and then change the symbol, do not drag and drop from another MXD? I initially used the 'Fix data source' method to update the paths so I wouldn't have to go back and set all my symbols again.

[MichaelVolz]

Unfortunately, that is what I found to be the case in my enterprise environment.  I first just resourced the exising mxds from 1 source to another so the old source was not even being used, but locks were still being placed on the old source so I knew there were still references to the old source.

I tried using MxdDoctor and SaveAs to get rid of the old source, but these workflows were never 100% effective.  Recreating the mxd was the only 100% way of getting rid of references to the old data source.

[DanielJohns]

Unfortunately, that is what I found to be the case in my enterprise environment.  I first just resourced the exising mxds from 1 source to another so the old source was not even being used, but locks were still being placed on the old source so I knew there were still references to the old source.

I tried using MxdDoctor and SaveAs to get rid of the old source, but these workflows were never 100% effective.  Recreating the mxd was the only 100% way of getting rid of references to the old data source.

Completely rebuilding the layers from scratch did not work.  I�??m going to keep the modification in place since it's working. Also, rebuilding the layers increased map performance and the decreased the amount of time it takes to open.

I appreciate the help, thanks again.