Skip to main content
Archived

Features that fail to join with a 1:M Cardinality

Related products:Transformers
  • March 29, 2016
  • 0 replies
  • 8 views
M

Joiners with a 1:M cardinality do not allow features with zero matches to pass through. I'd want to know what falls off for data validation purposes...adding a (1:M..0) cardinality would let me test _matched_records for values of 0.

Alternatively, Change all cardinality levels to not include 0 matches and add a Failed output for features that fail to join

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.

Community Stats

32,724
Posts
124,149
Replies
41,216
Members
Terms & ConditionsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.