Skip to main content
Solved

When writing to ArcGIS Portal, all my mixed-case field names show as lowercase in my feature service. Why is this happening?

  • November 14, 2016
  • 1 reply
  • 120 views
fmelizard
Contributor
Forum|alt.badge.img+17

I have a workspace that contains an ArcGIS Portal writer with mixed-case field names. It runs without a problem when first creating the feature service on ArcGIS Portal. However, when I attempt to use that same workspace to write updates to that feature service, I see warnings similar to the following:

ArcGIS Online Feature Service Writer: Attribute 'myFieldName' on feature type 'Feature_Type' does not match any field on the corresponding layer/table. The attribute will be ignored

If I check the feature service itself, I can see that all the mixed-case field names have actually been set to lowercase (so, myFieldName is actually set to myfieldname).

Best answer by laurawatsafe

This can happen when publishing to a Portal for ArcGIS that uses an ArcGIS Data Store. According to the known-issues listed at this page: http://solutions.arcgis.com/utilities/gas/help/facility-reports-gas-distribution/

 

"When publishing to Portal for ArcGIS with an ArcGIS Data Store Hosting Server, field names will be auto converted to lowercase."

When using FME to write updates to a feature service like this, make sure the casing of field names on the writer feature type in your workspace matches the casing of the field names in the published feature service layer.

View original
Did this help you find an answer to your question?

1 reply

laurawatsafe
Safer
Forum|alt.badge.img+11
  • laurawatsafeSafer
  • Safer
  • Best Answer
  • November 14, 2016

This can happen when publishing to a Portal for ArcGIS that uses an ArcGIS Data Store. According to the known-issues listed at this page: http://solutions.arcgis.com/utilities/gas/help/facility-reports-gas-distribution/

 

"When publishing to Portal for ArcGIS with an ArcGIS Data Store Hosting Server, field names will be auto converted to lowercase."

When using FME to write updates to a feature service like this, make sure the casing of field names on the writer feature type in your workspace matches the casing of the field names in the published feature service layer.

Reply


Helpful Members This Week

Community Stats

31,057
Posts
117,740
Replies
38,831
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie 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.