In the change detector is there any way of transferring an attribute value from the original feature to the updated feature when it's not either a Key Attribute or one of the attributes listed in the matching strategy
e.g.
Question
ChangeDetector - pass attribute from original features to updated features when not one of the selected attributes
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.
+59- Safer
Did you get an answer to this? It looks to me like you can't, which is very weird. I would have expected a Merge Attributes section, like on other transformers. It looks to me like you'll have to follow up with a FeatureMerger transformer to copy info across. Not ideal and definitely worth posting an Idea for.
+46- Influencer
No, I'm presuming it's not possible. I couldn't decide whether a FeatureMerger would be the best way, or whether to include the UniqueID as a an Attribute to Match, discard the features that only differed by the UniqueID attribute then fetch the value from a list built in the change detector. Or whether if having to use the FeatureMerger anyway, is the ChangeDetector even worth keeping?
I thought I might be missing something, as I thought it might be a common use, to compare records from say an outside source, with an existing table and then want to update the existing table using a unique key that only exists within that table, not the outside source.
+22- Contributor
Hi @ebygomm, I ran into the same issue. Did you post an idea? I couldn't find it.
Using a FeatureMerger seems the best way to me as well.
+46- Influencer
Hi @ebygomm, I ran into the same issue. Did you post an idea? I couldn't find it.
Using a FeatureMerger seems the best way to me as well.
No, I didn't get round to posting an idea, it ended up no longer being an issue for the particular workspace i was developing.
+22- Contributor
No, I didn't get round to posting an idea, it ended up no longer being an issue for the particular workspace i was developing.
I mentioned you and @mark2atsafe in the idea. I hope that is fine for you both: https://community.safe.com/s/idea/0874Q000000j0MdQAI/detail
+46- Influencer
