Select to view content in your preferred language

Identify Widget Not Working

3216
10
Jump to solution
09-30-2013 08:56 AM
GeorgeHaskett
Deactivated User
Hello,

I am using the Idendify Widget version 3.4.2 for the Viewer for Flex application and have used older version of this widget at a different job with out any issues.  However, at my new job I cannot seem to get the widget to work properly.  I have tried various options and still cannot get it to work.  After trying making variouis adjustments I am officially at a loss.

My symptoms include the following:

Widget fails to identify features - acts as if it completely stopped working as there are no error or result messages/warnings.

At one point I was able to get the widget to work when using the preview option of the Application Builder in a test map, however once I copied the files over to my pre-existing map they no longer worked.  However, the widget worked with the extent tool and not the mappoint tool, I actually received a "No Results Found" message when attempting the mappoint tool.  At one point I commented out all my references to popups hoping that this would work, but it didnot.

I have even attempted added both a mapserver and featureserver and am still at a loss.

I have redownloaded the latest version (3.4.2) and copied the compiled version over and rebuilt from scratch using XML Notepad program.

Any help would be greatly appreciated.

I have attached my xml docs.

Thanks,

Haskett
Tags (2)
0 Kudos
1 Solution

Accepted Solutions
GeorgeHaskett
Deactivated User
Okay,

I figured out the second portion of my issues. 

I was using my Featureservice and not my Mapservice.

Is it possible to find even bolder text then you are using in your write up to help individuals like me....

I guess it was not all a loss, we did identify the reference basemap clitch.

Thanks for all your hard work on this widget Rob.

View solution in original post

0 Kudos
10 Replies
RobertScheitlin__GISP
MVP Emeritus
George,

  using version 3.4.2 in Application Builder, you should not have any need to touch the xml in any editor program. I would say start tesing by adding a new app in App Builder and add layer that you are attempting to identify USING THE GUI in app builder and see what happens (Always be aware that if the URL that you use to add the operational layer is http://www.yourcompany.com/arcgis/rest/services/my_mapservice/ then your url you enter in the identify widget configuration GUI need to be identical CaSe and all).
0 Kudos
GeorgeHaskett
Deactivated User
Thanks Rob,

I have gone through and rebuilt the web app a few times.

I am now able to get the extent tool to work, but still not the mappoint tool.  Using it still returns the "No Results Found" message.

However I found what I believe was my biggest issue, when I add the reference basemap layer the tool stops working.  It still selects/highlights the features in question, but does nothing else.  When I remove the basemap layer, the extent works as advertised, but not the mappoint tool.

The basemap layer in question is:

http://services.arcgisonline.com/ArcGIS/rest/services/Reference/World_Boundaries_and_Places/MapServe...

Can you test this service on your end?

I am pulling it in via the app builder and the default settings are:
type - tilled
label - Aerial
visible - false
reference - true

Thanks,

Haskett
0 Kudos
RobertScheitlin__GISP
MVP Emeritus
George,

   Why would you be adding that reference layer as a layer to identify?...
0 Kudos
GeorgeHaskett
Deactivated User
Rob,

Sorry for the confusion, but when referencing the basemap layer in question (Imagery with Lables), I am referring to the main config.xml file not the identifywidget.xml file.  Looking things over, I must have changed the label name on my config file to "Aerial", either way the basemap layer in question is the "Imagery with Labels".

I have come to find out that if I add the Portal for ArcGIS Basemaps, then the identify widget works using the extent tool, but not the mappoint tool.  However if I remove the Portal for ArcGIS Basemaps and add only the Imagery with Labels basemap, then the identify tool stops working all together.

Either way I don't seem to be able to get the mappoint option working, just the extent option.  Granted I am not trying any of the others identify tools.  Is there a way to remove the mappoint from the GUI or is it there by default and not removable?

Again, I am not adding the basmap in question to my identify widget, only to my main config file.  But for whatever reason that is affecting the identify widget.

I recreated the error in a basic test map and have attached the config.xml and identifywidget.xml files.

Thanks for any insight you might be able to give.

Is there a chance that this is a bug in the code seeing how I can recreate this in multiple maps? 
Can you test either the standard compile files or the application builder files and build a map using only the Imagery with Labels basemap and still have the identify widget work properly on your end?

Thanks again for all your hard work,

Haskett
0 Kudos
RobertScheitlin__GISP
MVP Emeritus
George,

   I will have to find time to test your scenario. There is always a chance that this is a bug, but I have to say that I am using the ArcGIS Basemaps from Portal in the live preview site and all the identify tools work fine.

   If you read the documentation you will see that you can disable any of the tools.
0 Kudos
GeorgeHaskett
Deactivated User
Rob,

Yes, that is the strange part.  If I use the ArcGIS basemaps via the Portal option, then everything works as advertised.

It is when I turn off the portal option and instead pull in the Imagery with Labels basemap that the identify widget stops working for me.  Its as if the extra layer of annotation is somehow getting in the way.  I do not recall having this issue with the older versions.

Today when I get to work I can check if the other basemaps with labels interfere when they are pulled in separately from the portal.
Later this week when I am back at the university I can check some of my older maps and see if there is a difference.  Off the top of my head I cannot remember if I pulled in a basemap with labels or not.

Thanks,

Haskett
0 Kudos
RobertScheitlin__GISP
MVP Emeritus
George,

   Strangest thing... The attribute reference on the labels layer in the basemaps is the culprit.

    <basemaps>
      <layer type="tiled" label="Imagery with Labels" icon="https://www.arcgis.com/sharing/rest/content/items/413fd05bbd7342f5991d5ec96f4f8b18/info/thumbnail/tempimagery_with_labels_ne_usa.png" url="http://services.arcgisonline.com/ArcGIS/rest/services/World_Imagery/MapServer" visible="true" />
      <layer type="tiled" label="Imagery with Labels" url="http://services.arcgisonline.com/ArcGIS/rest/services/Reference/World_Boundaries_and_Places/MapServer" visible="false" reference="true" />
    </basemaps>


Manually remove that from the config.xml and the identify works fine. I have to continue to research why this is the case though. Also I am not sure why you even have that url added as a layer in your basemaps when you have its visibility set to false?...
0 Kudos
GeorgeHaskett
Deactivated User
Rob,

Thanks, I figured it had to be some kind of code conflict because I could replicate it on different maps. 

Maybe, for some reason, its treating the reference portion of the service as if its blocking access information from layers that lay below it.

I have the visible value set at false so that the Topo basemap is automatically on when the map opens and then the end-user uses the emapswitcher to slide between the other two basemap layers in my map.  I didn't think you could turn more than one on at a time.  Can you set multiple basemaps visible value to true at the same time?  I'll have to check.

Unfortunately I am still having issues with the mappoint tool not working.  It is still returning No Results Found.  Could this have something to do with a popup conflict?  Any guesses why?  Is it working via either the application builder or the compiled versions on your side?

Thanks,

Haskett
0 Kudos
GeorgeHaskett
Deactivated User
Okay,

I figured out the second portion of my issues. 

I was using my Featureservice and not my Mapservice.

Is it possible to find even bolder text then you are using in your write up to help individuals like me....

I guess it was not all a loss, we did identify the reference basemap clitch.

Thanks for all your hard work on this widget Rob.
0 Kudos