Skip to main content Skip to complementary content

Deleting invalid fields from a Data Stewardship campaign

This scenario aims at helping you set up and use connectors in a pipeline. You are advised to adapt it to your environment and use case.

Before you begin

  • A task has been assigned to the data steward, that is fixing customer data with empty emails, but some emails were not found.
  • You have the Campaign owner role that allows you to display and retrieve the campaign in Talend Cloud Pipeline Designer. See this documentation for more information.


  1. Click Add pipeline on the Pipelines page. Your new pipeline opens.
  2. Give the pipeline a meaningful name.


    Delete unsolved emails from Stewardship campaign
  3. Click ADD SOURCE and go the Campaigns tab to retrieve the Resolution campaign that contains empty email fields.
    You can see that the campaign task retrieved contains the tag NOT_SOLVED which means the empty emails were not fixed by the data steward.
  4. Click the ADD DESTINATION item and go the Campaigns tab to select the same Resolution campaign in which you want to delete the fields with empty emails.
  5. Give a meaningful name to the destination; delete all records with empty emails for example.
  6. In the Configuration tab of the destination, click Main:
    1. Select Delete in the Action list to delete the email data from the campaign.
    2. Enter TDS_ID in the Input field of task ID field as it is the task identifier.
    3. Click SAVE to save your configuration.
  7. On the top toolbar of Talend Cloud Pipeline Designer, click the Run button to open the panel allowing you to select your run profile.
  8. Select your run profile in the list (for more information, see Run profiles), then click Run to run your pipeline.


Your pipeline is being executed, the customer records containing emails that could not be found are deleted from the Stewardship campaign.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!