Question about <fields> configuration in Identify widget version 2.5.3

[KenHolmquist]

Robert,

First of all, let me once again thank you profusely for all of the work you have done to create and maintain these wonderful widgets.  They are excellent.

This question is the same one I mistakenly started in the Comments box on the page from which I previously downloaded the Identify widget.  With the previous version of your Identify widget, I was able to have a <fields> definition like <fields>TPROJ_NAME:Project Name,SCALE:Scale</fields> in the configuration xml file so that I could define friendly attribute field names, such as "Project Name" rather than TPROJ_NAME to be shown to the viewer users.  It is my understanding that with the version 2.5.3 of the Identify widget, this is no longer supported and that whatever the REST field alias is that is what the Identify widget is going to display as the attribute field name.

I was just wanting to know if I am missing something and there is still possibly some way to configure the widget to show the friendly names without going into the mxd file and defining them there.

Thanks,
Ken

[RobertScheitlin__GISP]

Ken,

   I don't remember having that ability in even my old 1.x versions of the identify widget (even went back and look though a couple old versions)... But the answer is no you will have to go into the mxd and assign aliases to the fields (not sure why you are leaning towards this being difficult... or undesirable). What most people don't understand is that the IdentifyTask is a completely different animal than the QueryTask. The identify Task because is actually deals with a Map and not just the data it returns aliases for field names and never returns the actual field names unless the alias has been set to the same as the field name. Anyway there are a lot of technical reasons that the Identify Widget is not like the eSearch or other widgets I have produced that allow you to define aliases in the xml.