Skip to main content
  • EN
  • Home
  • Forums
  • FME Form
  • Data
  • Does FME 2024.0 Support Esri's New Big Integer Field Types When Creating New Dynamic Feature Classes?

I have been using Dynamic writers to create feature classes and tables in an Esri File Geodatabase for years. I normally use the FME field type “fme_int32” to create Long Integer field types. However, I need to create attributes using Esri’s new ‘Big Integer’ field type. I assumed I could use “fme_int64” but when I run my workspace in FME 2024.0, it runs without errors but it doesn’t create the new feature class. When I change the 2 fields from fme_int64 back to fme_int32, it runs without errors and creates the new feature class. 

I have ArcPro 3.2.2 installed which also supports the new Big Integer (64 Bit) field types.

My question is: Should I be using a different FME Field type besides ‘fme_int64’ to generate Big Integer field types via a Dynamic FGDB Feature Class Writer?

Thanks in advance.

Hi @mmccart 

 

After running a few tests, I wasn’t able to reproduce the issue on my end. 

 

Could you please share your workspace or how you configured your writer and changed the data type from int32 to int64?
 

Thanks! 

Crystal 

Crystal,

I am using the Schema (From Table) feature type in a FeatureReader. As you can see from this screenshot, the fme_int64 attribute type is defined for these two attributes.

 

I am then using a Esri FGDB feature type in a writer with Dynamic Schema Definition: 

 

Let me know if you need any additional information.

Hi @mmccart 

 

If you are able to share your workspace and data with us, this will allow us to reproduce the issue and we will be able to file a bug report. 

 

Crystal 

@cfitzpat can you send me over your email address (either here or via private message) and I will send it to you. I don’t want to post the workspace here. Thanks. 

@cfitzpat I just emailed you the workspace. Let me know if you don’t get it.

@mmccart I received it. Thank you! 

This issue should now be fixed in the latest version of FME (Build 24219).


However, to maximize performance, it may be better to change the value of fme_schema_handling from schema_only to schema_and_data using the AttributeManager.


This informs the writer pipeline that the feature contains schema information for creating a dynamic feature type along with the first data feature to be written to that dynamic feature type.


schema_only tells the writers to discard non-schema information on the feature, which is why nothing was being written previously.

Reply


Community Stats

30,351
Posts
115,336
Replies
38,078
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.