Problem/Motivation
There is no migration integration for this module.
Proposed resolution
Write the cck field migration class.
Remaining tasks
Patch
Test
Commit
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | migration_integration-2843684-2.patch | 1.31 KB | hussainweb |
There is no migration integration for this module.
Write the cck field migration class.
Patch
Test
Commit
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | migration_integration-2843684-2.patch | 1.31 KB | hussainweb |
Comments
Comment #2
hussainwebAdd migration upgrade support.
Comment #3
brooke_heaton commentedThis is helpful but could you provide the actual yml format example for how this mapping is handled in the migrate yml?
Comment #4
brooke_heaton commentedOk, so it's fairly intuitive, but as an example for First Name and Last Name fields, my process mapping in my migrate yml, which is working with this patch is:
'field_name/given': first_name
'field_name/family': last_name
so use the machine name of the field followed by the name sub-element
Comment #5
brooke_heaton commentedRBTC for me!
Comment #7
alan d. commentedThanks!
I am a bit green on the internals, but was successfully able to migrate name field data with the patch, so I'm assuming it works :)
Would have been best to test a true D7 name field to D8 name field (field_new_name: field_old_name) for testing, but open a followup issue if there are issues with that :P