To modernize the MDM Hub objects, upload your mapped files. The modernization process standardizes the uploaded configuration files into multiple JSON files.
During standardization, the modernization process validates the MDM Hub configuration against MDM SaaS limits and thresholds. For example, the total number of searchable fields across the MDM Hub and MDM SaaS for a business entity is checked against the allowed limit of 30 fields. If the count exceeds the allowed limit, you can't continue with the modernization process until you disable enough searchable fields to meet the limits. If 40 fields are searchable but the limit is 30, 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, the modernization process uses the properties of the fields in MDM SaaS.
•If business entity fields in the MDM Hub are mapped to custom business entity fields in MDM SaaS, the modernization process uses the properties of the field in the MDM Hub.
•If base object columns in the MDM Hub are mapped to predefined or custom business entity fields in MDM SaaS, the modernization process uses the properties of the fields in MDM SaaS. 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 of the fields in 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.