-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Low
-
Component/s: Cloud to Cloud Migrations - Jira
-
None
-
1
-
Severity 2 - Major
Issue Summary
When a cloud-to-cloud migration is performed with translated locked custom fields, the migration fails if the destination has the same custom field as non-translated.
Steps to Reproduce
- Migrate the translated custom fields (locked) to destination with the same custom field in non translated form.
- Migration fails with error "Cannot find a locked custom field"
reason='Cannot find a locked custom field with name <non-english-language>
Expected Results
Migration should go through
Actual Results
Migration fails with the below exception is thrown
reason='Cannot find a locked custom field with name <non-english-language>
Workaround
A potential workaround is to modify the locked custom field name to the one present on the source site, contact-support for help