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?
+22- Safer
Hello,
Thanks for posting your question to the community! Thanks for brining this to our attention.
We looked into it on our end. This behavior is probably expected (Note: We haven't carefully investigated to confirm the current behavior in other scenarios).
Scoping preference here. Wondering if you would see value added to see the ArcSDE writer honor the default values in the Geodatabase when attributes are missing in use cases you’ve been through?
Thanks!
Reply
Rich Text Editor, editor1
Editor toolbars
Press ALT 0 for help
Helpful Members This Week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.