Known Issues/Limitations
The following are the known issues or limitations in Migration Tool:
• In SFM Transactions, the default Lookup Configuration flag is not migrated.
• Output Documents:
◦ If you are exporting to a file or importing from a file, associated checklists with Output Documents in the advanced option are not migrated.
◦ Images and documents referenced in Output Document templates are not migrated.
◦ Output Document is not migrated if the following conditions are true:
▪ The output document template associated with Output Document already exists in the target org.
▪ There is a mismatch between the source and the target org, concerning the child section name, count, or sequence.
• SFM Wizards:
◦ Newly created SFM Wizards in the target org are added to the layout configuration. However, the wizard display order is not in the same order as that of the source org. Newly created SFM Wizards are placed based on the available position in the target org.
◦ If a wizard has a step associated with an SFM Custom Action and the action refers to a VF page or an Apex class, those dependent items are not migrated.
◦ Wizard steps associated with SPRL Processes are not migrated.
• ServiceMax Configuration Profiles:
◦ The existence of any custom fields configured in any of the settings is not checked in target org, at any stage of validation or migration. This is also applicable to fields defined for DC Field updates and iPad settings.
• Translations defined using the ServiceMax Translation Workbench:
◦ All available translations are migrated for all supported languages.
◦ Any existing translation is overwritten.
◦ Translations for Wizard Step Description for all selected SFM Wizards and Description for Search Objects in all selected SFM searches are not migrated.
• SFM Expressions and Advanced Download Criteria:
◦ When an SFM Expression and an Advanced Download Criteria expression have the same name in the source org, the item migrated first is overwritten by the item migrated last to the target org.
• DC Views:
◦ Assignments for the selected DC Views are not migrated. It should be manually set in the target org for restricting them to specific service teams or territories.
• PM Process:
◦ The values for Assign To and Active fields are not migrated. They should be manually set in the target org after migration.
• Field Inventory configuration:
◦ Migration of metadata is not supported. Hence, if custom picklist values are created for the status field in product stock and are used for field inventory configuration, the tool does not migrate picklist values. It prompts the user with the message that Custom picklist values for the Status field in Product Stock Object are not migrated. Ensure that both source and target have the same picklist values.
◦ Any changes to the associated configuration profile are not migrated when this item is migrated as a dependent.
• The following are the characteristics of all the migrated configuration items:
◦ The existence of any referenced JavaScript code snippets, VF pages, and Field Sets is not checked in target org, at any stage of validation or migration.
◦ The history of migrations is not recorded in the target org against the individual migrated items, for a quick and intuitive reference. However, the details of each migration are captured in the ServiceMax Job record created in the target org and the completion status email sent to the target org user, to both of which a log file is attached.
◦ There is no option to save the list of items selected for migration, for future use.
• The overwrite scenario is not supported in the Field Inventory migration.
• Checklists:
◦ If you are exporting to a file or importing from a file, checklist processes that are part of SFM Wizards or SFM Mobile Permissions are not migrated.
◦ During checklist migration, if a question ID already exists in the target org and its type gets changed or overwritten because of migration from multiple orgs, then it might cause misconfiguration of the checklist if the question is linked with exit criteria or data validation rule. Consider the following scenarios:
▪ The same question is added to two different checklists in the target org and both checklists have data validation rule and exit criteria.
▪ One of the checklists is migrated from the source org, which successfully updates all configurations of the checklist in the target org.
▪ If the question type or the response type gets updated as part of the migration, then the same will reflect in another checklist where the same question ID is used. Exit criteria and data validation rules configured in the other checklist if any, l become invalid if it is based on the response type or question type.
To avoid this issue:
• Review the validation screen to see which question IDs will be overwritten and take appropriate action.
• ServiceMax recommends using the Checklist Import and Export option when you have multiple checklists for migration. The checklist import and export option allows you to manually edit the .csv files, wherein you can update the question IDs. This helps in avoiding misconfigurations.
OR
• Use the
New Checklist Designer. This issue does not occur for the new questions and checklists created through the New Checklist Designer.