Skip to main content
Solved

Attributes Not Writing to ArcGIS Portal Feature Service During FME Migration

  • November 19, 2025
  • 2 replies
  • 45 views

neeraja.kolipe
Contributor
Forum|alt.badge.img+6

Hello,

 

I am attempting to copy an ArcGIS Server Feature Service from our Production portal to our Staging portal as a test migration using ArcGIS Data Interoperability (FME). The migration runs successfully, and the layer is created on the destination portal with all point features appearing correctly. However, every attribute field in the destination portal is empty for the layer.

For this workflow, I used:

  • Reader: Esri ArcGIS Server Feature Service

  • Writer: Esri ArcGIS Portal Feature Service

The strange part is that when I inspect the data immediately before the writer, all attribute values are present and correct in the Visual Preview. But once the writer publishes the layer to the portal, the attributes do not appear, only the geometry is transferred.

Could you please help identify what might be causing the attribute values to be lost during the migration?

Best answer by davechoi

@neeraja.kolipe Do your attribute names contain any uppercase values? ArcGIS Enterprise/Portal's Data Store is a PostgreSQL database (unless you do custom configurations during deployment) that does not allow uppercase values for attribute names, hence all your attribute names must be lowercase. If your attribute names contain uppercase letters, this becomes the alias and the writer creates the attributes but the data will not transfer over.

Try using BulkAttributeRenamer before the writer and change all attribute names to lowercase, and let me know if that resolves your issue.

2 replies

davechoi
Safer
Forum|alt.badge.img+12
  • Safer
  • Best Answer
  • November 20, 2025

@neeraja.kolipe Do your attribute names contain any uppercase values? ArcGIS Enterprise/Portal's Data Store is a PostgreSQL database (unless you do custom configurations during deployment) that does not allow uppercase values for attribute names, hence all your attribute names must be lowercase. If your attribute names contain uppercase letters, this becomes the alias and the writer creates the attributes but the data will not transfer over.

Try using BulkAttributeRenamer before the writer and change all attribute names to lowercase, and let me know if that resolves your issue.


neeraja.kolipe
Contributor
Forum|alt.badge.img+6
  • Author
  • Contributor
  • November 21, 2025

@davechoi Thank you! That solution worked perfectly. I really appreciate your help!