When setting the output feature definition to "Automatic", it would be nice if the data types were preserved even when the attributes are renamed in the workspace. As it is, all the data types are set to something like "char(200)" if the attributes hitting the writer has been renamed.
Released
Automatic feature definition to preserve data types
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+7- Participant
An example:
the data types are retained in the Attribute Manager until just one attribute is renamed. From that moment on all data types are lost and set to "char(200)".
+26- Contributor
But how could you know the data type if an attribute is created in the workspace (by AttributeManager or any other transformer)?
+22- Safer
We'd have to give you the option to set the data type in, say, the AttributeManager. And any attributes added by other transformers would need their types added too. We are going to make progress on this in FME 2017, but complete nirvana may take a couple releases.
I don't mind attributes created inside the AttributeManager to lack data types, but it is unexpected that all existing attributes lose their datatypes if one of them is renamed.
+8- Supporter
When a field is unknown as it comes in via a generic via a generic reader or dynamic attributes, this often is a problem. Especially when writing out to databases that are a bit more picky.
The AttributeRenamer transformer should get an extra option of Type, to be able to quote the data type we wish the output to be in.
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.