To modernize the MDM Hub objects, you need to use the standardized configuration of the mapped files that you upload. The modernization process standardizes the configuration details into multiple JSON files.
To comply with the field property limits for business entity fields in MDM SaaS, the modernization process verifies field configurations of the MDM Hub business entities during standardization. The modernization process counts how many fields have properties like searchable, facetable, and auto-suggest, enabled in both MDM Hub and MDM SaaS. If the count exceeds the allowed limits, you can't continue until you disable enough field properties to meet the limits. For example, if 30 fields are searchable but the limit is 20, you must disable the searchable property for 10 fields before you proceed.
Consider the following guidelines when you modify the field properties of a business entity:
•If business entity fields in the MDM Hub are mapped to predefined business entity fields in MDM SaaS with their field properties enabled, the modernization process applies the field properties, such as searchable and facetable, of MDM SaaS during standardization.
•If business entity fields in the MDM Hub are mapped to custom business entity fields in MDM SaaS with their field properties enabled, the modernization process applies the field configurations, such as searchable and facetable, of the MDM Hub during standardization.
•If base object columns in the MDM Hub are mapped to predefined or custom business entity fields in MDM SaaS, the modernization process applies the field properties, such as searchable and facetable, of MDM SaaS during standardization. Base object columns don't support field properties, such as searchable and facetable.
•After standardization, you can view the field properties of business entities that are ready for modernization. The business entities that exceeded the defined field property limits are highlighted in red. To stay within limits and proceed to the next step, disable the properties for some fields of the affected business entities.
•You can't disable a field property of a business entity field that has dependent objects unless you remove the dependency.