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; } } }

Identify Widget Snafu

Anonymous User

[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!

identify.jpg

gridPrint.png

MariaPanagiotidou_0-1605168089520.png

Najděte více příspěvků označených jako

Accepted answers

All comments

Anonymous User

Robert -

Finally got back to this! Ran a test this morning installing the new Flex Viewer 3.5 via Application Builder (been needing to give that a test drive anyway) and configured your new widget for the "problem" data, and it worked! I suppose we may never know why it didn't want to work in the 3.3 environment but I'm ready to proceed with the full 3.5 implementation now so let's go ahead and consider this case closed ... Thanks again for all your help and suggestions.

- Bob

Anonymous User

Robert -

I'm not ready to do a full-scale Flex Viewer 3.5 implementation just yet but might do a scaled down app with nothing more than the errant data to see the results. Unfortunately we're trying to get our 3.3 application live here in the next couple of days so I'm going to have shelve this until that's completed and then get back to you with my test results sometime next week or so ... Thanks again for the help - I'll be back in touch after I've had a chance to revisit it. For now we're just going to leave the streams and Hydrologic Features out of the Identify tool since it's not a show-stopper, but am still anxious to get them operational in the near future.

- Bob

RobertScheitlin__GISP

Bob,

Did you dumb down the data in any way? Have you tried to setup a 3.5 viewer and use the 3.5.x version of the widget to see if that makes a difference? What version of ArcGIS Server are you using?

Anonymous User

You don't suppose that some of the difficulties I'm seeing are related to the version I'm using do you? I'm going to go ahead and use the .gdb file I sent you and see if that behaves differently than the SDE database version to rule out any problems with the database itself ... Any other suggestions?

RobertScheitlin__GISP

Bob,

So the data you sent works fine for me. Here is a image showing the results.

[ATTACH=CONFIG]28839[/ATTACH]

35872Preview.jpg

Preview.jpg

Captura de pantalla 2022-09-16 075411.translated.jpg

Captura de pantalla 2022-09-16 080624.translated.jpg

Anonymous User

Robert -

Went ahead and stripped out everything except the Base Map service and the results were the same. I also went ahead and created a brand new data set and copied some features over. All results are the same! Even removed domains on the data set to see if that had any effect but no luck. Gotta get running but will be back to pick up the thread on Monday. Meanwhile I've exported the dataset to personal geodatabase to test out and am enclosing it here so that you can have a peek at the data and let me know if you see anything particularly sinister ... Once again thanks for all the help and have a great weekend!

- Bob

streams.gdb.zip

Field Convo REST Name.PNG

Anonymous User

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.

RobertScheitlin__GISP

Bob,

It would entail removing all layers from the main config.xml except the MRCBasemap layer you are tring to identify.

GuenterDoerffel_4-1627989680536.png

GuenterDoerffel_6-1627989680541.png

Anonymous User

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 ...

Anonymous User

I may have but not a bad idea ... Lemme try that and let you know what I find ...

RobertScheitlin__GISP

Bob,

Have you tried to create a new clean viewer and IdentifyWidget with just those layers?

Anonymous User

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 ...

RobertScheitlin__GISP

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.

Anonymous User

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

IdentifyWidgetSnafu.zip

mgrs_coords_labelling.jpg

RobertScheitlin__GISP

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.

Připojte se k diskusi

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

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