Currently in the AttributeValidator the Unique rule is treated as each attribute to validate is required to be unique (individual) I would like to see a configuration option added for "composite" which would treat all selected attributes as if they were concatenated. Yes this can be accomplished by simply adding a StringConcatenator and computing a new concatenated column to validate, but many other transformers that have key parameters accept multiple key fields and treat them in this composite fashion, so why not the AV.
Archived
Attribute Validator Unique Rule add Configuration for composite vs individual
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.
+18- Safer
Updated idea statusGathering Interest→Archived
Idea merged into: