Skip to main content
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
ParthaSarathy
ParthaSarathyAccepted solution
Community Advisor
July 12, 2023

Hi @hariharanb ,

In the import workflow example provided by @aggabhi , ( https://experienceleague.adobe.com/docs/campaign-classic/using/automating-with-workflows/use-cases/data-management/recurring-import-workflow.html?lang=en )

 

Lets consider in data loading activity, you import a CSV file with 10 recipient data, where 7 records already exist in database and 3 are new records.

And in enrichment, linking the input data with recipient schema using a simple join and selecting 'Type 11 simple link which may have a non-existent target' and run the workflow.

 

You can see in the output transition, Primary key for those 7 recipients who already exists in database will have primary key value, whereas for other 3 new records primary key of recipients will be 0. These records are called 0 ID records as per the above documentation.

 

In few cases these records might automatically filtered. If you notice such scenario, to avoid that you can enable the checkbox 'disable automatic filtering of 0 ID records' 

 

~  ParthaSarathy S~  Click here to join ADOBE CAMPAIGN USER GROUP for Quarterly In-person | Hybrid | Virtual Meetups
View in thread

5 replies

aggabhi
Level 5
July 12, 2023

Hi @hariharanb ,

 

Disable automatic filtering of 0 ID records option to make sure records that have a primary key equal to 0 are not excluded.

 

https://experienceleague.adobe.com/docs/campaign-classic/using/automating-with-workflows/use-cases/data-management/recurring-import-workflow.html?lang=en

 

Regards

Abhishek

Translate
Adobe Employee
HariharanBAdobe EmployeeAuthor
Adobe Employee
July 12, 2023

Hi Abhishek,
This answers the use of that setting, but could you please explain what is the purpose of 0 id records? and why is a 0 id record added to recipients by default?

 

Regards,

Hari

Translate
aggabhi
Level 5
July 12, 2023

Thanks for your question.

Basically lets say you have two tables one is recipient and other id country table and recipient table is joined by country table by n:1 cardinality and country code is foreign key in same table.

 

Now there can be case when country is not populated for some recipients and that is case they have no value in foreign key of same table leading to zero id records.

 

These records are called zero id records.

 

Regards

Abhishek

Translate
    ParthaSarathy
    Community Advisor
    ParthaSarathyCommunity AdvisorAccepted solution
    Community Advisor
    July 12, 2023

    Hi @hariharanb ,

    In the import workflow example provided by @aggabhi , ( https://experienceleague.adobe.com/docs/campaign-classic/using/automating-with-workflows/use-cases/data-management/recurring-import-workflow.html?lang=en )

     

    Lets consider in data loading activity, you import a CSV file with 10 recipient data, where 7 records already exist in database and 3 are new records.

    And in enrichment, linking the input data with recipient schema using a simple join and selecting 'Type 11 simple link which may have a non-existent target' and run the workflow.

     

    You can see in the output transition, Primary key for those 7 recipients who already exists in database will have primary key value, whereas for other 3 new records primary key of recipients will be 0. These records are called 0 ID records as per the above documentation.

     

    In few cases these records might automatically filtered. If you notice such scenario, to avoid that you can enable the checkbox 'disable automatic filtering of 0 ID records' 

     

    Translate
    ~  ParthaSarathy S~  Click here to join ADOBE CAMPAIGN USER GROUP for Quarterly In-person | Hybrid | Virtual Meetups
      Adobe Employee
      HariharanBAdobe EmployeeAuthor
      Adobe Employee
      July 12, 2023

      thank you to both of you @parthasarathy and @aggabhi for the answers.

      Translate
      Terms & ConditionsAccessibility statement

      Loading footer...