LAE

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: aop

Currently the change metadata node errors when metadata changes pin contains fields that are not found in input data pin (Field X not found in input data). However we would mainly want to use this node in scenarios where change metadata pin contains a complete mapping table for field names in certain system (could contain more fields than is in input data). The node could handle this if the error handling would not be fixed to throwing an error always when change metadata pin contains extra fields not present in input data. Basically it seems adding a parameter to exception behaviour tab would enable to use the node in this kind of scenario as well.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: aop

As a side note to allow the change metadata node to be used for name conversion only (no data type conversions) the NewTypeField should be an optional parameter not a required one.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: DanRosenblatt

Having field names in the Metadata Changes input that are not present in the Input Data has been created as a new enhancement in our issue tracking system as LAL-610. I'm attaching a sample graph that you might find useful in this situation. The data you are attempting to connect to the Metadata Changes input might look a little different from what I have, but the general idea is joining it on the output of a Get Metadata node to remove the extra field names.

If you are looking to change the field names only, you should be able to accomplish that with a Filter node.
Attachments:
MetadataEnhancement.brg

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Tim Meagher

Dan,

For the second item (changing the field names only), this would only be possible in a filter node if the field names were known in advance.
In the Change Metadata node, these can come from any data source.

If the data is acquired from different data sources - for instance a database where one table provides the real data with strange internal names for the columns and some metadata definition table provides the information with some human understandable names for the columns in the first table, then this information could change dependent on the data queried.

It wouldn't be possible then to just change the names directly in a Filter node as they wouldn't be known in advance.

It is possible to do this kind of conversion already in the LAE (see attached).

However it requires more work than just using the Change Metadata node - since the Change Metadata node requires that the new field type be specified as well.
In such cases, where the field type is not going to be changing, more effort and more processing is required than just using the Change Metadata node.
It should really be a quicker operation since no field conversion needs to take place and no verification needs to be performed as well.

I think there might already be an enhancement request about this raised within our internal system, but if not one should be added I think.

Regards,
Tim.
Attachments:
ChangeMetadataOnly.brg

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: jdoherty

Hi All,

Is there any update on this? Was an enhancment request raised?

We've encountered a similar issue where we need to change the field names to uppercase, again without knowing the field names in advance.

Thanks,
John

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: bpurcell

Hi

trying to bump this in the hope of getting an update

Thanks !

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Tim Meagher

Hi,

The first enhancement request suggested - allowing the Change Metadata node to work when the metadata changes input has fields which aren't in the input data has been raised as an enhancement request (Issue#: LAL-1762).
The second issue - about changing only the field names and not the field type, I'm not sure is necessary anymore.
This might have been a recent enhancement, or maybe it's always been there, I'm not sure, but if the value of the "NewTypeField" in the metadata changes input is NULL, then no type conversion will be performed.
So you should be able to use the node to simply change the field names and not the field type.
You still need to specify a "NewTypeField" and if you only wanted to change the names of the fields, then all values in the "NewTypeField" will need to be NULL.

Tim.