Select to view content in your preferred language

Identify Widget Snafu

1723
15
10-31-2013 03:33 PM
by Anonymous User
Not applicable
[ATTACH=CONFIG]28763[/ATTACH]

This post is obstensively for Robert Scheitlin but anyone else who has faced a similar issue while using his Identify Widget and maybe has an idea as to how to address it is welcome to reply as well.

I've attach an image that shows what I'm facing when using the Identify Widget (I'm using Version 3.3.2 of the tool as I am still running version 3.3 of the Flex Viewer).  I have many items being identified with the Widget and can attach the config.xml if that will help but the long and short of it is that I have several features that defy identification - namely the Streams features. It appears that the widget is identifying and returning geometry ok but not the underlying attributes.  I've crossed checked the XML file against the fields thoroughly and am using configurations settings virtually identical to other features that are being returned correctly.

One interesting side note of this is that when I roll over a selected Stream it highlights correctly on the map but when I go to delete it from the list it appears not to be able to differentiate and deletes random other listings in the identify list instead.

Anyway, one possible clue is that the same thing is happening for Hydrologic Features which is in a shared Feature Dataset with Streams. I've since tried dropping and recreating the offending dataset, have created dummy feature classes and always the results are the same - very odd. I will continue doing some testing and let you know if I find anything else but in the meantime I thought I'd see if anyone has experienced anything like this while using Robert's widget.

One final note, I've used both a stand-alone feature service containing Streams and also a map service containing Streams as a sublayer and the result is still the same ... 

Any and all help solving this puzzle is greatly appreciated!
Tags (2)
0 Kudos
15 Replies
RobertScheitlin__GISP
MVP Emeritus
Bob,

   Please provide your IdentifyWidget.xml, main config.xml, and a copy and paste of all the text of the layers rest service directory (the layer of the mapservice that is experiencing this issue) in a text file. Zip all these up and please attach for analysis.
0 Kudos
by Anonymous User
Not applicable
Robert -

I've attached the requested documentation for your review ...  Thanks again for your help with this!

- Bob

ps XML were provided in Word documents with key areas highlighted
0 Kudos
RobertScheitlin__GISP
MVP Emeritus
Bob,

    Sounds like you may be encountering a very common issue in the Identify widget. The issue is that Flex is a CaSe sensitive language. You have:

http://sac-gisweb-01/arcgis/rest/services/MRCBaseMap/MapServer
http://sac-gisweb-01/ArcGIS/rest/services/MRCBaseMap/MapServer
the url one way in the main config.xml and another CaSe in the IdentifyWidget.xml. You need to have both the main config.xml urls and the IdentifyWidget urls Identical in CaSe.
0 Kudos
by Anonymous User
Not applicable
Bob,

    Sounds like you may be encountering a very common issue in the Identify widget. The issue is that Flex is a CaSe sensitive language. You have:

http://sac-gisweb-01/arcgis/rest/services/MRCBaseMap/MapServer
http://sac-gisweb-01/ArcGIS/rest/services/MRCBaseMap/MapServer
the url one way in the main config.xml and another CaSe in the IdentifyWidget.xml. You need to have both the main config.xml urls and the IdentifyWidget urls Identical in CaSe.


I must admit you have a great eye Robert! However in this case that wasn't the culprit ... Would it help to see the raw data behind the service or the other related feature services rest points?  I neglected to mention this previously but the Streams layer along with the Hydrologic Features behave as expected in the edit widget, though those are with the Feature Services and not the base map layer ...
0 Kudos
RobertScheitlin__GISP
MVP Emeritus
Bob,

   Have you tried to create a new clean viewer and IdentifyWidget with just those layers?
0 Kudos
by Anonymous User
Not applicable
I may have but not a bad idea ... Lemme try that and let you know what I find ...
0 Kudos
by Anonymous User
Not applicable
OK, my understanding of doing a "clean" run was just to strip out everything from the IndentifyWidget.xml file except for Streams and Hydrologic Features.  I've not made any customizations to the widget itself so beyond that is there something else I would do?  No change in results thus far ...
0 Kudos
RobertScheitlin__GISP
MVP Emeritus
Bob,

  It would entail removing all layers from the main config.xml except the MRCBasemap layer you are tring to identify.
0 Kudos
by Anonymous User
Not applicable
OK, will try that. I'm trying something slightly different at the moment focusing on the data itself but I'll give that a try if nothing comes of my testing.
0 Kudos