I am using the Schema Scanner with a dynamic writer in my workspace and it is awesome except that it often incorrectly identifies some of my integer fields as date/time fields. If I turn off the date/time detection then my actual date/time fields get written as strings or integers. Right now I am running it with date/time detection on and then I put an attribute manager on the schema and find the ones it has incorrectly identified and manually adjust them but I feel this kind of takes away from the dynamic nature of the schema scanner. Is there a better way to do this? I wish I could tell it to ignore certain fields or specify the fields that it should look for date/time in but again that is taking away from the dynamic nature of the bench.
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.


