Partial Import of Fulfillment Catalog Data - Use Case 1
The following is the first 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 with the project tag [P1,P2]. 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 are tagged with [P1,P2] are added or modified to the Test enterprise.
Because ProductA does not exist in the enterprise, but exists in the PRODUCT_DATA.csv file with the project tag [P1,P2], it is added to the Test enterprise with the project tag [P1,P2].
Step 2
The import zip file has repository records (for example, PRODUCT repository records) named ProductA and ProductB with project tags as [P1,P2] and [P1] respectively. The TagNames.csv file, which exists within the import zip file, has [ P1 ]. Import the zip file to an enterprise on which Step 1 is performed.
Because [P1] is present in the TagNames.csv file, only the records that are tagged with [P1] are added or modified to the Test enterprise.
Because ProductB does not exist in the enterprise, but exists in the PRODUCT_DATA.csv file, ProductB, with the project tag [P1], is loaded to the Test enterprise.
Because ProductA exists in the enterprise with the project tag [P1], and exists in the PRODUCT_DATA.csv file with the project tag [P1], it is loaded to the enterprise with no modifications to the project tag.
