I suspect this might be an ESRI thing rather than an FME thing, but is it expected behaviour that if a feature is written to a table which has a non-nullable long field that field gets populated as zero if an attribute is missing? No error, or warning?
Login to the community
No account yet? Create an account
An FME Account is required to contribute
LoginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.


