cms 2.1.3 — Update released for Drupal core (2.1.3)! drupal 10.5.11 — Update released for Drupal core (10.5.11)! drupal 11.3.11 — Update released for Drupal core (11.3.11)! drupal 11.2.13 — Update released for Drupal core (11.2.13)! drupal 10.6.10 — Update released for Drupal core (10.6.10)! cms 2.1.2 — Update released for Drupal core (2.1.2)! drupal 11.1.10 — Update released for Drupal core (11.1.10)! drupal 10.5.10 — Update released for Drupal core (10.5.10)! drupal 10.4.10 — Update released for Drupal core (10.4.10)! drupal 11.2.12 — Update released for Drupal core (11.2.12)! drupal 11.3.10 — Update released for Drupal core (11.3.10)! drupal 10.6.9 — Update released for Drupal core (10.6.9)! drupal 10.6.8 — Update released for Drupal core (10.6.8)! drupal 11.3.9 — Update released for Drupal core (11.3.9)! drupal 11.3.8 — Update released for Drupal core (11.3.8)! drupal 11.3.7 — Update released for Drupal core (11.3.7)! drupal 11.2.11 — Update released for Drupal core (11.2.11)! drupal 10.6.7 — Update released for Drupal core (10.6.7)! drupal 10.5.9 — Update released for Drupal core (10.5.9)! cms 2.1.1 — Update released for Drupal core (2.1.1)!

← All modules

migrate_process_negate

21 sites Security covered

View on drupal.org

This is a simple migrate process plugin whose only purpose is to negate whatever value is sent over to it.

This is useful for situations where we want to save the opposite of what the source is.

For example, if our source content has a bool value of is_deleted, which roughly translates to Drupal's status (published) field, we actually want the content to be unpublished (0 or FALSE) when the source is marked as deleted (1 or TRUE).

Then all we'd need to do is:

...
process:
  status:
    plugin: negate
    source: is_deleted
...

And it would work as expected.

Activity

Total releases

1

First release

Oct 2025

Latest release

7 months ago

Release cadence

—

Stability

100% stable

Releases

Version	Type	Release date
1.0.3	Stable	Oct 6, 2025