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

fieldAliases when using the identify task.

TonyCollins

Hi,

Can someone recommend the best way to do this? (Do I have to make multiple trips to the server?)

Find more posts tagged with

Accepted answers

All comments

AlaaBakry

Hello Robert,
Yes the service rest has the latest aliases like this snapshot

and weirdly I get the identify results(check snapshot) with other names/aliases I don't know where they are coming from

I want to mention that i have only one layer that get the updated aliases in the identify task results, others are not!

Appreciate your support.

rscheitlin

Alaa,

Did you re-publish the map service? Have you checked to see if the map services rest endpoint has the updated alias values?

AlaaBakry

Robert is there any way to get field names instead of aliases in identify result?

I changed field aliases in the MXD, republished the map services, and cleared server cache, and still getting the aliases(maybe from datasource), any thoughts?

ArcGIS Server 10.3

JSAPI 3.14

ShaneBailey

In my department we are using another team's layer services and do not have control over the ALIAS assignments. Currently the ALIAS value is the same as the FIELD_NAME value. I would like to have functionality similar to built-in PopUp widget that allows for alias overrides if possible.

This is indeed an awesome widget already and would be even more excited if this functionality was available as well. Is this possibly on the roadmap?

thank you!

TonyCollins

Tony,

Yep that is exactly what happens. So all you have to do is define the fields aliases in ArcCatalog for the individual feature classes or in ArcMap if you only want those to be defined for that particular map service.

I got it working, but only if I set the aliases at the MXD level. Not to worry as that is the preferred method anyway!

Thanks Robert,

rscheitlin

Tony,

Yep that is exactly what happens. So all you have to do is define the fields aliases in ArcCatalog for the individual feature classes or in ArcMap if you only want those to be defined for that particular map service.

TonyCollins

Tony,

I have to say a still don't understand, the fields that are returned are always aliases in my experience... Have you recently defined the fields alias and have yet to clear your rest cache and restart your map service? The field ordering issue has always been there, Abode does not guarantee the order of items in an array collection.

Thanks Robert,

What if you have no aliases defined? Does it resort to the field_name? I don't have any REST cache issue, but if that is the case then i will look there instead of my code!

DasaPaddock

Some more info on the ordering issue:
http://forums.arcgis.com/threads/13549-Does-2.1-Fix-the-random-field-ordering?p=42722&viewfull=1#post42722

rscheitlin

Tony,

I have to say a still don't understand, the fields that are returned are always aliases in my experience... Have you recently defined the fields alias and have yet to clear your rest cache and restart your map service? The field ordering issue has always been there, Abode does not guarantee the order of items in an array collection.

TonyCollins

Tony,

I am a little confused... The identify task only returns field aliases.

Ah, hopefully I have something wrong then! This has been working fine for months but my users are asking for field Aliases to display rather than the Field Names (Which are unordered but no one seems to have that answer down).

When I inspect identifyResult.feature.attributes the object contains paired values [FIELDNAME, Value].

Does this make sense?

rscheitlin

Tony,

I am a little confused... The identify task only returns field aliases.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

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