Skip to main content
Solved

inserting subtype value

  • July 23, 2026
  • 1 reply
  • 24 views
mohamedalsobh
Contributor
Forum|alt.badge.img+9

I am experiencing an issue when inserting values into a subtype field in an ArcGIS Geodatabase using FME.

I am attempting to populate the type field, which is configured as the Subtype Code field. However, FME returns the following error: 

2026-07-23 12:10:18|   0.7|  0.0|ERROR |An error occurred while attempting to add the subtypes to the table/feature class 'lcLandcoverUnitInfo'. The error number from ArcObjects is: '-2147219885'. The error message from ArcObjects is: {An expected Field was not found or could not be retrieved properly. [lcLandcoverUnitInfo]}
 

What makes this even more confusing is that I am using the same workflow in the same workspace for other tables, where the subtype values are inserted successfully without any issues.

I have also verified the following:

  • The field has the same data type.
  • The field name is identical.
  • The subtype code exists in the geodatabase.
  • I refreshed/updated the geodatabase schema in FME to ensure it matches the latest changes.

Despite all of these checks, the problem only occurs with this specific table, even though its configuration appears to be the same as the others.

 

Best answer by mohamedalsobh

I solved the issue by creating a new field called type1, assigning the subtype to it, and then reassigning the subtype back to the original type field. After that, FME worked correctly.

It seems there was some hidden or stale subtype metadata in either FME or the geodatabase. If anyone knows why this happens, I'd appreciate the explanation.

    1 reply

    mohamedalsobh
    Contributor
    Forum|alt.badge.img+9
    • mohamedalsobhContributor
    • Author
    • Contributor
    • Best Answer
    • July 27, 2026

    I solved the issue by creating a new field called type1, assigning the subtype to it, and then reassigning the subtype back to the original type field. After that, FME worked correctly.

    It seems there was some hidden or stale subtype metadata in either FME or the geodatabase. If anyone knows why this happens, I'd appreciate the explanation.

      Community Stats

      32,751
      Posts
      124,206
      Replies
      41,258
      Members
      Terms & ConditionsAccessibility statement
      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.