Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Multidomain MDM 10.3 HotFix 3
  • All Products

Table of Contents

Search

  1. Introduction
  2. Configuring Hub Console Tools
  3. Building the Data Model
  4. Configuring the Data Flow
  5. Executing Informatica MDM Hub Processes
  6. Configuring Application Access
  7. MDM Hub Properties
  8. Viewing Configuration Details
  9. Search with Solr
  10. Row-level Locking
  11. MDM Hub Logging
  12. Table Partitioning
  13. Collecting MDM Environment Information with the Product Usage Toolkit
  14. Glossary

Configuration Guide

Configuration Guide

Back Next

Column Properties

Column Properties

You can configure the properties of
Informatica MDM Hub
 columns.
In the MDM Hub, an empty string is the equivalent of a null value regardless of the database type that contributes the empty string.
Informatica MDM Hub
 columns have the following properties:
Display Name
The name of the column that the
Hub Console
 displays.
Physical Name
The name of the column in the base object. The
Hub Console
 suggests a physical name for the column based on the display name.
The physical column name cannot be a reserved column name and it cannot include the dollar sign '$' character.
Nullable
If enabled, the column can contain null values. If you do not enable the Nullable property, you must specify a default value.
When the Nullable property is disabled for columns, if a record is updated in Data Director or during a SIF PUT operation, a cross-reference record is created with values only for the updated fields. All the other cross-reference record fields, including the fields that must not be null, have null values. During the best version of the truth (BVT) calculation for the record, null values can be the winner for fields that must not be null, and an error occurs.
To ensure that the BVT calculation takes into account the fields that must not be null, set the
cmx.server.put.autopopulate.missing.user.columns.bo.list
 property in the
cmxserver.properties
 file. Set the property value to a comma-separated list of the names of base objects that have columns with the Nullable property disabled. When the property is set, the MDM Hub updates the null values in the cross-reference record with values from the associated base object. This ensures that during BVT calculation, null values are not the winner for fields that must not be null.
Data Type
The data type of the column. For character data types, you can specify the length property. For certain numeric data types, you can specify the precision property and scale property.
Length
For character data types, specify the number of characters allowed.
Precision
For numeric data types, specify the number of digits allowed in the number, including all decimal places.
Scale
For numeric data types, specify the number of digits allowed after the decimal point.
Has Default
If enabled, you can specify a default value.
Default
The default value for the column.
Informatica MDM Hub
 uses the default value if the column is not nullable and no value is provided for the column.
If you enable the Unique property or if you disable the Nullable property, you must specify a default value for the column.
Trust
If enabled,
Informatica MDM Hub
 uses the source system value with the highest trust score.
If not enabled,
Informatica MDM Hub
 uses the most recently updated value.
Unique
If enabled,
Informatica MDM Hub
 enforces unique constraints on the column. If unique constraint is enabled, ensure that duplicate values do not exist in the unique column. Most organizations use the primary key from the source system for the lookup value.
Informatica MDM Hub
 rejects any record with a duplicate value in the column when you enable the Unique property. You must configure a default value for the column if you enable the Unique property.
If you enable the Unique property for consolidated base objects, an insert into the base object could fail because
Informatica MDM Hub
 might load the same key from different systems. Ensure you have unique keys for this column across all source systems.
Validate
If enabled,
Informatica MDM Hub
 applies validation rules during the load process to downgrade trust scores for cell values that are not valid. You must configure validation rules if you enable the Validate property.
Apply Null Values
Set this property to whatever default you want to use when a null value is the most trustworthy value for this column. A process uses this property when the process cannot determine the setting of the
Allow Null Update
 property for the column in a staging table.
  • True. When enabled, if the most trustworthy value for this column is a null value, a process can write the null value to the base object record.
  • False. Default. When disabled, a process cannot write a null value to the base object record as long as another source system contributes a non-null value for this column.
The
Apply Null Values
 property works the same way as the
Allow Null Update
 property. For more information about the
Allow Null Update
 property, see Properties for Columns in Staging Tables.
GBID
If enabled,
Informatica MDM Hub
 uses this column as the Global Business Identifier (GBID) for the base object. You can configure any number of GBID columns for API access and for batch loads.
On Oracle, if GBID is enabled, you must configure the column as an INT datatype or as a CHAR, NCHAR, VARCHAR, and NVARCHAR2 datatype with a length of 255.
On IBM DB2, if GBID is enabled, you must configure the column as an INT datatype or as a VARCHAR, and NVARCHAR datatype with a length of 255.
On Microsoft SQL Server, if GBID is enabled, you must configure the column as an INT datatype or as a VARCHAR, and NVARCHAR2 datatype with a length of 255.
If you enable GBID for any base object column,
Informatica MDM Hub
 creates an index for the base object.
Informatica MDM Hub
 does not allow you to create a custom index for the base object because the base object has an index.
Putable
If enabled for system columns, batch jobs and SIF API requests can insert or update the data in the system column. You cannot enable the Putable property for the following system columns:
  • ROWID_OBJECT
  • CONSOLIDATION_IND
  • HUB_STATE_IND
  • LAST_ROWID_SYSTEM
  • CM_DIRTY_IND
If a Put or Cleanse Put API request tries to update a system column but you do not enable the Putable property, the API request fails.
User-defined columns and the INTERACTION_ID and LAST_UPDATE_DATE system columns are always putable.
0 COMMENTS
We’d like to hear from you!