In this workflow, a particular use case is failing. In the event that we need to add a new field through customisation and at the same time create a Patch to set values to this new field for old data, the update fails. This is because the Patch is run before the new field is created on migrate.

Should we consider to edit the update workflow? Or there is a proper way to deal with this usecase?

Note: Quick fix is to separate the Patch and do update first for customisation to take effect and add the patch later on. But this is not practical at all times.