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

LefterisKoumis

I trying to use the custom identify tool with my layers and the tool just ignores their entries in the xml file. I am using the identifywidget.xml file that Robert provided with his tool and I included my layer as a test. When I zoom to the area of my layer the identify tool cannot find anything! When I zoom in the area of the layers that were originaly in the xml file the identify tool works!
Any suggestions?

Attached is the xml file. My layer is the second listed. I already checked the field names for mispellings or similar errors but nada.

Thanks.

xml version.docx

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

Accepted answers

All comments

RobertScheitlin__GISP

Lefteris,

Someone else had a question that caused me to think of something you should check in your configuration.

Check your url CaSe as Flex is CaSe sensitive language. If the URL you have in the IdentifyWidget.xml can not be matched to a URL in your map (coming from your main config.xml) then you will not get any results.

RobertScheitlin__GISP

Lefteris,

Except for the fact that I took the exact xml that you posted and got it to work un-edited as I posted in that previous thread and even supplied a screenshot proving that it worked... I am not sure what to tell you.

LefterisKoumis

Guys,

I will be releasing a 3.4 version (hopefully in a week or two) of the widget that has full application builder integration (this means I can eliminate user xml configuration errors). All I can say is you have an issue in your configuration of the widget as I don't have any issue getting it to work.

Thank you Robert, but I don't think it is a xml issue. I already posted the xml for the widget and for the main config (under a similar forum post) and there was nothing wrong with them. I will look into other possible reasons.

RobertScheitlin__GISP

Guys,

I will be releasing a 3.4 version (hopefully in a week or two) of the widget that has full application builder integration (this means I can eliminate user xml configuration errors). All I can say is you have an issue in your configuration of the widget as I don't have any issue getting it to work.

LefterisKoumis

Mike,

I just started a brand new compiled site on my IIS and copied over the 3.3.2 compiled Identify Widget over to it and and it worked fine....

I have the same problem only when I use onlythese="true"

RobertScheitlin__GISP

Mike,

I just started a brand new compiled site on my IIS and copied over the 3.3.2 compiled Identify Widget over to it and and it worked fine....

MichaelEdelson

Hi Robert,
I'm using the compiled version. I was using 3.3.1. I hope this is helps, I'm still having the same issue. Thanks, Mike

RobertScheitlin__GISP

Michael,

No one elese has reported an issue like this... When you say you upgraded to 3.3.2, can you eloborate? Are you using app builder, the compiled version, or the uncompiled? What version were you running before 3.3.2?

MichaelEdelson

Robert, this is a great tool, thanks for building, upgrading and maintaining it. I'm using Flex Viewer 3.3 and just recently upgraded the Identify Widget to 3.3.2. Ever since this update the Identify tool is not returning any values. I think the problem is occurring because the Identify Pop-up dialog box is not recognizing my clicks to highlight the Point, Line, or Polygon selection tools. Has anyone else come across this? I've searched the forum but could not come up with a fix. Thanks!

LefterisKoumis

Lefteris,

Using the exact XML you provided I had no Issue. Do you have the layer visible in the map?

[ATTACH=CONFIG]23055[/ATTACH]

That's bizarre.

The layer is visible.

in the main config file the layer is identified as"

<layer label="Agencies" type="dynamic" visible="true"
url="http://svctenvims.dot.ca.gov/dea_web_gis/rest/services/agencies/agencies/MapServer/">

and the MPO is layer id=0

see screenshot.

Thank you.[ATTACH=CONFIG]23061[/ATTACH]

identify.JPG

RobertScheitlin__GISP

Lefteris,

Using the exact XML you provided I had no Issue. Do you have the layer visible in the map?

[ATTACH=CONFIG]23055[/ATTACH]

Preview.jpg

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.