Table of Contents

Search

  1. Preface
  2. Part 1: Introduction
  3. Part 2: Configuring Hub Console Tools
  4. Part 3: Building the Data Model
  5. Part 4: Configuring the Data Flow
  6. Part 5: Executing Informatica MDM Hub Processes
  7. Part 6: Configuring Application Access
  8. Appendix A: MDM Hub Properties
  9. Appendix B: Viewing Configuration Details
  10. Appendix C: Row-level Locking
  11. Appendix D: MDM Hub Logging
  12. Appendix E: Table Partitioning
  13. Appendix F: Collecting MDM Environment Information with the Product Usage Toolkit
  14. Appendix G: Informatica Platform Staging
  15. Appendix H: Informatica Platform Mapping Examples
  16. Appendix I: Glossary

Requirements for Exact-match Columns in Match Column Rules

Requirements for Exact-match Columns in Match Column Rules

Exact-match columns are subject to the following rules:
  • The names of exact-match columns cannot be longer than 26 characters.
  • Exact-match columns must be of type VARCHAR or CHAR.
  • Match columns can be used to match on any text column or combination of text columns from a base object.
  • If you want to use numerics or dates, you must convert them to VARCHAR using cleanse functions before they are loaded into your base object.
  • Match columns can also be used to match on a column from a child base object, which in turn can be based on any text column or combination of text columns in the child base object. Matching on the match columns of a child base object is called intertable matching.
  • When using intertable match and creating match rules for the child table (via a foreign key), you must include the foreign key from the parent table in each match rule on the child. If you do not, when the child is merged, the parent records would lose the child records that had previously belonged to them.

0 COMMENTS

We’d like to hear from you!