Partial Import of Fulfillment Catalog Data - Use Case 9
The following is the ninth 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,P3] exists in the TagNames.csv file, only the records with the project tags [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,P2,P3]. Import the zip file to an enterprise on which Step 1 has been performed.
[P4], [P5], and [P6] does not exist in the TagNames.csv file and such project tags 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 enterprise with the project tag [P1,P2], the import process removes the project tag [P1,P2] from ProductA. Because there is no project tag for ProductA, it is deleted.
Because ProductB exists in the PRODUCT_DATA.csv file without the project tag [P2,P3], and ProductB exists in the enterprise with the project tag [P2,P3], the import process removes the project tag [P2,P3] from ProductB. Because there is no project tag for ProductB, it is deleted.
Because ProductC exists in the PRODUCT_DATA.csv file without the project tag [P3,P1], and ProductC exists in the enterprise with the project tag [P3,P1], the import process removes the project tag [P3,P1] from ProductC. Because there is no project tag for ProductC, it is deleted.
