Hi,
I am in the situation that I have two "half" migration scripts.
With one migration I can fill my terms and other fields. With the other migration I can fill specific module fields in the same node.
Right now when I run the first migration and then the second one I got two seperate double nodes
1) One half is filled with half of the fields
2) The second half is filled with the other fieds.

Is it possible to run a Migration and NOT let it overrule already filled fields?
Greetings, Martijn

Comments

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Murphysboro, IL, USA
CreditAttribution: mikeryan at Acquia commented
Status: Active » Postponed (maintainer needs more info)
Issue tags: -migrate

I'll ask the obvious question - why not have a single migration populate all the fields? If some of the fields have a different source, you can pull them into the source row being populated in prepareRow().

If you must have two migrations, see https://www.drupal.org/node/1117454 - your first migration, which creates the nodes, would be a normal migration. Your second migration, which updates specific fields, would use a system-of-record of DESTINATION.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Murphysboro, IL, USA
CreditAttribution: mikeryan at Acquia commented
Status: Postponed (maintainer needs more info) » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.