Overview
MoveData executes in phases:
AccountContactCampaignRecurringDonation
This article describes how to disable a phase from executing. In this example we will focus on disabling the Recurring phase (so that an Opportunity record is created but not parented by a Recurring Donation) but note that the below logic is compatible in all phases of the execution.
Implementation
Disabling a Phase via Metadata
Related Article:
For information on how MoveData handles the registration of flows, please select your extension(s) from the following article:
Any metadata entry ending in *_DISABLE will disable that phase when entered into the MoveData Pipeline Metadata.
To disable the Recurring phase we created the following entry:
Disabling Recurring Donation Example
Labelis an explicit key used by MoveData to located the registered entry, and in this case, it will bePIPELINE_DONATION_RECURRING_DISABLEMoveData Pipeline Setting Nameis not consumed by MoveData and as such can be anything you likeSet
HandlertoTrueSort Orderis not requiredSet
TypetoConfig
Outcome
Below is an example of a before and after for disabling Recurring:
Before | After |
 |  |
From the execution log, we can see the Recurring phase has been skipped:
Skip Phase Execution Log