2023.1: Set source for Data migration in Deployment package screen

Similar to the Creation screen, we would like to be able to use the ‘Set source for data migration and upgrade’ task in the Deployment package screen and then decide to Continue creation or Review mapping:

Currently there is no way to see and/or determine which Source branch and model version are going to be used in the Deployment package. One has to navigate to Model overview > Branches > Form to figure out the setting, and if incorrect, navigate to Data migration and execute the ‘Set source for data migration and upgrade’ task. 

Following up on the conversation with @Mark Jongeling in this topic as well as the conversation with @Ester and @Anne Buit at the Thinkwise office, I believe it adds value to

1. At least be able to see which Source branch and model version will be used in the Deployment package
2. Be able to set which Source branch and model version will be used in the Deployment package

We often perform incremental upgrades on our DEV/TEST environment using the Creation tasks/APIs, but for our Production deployments always use the Deployment package. As such the Source branch / model version always needs to be set before creating a Deployment package.

Note: one might argue that this situation does not apply if the practices for the MAIN branch as explained in this Thinkwise blog are followed. But currently such a setup is not feasible for us, among others due to the lack of proper Data migration support in the merging process.