Issue:
When using the config migration tool, it points to the wrong schema. The dropdown does not have a whole list of schemas to choose from, it's only this incorrect one or the ignore option. If this schema is ignored then the migration doesn't work.
Environment:
Config Migration tool
Cause:
In the backend, there are provenance URIs that are the unique IDs that config migration creates to map two objects during a migration. This is the ID that is then used to remember what objects map to each other in later migrations. If objects evolve into different things across tenants, sometimes these mappings need to be redone to achieve the desired outcome. These IDs cannot be changed via the UI, but Benchling support can remove these IDs so that you can correctly map the migration to the schema of your choosing.
Resolution Steps:
- Reach out to Benchling support with the API ID of the object (schema, dropdown, template) that you would like to be 'unmapped'. This is likely the schema that the config migration tool is wanting to update.
- Benchling support will remove this provenance URI/unique backend ID so that you can try the config migration again and choose the correct object mapping.