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 3.0.1f - results &amp; white exclamation problem

I have some problems using the identify widget. 1) Everytime I try to identify a feature, I will get this message "No Results Found" before the results show up. I try to modify the code on ArcGISDynamicMapServiceLayer but still get the same message.
2) Somestimes I will get a White screen with exclamation mark after the identify results show up.
Have any ideas how to solve this problems? Thanks for the time to look into it.

Encuentra más publicaciones etiquetadas con

Accepted answers

RobertScheitlin__GISP

All,

   A new version is now available.

* 3.0.2 - Fixed the Gray Circle Of Death (GCOD) people were seeing because of the glowfilter
              being applied to graphics not completely in the map extent.
           - Fixed the identifying features message to more accurately report the identify progress.

All comments

Richard,

OK, that makes me feel better... The API team is aware that there is still an issue with Polylines and it will be addressed in the next version of the API.

Robert,

FYI, just tried a fix from post #4 on this thread that removes the glowfilter. I'll run with this until the API is repaired.

Regards,

Rick

RobertScheitlin__GISP

Richard,

OK, that makes me feel better... The API team is aware that there is still an issue with Polylines and it will be addressed in the next version of the API.

Richard,

So you are saying that you can get the GCOD when using the identify widget on a polyline Using Version 3.1 of the Identify Widget?

Robert,

My bad. I posted this in the wrong thread. This is in the 3.1 Viewer and relating to the popups. Not your widget.

Rick

RobertScheitlin__GISP

Richard,

So you are saying that you can get the GCOD when using the identify widget on a polyline Using Version 3.1 of the Identify Widget?

Just tested the 3.1 API/Viewer and I am still getting the GCOD. Tested a polyline featueclass that is in SDE and FGDB with the same results.

Rick

RobertScheitlin__GISP

Shingo,

If that is the case than no there is no work around for that. You will have to wait for the 3.1 API that fixes that bug.

Exactly.
Shingo

RobertScheitlin__GISP

Shingo,

Are you saying that it happens with PopUps on Polylines but does not crash until you zoom into the highlighted polyline where there is a portion of the line outside the maps extent?

Robert,

Good to know. Before I attempted the identify widget, I am observing this GCOD issue with normal layer popup. It is resolved for upcoming API, but it is strange that not many users have recognized.

Shingo

RobertScheitlin__GISP

Shingo,

It is really going to help you in the future to use the proper terminology. What you are calling non-identify widget identifying is simply using a layers PopUp. As far as the standard PopUp ever crashing Flash Player with a GCOD... I have never seen this happen. I have only seen this with my old Identify Widget.

renditionDownload.png

Makes sense. As for the GCOD error, do you know if there is workaround for non-identify widget users? It seems identifying and zooming to any dissolved segment can be at risk of crashing flex application.

RobertScheitlin__GISP

Shingo,

Though the code change you made does work... It would break if you wanted to use an alias name other than the one provided by the REST Service.

I see. The alias need to be set to name parameter and it is taking from the initial index [0] in xml. I was using the field name to name param and alias to the alias param... Thanks!

RobertScheitlin__GISP

Shingo,

That change is not appropriate if you follow all the instructions in the PDF that come with the widget. You have to use the field alias names (FROM THE REST SERVICE DIRECTORY) in the IdentifyWidget.xml field name attribute.

The name attribute is the EXACT ALIAS (as it is displayed in the REST services directory) of the field and is a
REQUIRED attribute. The alias attribute is optional as this information can automatically be retrieved
from the map service. If you want to specify an alias that is different than the alias specified in ArcMap
than you can set this value.

Also, FYI. If you are using alias in config as:
<field name="APP_STATUS" alias="Application Status"/>

line 989 of IdentifyWidget.mxml needs to be:

value = obj[cArr[1]] ? String(obj[cArr[1]]) : "";

in stead of:

value = obj[cArr[0]] ? String(obj[cArr[0]]) : "";

This fixed all my value = "" issue. 🙂

Without using identity widget, Fiber viewer uses popupconfig to perform query and display REST result using Identify Task. When popupconfig is set on my dynamic sub layers, the application opens the attribute info using the grow filter to highlight the feature. I am experiencing the GCOD when we identify for a multi-part feature that goes out of map extent, as you mentioned.

I was able to turn off the default identify by removing popupconfig from the config.xml.

RobertScheitlin__GISP

Shingo,

I have no idea what you are referencing here:

