IBM Content Navigator, Version 2.0.3 Supports: Content Manager, FileNet P8

Compatible data types

You can map a property to another property if the data types are compatible. When you map a property to another property, the properties are treated as a single property in the cross-repository search. Then, IBM® Content Navigator validates the value that you enter for the search criteria and uses the value with the corresponding data type to search each repository.

For example, to do a cross repository search with an account number value, when the Account Number property is defined as a string property in one repository and defined as an integer property in another repository, you must map the properties. Then, when a value is entered for the search criteria, the value is treated as an integer for data validation, and the search retrieves a string value from one repository and an integer value from the other repository.

You can map properties of mixed types if the values intersect.

A string property can be mapped to a number property when the string value includes number characters only.
A string property can be mapped to a Boolean property when the string value includes strings for true or false.
You can map a string property to a different type of string property. For example, an alphanumeric string data type can be mapped to an alphabetic string data type or to a numeric string data type.
You can map a number property to a different type of number property. For example, an integer data type can be mapped to a decimal value data type or to a floating-point number data type.

Exceptions to mapping

The following mappings are not allowed because the values do not intersect:

A numeric string cannot be mapped to an alphabetic string.
An alphabetic string cannot be mapped to a numeric string.
An alphabetic string cannot be mapped to any number property.
A numeric string cannot be mapped to a Boolean property.
A Boolean property cannot be mapped to a numeric string.
A Boolean property cannot be mapped to any number property.
A time stamp property cannot be mapped to any other property.
A date property cannot be mapped to any other property.
A time property cannot be mapped to any other property.
A child component cannot be mapped to any other property.

The following special types can be mapped to a string property or an extended alphanumeric string property, but they cannot be mapped to any other properties:

GUID (globally unique identifier)
ID (for CMIS repositories)
Object

Search criteria entry data validation

For search criteria that includes a number property that is mapped to an integer, you can enter integer values only.

For search criteria that includes a number property that is mapped to an alphanumeric string or a numeric string, you can enter positive integer values only.

Any user-defined constraints on property values are not applied to the search criteria value. For example, constraints for minimum value, maximum value, or maximum string length are not validated when you enter the search criteria value.

If the property mapping includes a fixed value property in an IBM Content Manager OnDemand repository, the defined fixed value is the only valid value for the search criteria. Because you cannot enter any other value, the fixed value is provided read-only in the search criteria. If the fixed value does not intersect with any valid values for the other type in the mapping, when you click search or save, an error is displayed, and you must correct the mapping.