Skip to main content
  • EN

I have a series of Feature Services in ArcGIS Online.  

Unfortunately they contain attribute names of varied case.

 

This is proving difficult for me when I try to create a dynamic workflow that updates the data in ArcGIS online.  When the Reader reads the source data (also of varied case), it converts them all to lower case.

Therefore, when my workflow tries to write to ArcGIS online, it cannot find matching attributes to write to because the case is different.

It is now too late for me to change all the layers on ArcGIS online to lower case because of downstream dependencies. 

Will I have to write a separate workflow for each individual layer and individually do the field mapping?

Or is there a way around this ?

Where is your source data coming from?

My data is coming from ArcGIS Enterprise Feature Services (non hosted but by reference to SDE).  Pretty much the same schema as the destination but different service names.

I’m fairly new to FME and I’ve since just discovered the tutorials for Dynamic workflows in FME resources and think I will try a method like the following which involves the use of AttributeManager to rename all the fields within a dynamic workflow.  Will report back. :)

https://support.safe.com/hc/en-us/articles/25407544150029-Dynamic-Workflows-Destination-Schema-Contains-Different-Feature-Type-Names

 

The above tutorial was too different from my case.

However, after persistence and nearly giving up, I finally SOLVED it  !!!

Yes, the reader makes all the attribute names lower case, however, in my case, with my source being ESRI format, I discovered the ‘Alias Mode’ setting.   I chose the option ‘Replace Attribute Names with Aliases’ and now my fields look right, in their original case.  I hope this helps somebody.

 

An Alias is not the field name, it is a separate piece of field metadata that different GIS applications use to display field names in a more human readable way on screen within the app.

As far as am aware, will not be able to Dynamically write back with these since will need to match the actual field names.

It sounds like the real field names are actually lower case, but the Admin set a separate Alias for them such that if use it in n ArcGIS etc. then the Dialogs like Attribute Tables etc. will display the Alias rather than the true field names and that is possibly what have been used to seeing.

Can confirm this if download the data to an Eg. FGDB and look at the raw Feature Classes or Tables in the Catalog view to see actual field names.

Reply


Community Stats

30,143
Posts
114,415
Replies
37,785
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.