topic Re: Identify 2.1.6 in ArcGIS Viewer for Flex Questions

Identify 2.1.6

JoshuaCoates — Tue, 26 Oct 2010 16:50:23 GMT

I have added this identify widget to my map. I have added the widget to the widget container, compiled it and added my changes to the identifywidget.xml. My problem is when I use the widget and click something....it displays the result box with the layer it is pulling from and it also shows the field, however, there are no values?! Also, when the application first opens, the identify widget automatically open by default. Where do I change this to where it will not auto-launch the widget?!

Thanks,
Josh C.

Re: Identify 2.1.6

JoshuaCoates — Sat, 11 Dec 2021 13:24:51 GMT

Here is my xml for reference. Also, for the <fields>DO I USE THE NAME OF THE FIELD OR THE ALIAS?</fields>

<layer>
   <name>Address</name>
   <fields>FIRSTNAME,LASTNAME,ADDRESS,STREETNO,STREET,CITY,STATE,ZIP</fields>
   <linkfield></linkfield>
   <linkprefix></linkprefix>
   <linksuffix></linksuffix>
   <iconfield></iconfield>
   <iconprefix></iconprefix>
   <iconsuffix></iconsuffix>
   <zoomscale>15000</zoomscale>
   <forcescale>true</forcescale>

Re: Identify 2.1.6

JasonNielsen — Sun, 12 Dec 2021 16:16:23 GMT

To fix the identify from loading up on the start of the application just delete the following text highlighted in red from the config.xml file.

<widget label="Identify" left="330" top="80" preload="open"                
                icon="assets/images/i_info.png"
                config="widgets/Identify/IdentifyWidget.xml"
                url="widgets/Identify/IdentifyWidget.swf"/>

To answer your second question on do you use Field names or Aliases for the identifyWidget.xml I use the Alias for the fields and it seems to work fine for me. 🙂

Re: Identify 2.1.6

MarshallPlants — Tue, 26 Oct 2010 18:42:43 GMT

Use the aliases and it's also case sensitive.

Re: Identify 2.1.6

DonaldWasson — Fri, 05 Nov 2010 11:47:19 GMT

Can someone please elaborate on how to use the alias instead of the field names with the identify tool. I have not been able to use the alias in the fields list of the identify tool with any success at this time. For example when I place the field names of an sde feature class between the identify field tags the identify tool works but when I change the field names to the field aliases the tool does not work only the alias names appear in the identify window. From this post I can read that some users have successfully used the alias so maybe one of them can add an example to this thread on how to use the field alias names with the identify tool. Can someone please help? Thanks in advance.

Re: Identify 2.1.6

EmilyLaMunyon — Fri, 05 Nov 2010 13:32:48 GMT

Did you ever figure this out, I am having the same issue?

Emily

Re: Identify 2.1.6

DonaldWasson — Fri, 05 Nov 2010 14:56:10 GMT

Hi Emily

It does work you just put the alias names between the field tags and use comas to separte them as the other users have reported. There is just one tricky part regarding alias names that I have seen in other situations within the ESRI core products. You bascially have to refreshes your map document layers and maybe even refresh your map services if you create or modify your alias after you set up your widget which is what I had done. Make sure you can see your alias names in your map document attribute table before you try use the alias names in your widget. Hope this information helps you and others out. Thanks for posting your question on this thread.. Donald

Re: Identify 2.1.6

NadeemShaukat — Thu, 11 Nov 2010 02:44:18 GMT

I have added this identify widget to my map. I have added the widget to the widget container, compiled it and added my changes to the identifywidget.xml. My problem is when I use the widget and click something....it displays the result box with the layer it is pulling from and it also shows the field, however, there are no values?! Also, when the application first opens, the identify widget automatically open by default. Where do I change this to where it will not auto-launch the widget?!

Thanks,
Josh C.

Robert did a great job enhancing these widgets but sometimes things do not work because we miss a point in implementing them.

