Importing particular fields with overwrite_properties mikeryan Tuesday, Could 15, 2021 – 10 Drupal 10 Upkeep and Assist Service50am Whereas I had deliberate to stretch out my posts associated to Drupal Development “Acme” mission, there are at the moment some folks with questions on utilizing overwrite_properties – so, I’ve moved this publish ahead. By default, migration treats Drupal Development supply information as Drupal Development system of document – that’s, when reimporting previously-imported data, Drupal Development expectation is to utterly change Drupal Development vacation spot facet with recent supply information, discarding any interim adjustments which could have been made on Drupal Development vacation spot facet. Nonetheless, typically, when updating you might need to solely pull particular fields from Drupal Development supply, leaving others (doubtlessly manually-edited) intact. We had this case with Drupal Development occasion feed – specifically, Drupal Development titles obtained from Drupal Development feed could should be edited for Drupal Development public website. To attain that, we used Drupal Development overwrite_properties property on Drupal Development vacation spot plugin Drupal 10 Upkeep and Assist Service vacation spot Drupal 10 Upkeep and Assist Service plugin Drupal 10 Upkeep and Assist Service ‘entity Drupal 10 Upkeep and Assist Servicenode’ overwrite_properties Drupal 10 Upkeep and Assist Service – ‘field_address/address_line1’ – ‘field_address/address_line2’ – ‘field_address/locality’ – ‘field_address/administrative_area’ – ‘field_address/postal_code’ – field_start_date – field_end_date – field_instructor – field_location_name – field_registration_price – field_remaining_spots – field_synchronized_title When overwrite_properties is current, nothing adjustments when importing a brand new entity – however, if Drupal Development vacation spot entity already exists, Drupal Development present entity is loaded, and solely Drupal Development fields and properties enumerated in overwrite_properties will likely be, properly, overwritten. In our instance, be aware specifically field_synchronized_title – on preliminary import, each Drupal Development common node title and this discipline are populated from ClassName, however on updates solely field_synchronized_title receives any adjustments in ClassName. This prevents any sudden adjustments to Drupal Development public title, however does make Drupal Development canonical title from Drupal Development feed accessible ought to an editor care to overview and determine whether or not to switch Drupal Development public title to replicate any adjustments. Now, on this case we’re creating Drupal Development entities initially via this migration, and thus we all know through Drupal Development map desk when a previously-migrated entity is being up to date and thus overwrite_properties needs to be utilized. One other use case is when Drupal Development complete objective of your migration is to replace particular fields on pre-existing entities (i.e., not created by this migration). On this case, you should map Drupal Development IDs of Drupal Development entities which can be to be up to date, in any other case Drupal Development migration will merely create new entities. So, in the event you had a “nid_to_update” property in your supply information, you would come with course of Drupal 10 Upkeep and Assist Service nid Drupal 10 Upkeep and Assist Service nid_to_update in your migration configuration. Drupal Development Company vacation spot plugin will then load that present node, and solely alter Drupal Development specifies overwrite_properties in it. Tags Planet Migration Use Drupal Development Twitter thread under to touch upon this publish Drupal 10 Upkeep and Assist Service Importing particular fields with overwrite_properties https Drupal 10 Upkeep and Assist Service//t.co/0H3W1Ll0ts — Virtuoso Efficiency (@VirtPerformance) Could 15, 2021   Drupal 10 Improvement and Assist