Consider the following guidelines before you start modernizing the MDM Hub objects:
•Based on the business application selected during project creation, the business entities are automatically assigned to that business application after modernization. However, the modernization process assigns search layouts only to business entities that contain fields that are enabled as searchable in the MDM Hub.
•Ensure that the picklist fields in business entities that you want to create automatically through smart field mapping are mapped to their corresponding lookup tables in the reference data mapping file.
•If the modernization process migrates any one of the business entities to MDM SaaS through smart field mapping, you can’t regenerate the mapping even if other business entities in the mapping aren't modernized.
•If you modernize business entities through smart mapping, you can add new fields or field groups to business entities only after the modernization.
•If any of the MDM Hub objects fail during modernization, you can skip them and continue modernizing other objects. However, you can't skip and continue when errors or failures occur when you standardize configurations or migrate data models.
•Ensure that you don’t delete the modernized objects in MDM SaaS. If you try to modernize the deleted objects again, the modernization process generates validation errors.
•When you modernize hierarchies and relationships, ensure that all business entities that the hierarchies use are included in a single modernization project.
•You can create a copy of an existing code list sheet and modify the sheet name and attributes to include the lookup tables that you want in the mapping file. However, manually creating code list sheets using this approach might introduce errors into the mapping file. Therefore, it is recommended to include the lookup tables when generating a mapping file if intend to create code lists for them in Reference 360.