Partial Import of Fulfillment Catalog Data - Use Case 10
The following is the tenth use case for the Partial Import feature of Fulfillment Catalog:
Step 1
The import zip file has repository records (for example, PRODUCT repository records) named ProductA, ProductB, and ProductC with the project tags [P1,P2], [P2,P3], and [P3,P1] respectively. The TagNames.csv file, which exists within the import zip file, has [P1,P2,P3]. Import the zip file to a Clean or New Enterprise.
Because [P1], [P2], and [P3] exist in the TagNames.csv file, only the records having the project tag [P1], [P2] or [P3] are added or modified to the Test enterprise.
Step 2
The import zip file has repository records (for example, PRODUCT repository records) named ProductA, ProductB, and ProductC with the project tags [P4], [P5], and [P6] respectively. The TagNames.csv file, which exists within the import zip file, has [P1,P6]. Import the zip file to an enterprise on which Step 1 is performed.
Because [P1,P6] exists in the TagNames.csv file, only the records that have the project tag [P1] or [P6] are added or modified to the Test enterprise.
Because [P4,P5] does not exist in the TagNames.csv file, the records that have the project tag [P4] or [P5] are not added to the Test enterprise.
Because ProductA exists in the PRODUCT_DATA.csv file without the project tag [P1,P2], and ProductA exists in the TagNames.csv file with the project tag [P1,P6], ProductA is added to the Test enterprise without the project tag [P1].
Because ProductB exists in the PRODUCT_DATA.csv file with the project tag [P5], and the TagNames.csv file has [P1,P6], ProductB is not imported into the Test enterprise.
Because ProductC exists in the PRODUCT_DATA.csv file without the project tag [P3,P1], and the TagNames.csv file has [P1,P6], ProductC is added to the Test enterprise with the project tag [P6] and without the project tag [P1].
