If I have an entity where I have overridden a particular value, that value will not hold the next time a migration is run if the field I set isn't included in the source. For example if I have an entity with a 'phone' field and I select that as an override field and assign it a value of '555-555-5555'. If I then run a migration and do not pass 'phone' as a field in the requested xml, the phone field is added as an empty destination. The migration code then sets all empty destinations to be NULL. If a field is set as a migration override it should probably be removed as an empty destination so we hold on to whatever value was originally set and not replace it with NULL.
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | interdiff.3040654.6-8.txt | 4.34 KB | mikelutz |
| #8 | 3040654-8.migrate_override.Overridden-fields-set-to-NULL-if-not-present-in-source.patch | 5.82 KB | mikelutz |
| #8 | 3040654-7.TEST_ONLY.patch | 3.23 KB | mikelutz |
Comments
Comment #2
mikelutzStarter patch. Needs tests
Comment #3
mikelutzComment #4
AngryWookie commentedWrote test that will fail before this issue is fixed.
Comment #5
mikelutzShould be 'entities.node.test_type.fields.field_test_missing'
Missing blank line before function
Missing blank line after function
Comment #6
mikelutzTest patch
Comment #8
mikelutzComment #11
mikelutzComment #12
mikelutzComment #15
mikelutz