How to handle field merges?

[mattbloomfield]

Question

I recently tried to update a site to Craft5 from Craft4 - as part of the process I wanted to merge some fields.

I used the craft fields/auto-merge command that Craft5 offers, but in the process I decimated the data in the Vizy fields that used those fields.

How should I be thinking about merging fields in Vizy? Is there a safe way to do this?

Additional context

No response

[engram-design]

This is a great point, in that we need to look at hooking into the merge process, and update the field handles in vizy content. This is done in normal circumstances where you modify a field handle whose content existing in a Vizy block.

This actually fires for every fields' add/update/delete process in project config, so I would have thought it be handled already, but not tested it specifically.

[mattbloomfield]

Yeah, I'm not sure why it doesn't pick up the changes but it doesn't seem to be working. In my git changes I see this, for example. We have a "Quote" block in Vizy that relies on hte "quoteText" field. These are the associated changes.

Field:

Vizy (no change):

Migration:

I would expect to see changes here, but seeing nothing. The old ID (9d83c597-21a6-4fbc-847f-81d339998570) is still there, which then seems to get wiped in the DB as well (if I look at the elements_sites table):