When I used your latest identify widget, I noticed that the default identify is still active. Do you know the way to disable the default identify from the index.mxml until the bug fix is released?

What are you calling "default identify"?

Hi Robert,

Thanks for great widget as always. It seems that GCOD is happening to my app as well. ESRI has resolved the issue in NIM084978 for the next release of API. When I used your latest identify widget, I noticed that the default identify is still active. Do you know the way to disable the default identify from the index.mxml until the bug fix is released?

Thanks,
Shingo

2.クエリレイヤー.png

10.ポータルースタンドアロン.png

5.ポータル-レイヤー.png

RobertScheitlin__GISP

Rhett,

Just good old practical observation. I noticed that when you were zoomed out where all the graphics where contained in the map extent, there was no issue. Then if you clicked one of the small graphics result (with zoomed the map extent in) and hovered over a graphic that was not completely contained in the map extent, you got an instant GCOD. But you did not get it when you hovered over a graphic that was completely contained.

Now you really got me curious.

How did you manage to figure out that it was because the glowfilter on out of extent feature?

was there some trace error or something that pointed you in that direction, or just trial/error?

R_

RobertScheitlin__GISP

All,

   A new version is now available.

* 3.0.2 - Fixed the Gray Circle Of Death (GCOD) people were seeing because of the glowfilter
              being applied to graphics not completely in the map extent.
           - Fixed the identifying features message to more accurately report the identify progress.

Robert,

I can consitantly make you live site give the exclamation point of death, but not a consistant method (or rather, not a consistant number of clicks).

However, if I Turn on the zoning layer, select it from identify and select by rectangle, it will return a selection.

If I start clicking like mad on the results and not quite letting it "finish" drawing after it pans, THEN try to move the mouse up to the top of the widget (like you were going to switch to input mode rather than results) OR hover the mouse over the map somewhere (other than over the identify widget), bam, I get the exclamation point.

Seems to be related to a mouse_over event or something as I can only make it happen when I have the mouse going all over the place while "panning/zooming to" a feature.

R_

Looks like I can do it with the land use layer also, but not as "quickly".
at first, thought it had something to do with the bug on dynamic layers losing (or getting null geometry) once you click off the feature, but, I can make it happen on the land use layer "eventually" also.

RobertScheitlin__GISP

May Jeff,

Can you get it to happen all the time? Is there a certain sequence? What area of Louisville are you selecting? I have been playing around with my live site every way I can think of and have yet to receive the error. Are you from a foreign county? Maybe it has something to do with internet connection lag. I just have no idea when I can not get the same results on the same site.

Robert,
Thanks for taking to look into it. I just tested it on Firefox and got the same error message. My lastest version is 11.5.502.110 & have 8GB RAM, windows 7 & 64bit.

closed_infowindow.gif

RobertScheitlin__GISP

May Jeff,

Do you have a old machine with limited memroy or something? I have tried many things to reproduce your error and can not. Using my live site I turned on the "Louisville Landbase Landuse" layer and used the rectangle tool to select a large area of both landbase and Public Safety features and clicked around in the results (a lot) and never got the issue. So then I noticed that you are using Internet Explorere (which I never use) so I tried it and repeated the steps, never getting an error. The I used another workstation and duplicated my test using the same steps, no issue. My flash player versions on these machines are 11.5.502.110

Robert,
I used your life map to test it and got white exclamation mark too. See the error message.
I turned on the land use layer, then selected All Layers and used identify by rectangular to select a area to identify. After the results came up (include polygons & points), just clicked different results couple times then white exclamation mark showed up.
Pretty weird. Hope can figure this out.
Thank you.

ArcMapPublishingError.png

RobertScheitlin__GISP

May Jeff,

I have tried what you said using esri map services and could not get the error.

Thanks for the quick reply. Map services is not public. One thing I find out, if you choose to identify "All Layers" then scroll your mouse to zoom in cloaser to your map then click the results or just click the results will get "White exclamation" mark. So far, if you choose just one layer to identify then didn't get that white exclamationmark yet.
Thank you very much.

RobertScheitlin__GISP

May Jeff,

You will always get this message "No Results Found" if one of your map services in your application does not support the identify operation. This will be addressed in the next version of the widget. As far as the White exclamation mark there seems to be a couple of people getting this error but I have not been able to reproduce it. If I can not reproduce it I can not fix it. Is your application and or map services public? can you pin point one layer or feature that exhibits this error?

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

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