I also installed this widget, compiled and tried to use the Find tool but no results were returned. I get the message on the Widget Panel "Identify operation is not supported on this service", though Query and Find operations work fine.

Following is the Layer blocks in my xml. Everything else is same as in the original xml.
                            <layer>
   <name>Water Quality Sampling Locations</name>
   <fields>StationID,Project,Status,StreamName</fields>
   <linkfield></linkfield>
   <linkprefix></linkprefix>
   <linksuffix></linksuffix>
   <iconfield></iconfield>
   <iconprefix></iconprefix>
   <iconsuffix></iconsuffix>
   <zoomscale>15000</zoomscale>
   <forcescale>true</forcescale>
</layer>

nshaukat

Re: Identify 2.1.6

NadeemShaukat — Thu, 11 Nov 2010 02:55:54 GMT

Robert did a great job enhancing these widgets but sometimes things do not work because we miss a point in implementing them.

I also installed this widget, compiled and tried to use the Find tool but no results were returned. I get the message on the Widget Panel "Identify operation is not supported on this service", though Query and Find operations work fine.

Following is the Layer blocks in my xml. Everything else is same as in the original xml.
                            <layer>
   <name>Water Quality Sampling Locations</name>
   <fields>StationID,Project,Status,StreamName</fields>
   <linkfield></linkfield>
   <linkprefix></linkprefix>
   <linksuffix></linksuffix>
   <iconfield></iconfield>
   <iconprefix></iconprefix>
   <iconsuffix></iconsuffix>
   <zoomscale>15000</zoomscale>
   <forcescale>true</forcescale>
</layer>

nshaukat

I have figured it out myself. The value in the <name> tag is not the same as label value in the operational layer. It's the exact name of the feature class in the service.

nshaukat

Re: Identify 2.1.6

AaronWeier — Tue, 16 Nov 2010 19:27:38 GMT

love the tool, thanks for sharing!

it works great for a single hyperlink, i'm curious if it supports multiple hyperlinks?

i've tried hacking it but i'm not a flex dev and i don't fully know what i'm doing.

I tried adding another 'layer' to the 'layers' section but that didn't work...

any thoughts or working code examples are very much appreciated!

AW

Re: Identify 2.1.6

AaronWeier — Wed, 17 Nov 2010 11:40:36 GMT

Hi All,

i figured it out. I simply added a second layer to my map to get the second hyperlink.

I changed my service to be "dynamic" instead of "feature". Now the identify tool shows two features. This works great.

I'm still curious if there is any potential for the tool to handle multiple hyperlinks on a single layer.

Again, thanks for the sharing the tool! It's very easy to use and configure!!

AW

Re: Identify 2.1.6

RobertScheitlin__GISP — Wed, 17 Nov 2010 17:25:57 GMT

Aaron,

I have looked at the possibility of multiple hyperlinks but as of right now I have no plans to implement this. I have a higher priority of adding the attachment inspector for the next release.

Re: Identify 2.1.6

HaroldBostic — Sat, 20 Nov 2010 00:39:30 GMT

Robert,
one of my layers requires a proxy to access it. What's the best way to use a proxy for one layer using this widget?

Thanks

Re: Identify 2.1.6

BrettFlodine — Mon, 22 Nov 2010 00:21:08 GMT

Robert,

Thank you for the updated widget it works great! I am wondering what I need to do to change the color of the field names so they are different from the attributes? I had this working in my 1.3 viewer.

Brett

Re: Identify 2.1.6

HaroldBostic — Tue, 23 Nov 2010 16:32:25 GMT

For the proxy issue, I patterned the methods used in the main config file and set the identifyTask.proxyURL for the layers that require it.

Thanks

Re: Identify 2.1.6

RobertScheitlin__GISP — Wed, 24 Nov 2010 16:04:13 GMT

Harold,

I will probably be putting out a new version with minor bug fixes and would like to include what you did for the proxy thing as your code would be tested and I don't have any services that need a proxy to test with.