The ChangeDetector transformer is great particularly when enriching source data and updating a target database, but it is sometimes difficult to track which attributes are shared between the Original and Revised ports. It would be terrific if the attribute lists could be color coded, or have some other kind of indicator to quickly shed light on the attributes that are on both ports vs those that are only on one port. More than once I have been confused why I was seeing so many updates when some enriched attribute hadn't yet been considered before reaching the revised port. I'm sure there are other transformers that could benefit from similar treatment.
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, 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 a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, 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.
+11- Supporter
Another option is prefixing or suffixing, for example either if the transformer (such as the FeatureMerger) supports it or using a BulkAttributeRenamer to tag those attributes before sending them to a subsequent transformer.
Helpful Members This Week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.