Partial Import of Fulfillment Catalog Data - Use Case 6
The following is the sixth 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], [P1], and [P2] respectively. The TagNames.csv file, which exists within the import zip file, has [P1,P2]. Import the zip file to a Clean or New enterprise.
Because [P1,P2] exists in the TagNames.csv file, only the records that have the project tag [P1] or [P2] are added or modified to the Test enterprise.
Because the import is performed on a Clean or New enterprise, ProductA, ProductB, and ProductC are loaded to the Test enterprise with the project tags [P1], [P1], and [P2] respectively.
Step 2
The Import zip file has repository records (for example, PRODUCT repository records) named ProductA, ProductB, and ProductC with the project taga [P1,P2], [P1], and [P2] respectively. The TagNames.csv file, which exists within the import zip file, has [P1]. Import the zip file into an enterprise on which Step 1 is performed.
Because [P1] exists in the TagNames.csv file, only the records that have the project tage [P1] are added or modified to the Test enterprise.
Because ProductA and ProductB exists in the PRODUCT_DATA.csv file with the project tag [P1,P2] and [P1] respectively, and ProductA and ProductB also exists in the enterprise with the project tag [P1], they are loaded to the enterprise without any changes to the project tags.
Because ProductC has the project tag [P2], and ProductC also exists in the enterprise with the project tag [P2], it is not loaded to the enterprise as the project tag did not match the exported project tag [P1].
