+5I have a custom transformer. One of the incoming attribute values contains a comma separated list of strings. As soon as the record passes through any subsequent transformer, the value is set to null.
Here is the incoming data with WOTEMPALTEIDs as the value that's getting dropped.
After passing through any transformer (AttributeManager in this example), WOTEMPLATEIDs values are dropped to null. The other values are unchanged.
Thanks
+5I pulled this logic out of the custom transformer and everything worked as it should. There seems to be something about that list that passing into a custom transformer made it go south.
+63Whats the configuration of the attributemanager? Its possible its setting that attribute value to null
+5Whats the configuration of the attributemanager? Its possible its setting that attribute value to null
Hi hkingsbury,
The attributemanger can be simply default as shown. For whatever reason, when this processes in my custom transformer, it clears out the WOTEMPLATEIDs values to null. The other attributes are unchanged.
