Partial Import of Fulfillment Catalog Data - Use Case 4

The following is the fourth 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 and ProductB with project tags [P1 ]and [P1] respectively. The TagNames.csv file, which exists within the import zip file, has [P1]. Import the zip file to an existing enterprise that has data present in it.

Because [P1] exists in the TagNames.csv file, only the records with the project tag [P1] are added or modified to the Test enterprise.

Because ProductA exists in the PRODUCT_DATA.csv file with the project tag [P1], and ProductA also exists in the enterprise with the project tag [P2], it is loaded into the enterprise with the project tag [P1,P2].

Because ProductB exists in the PRODUCT_DATA.csv file with the project tag [P1], and ProductB does not exist in the enterprise, it is added to the Test enterprise with the project tag [P1].

Partial Import of Fulfillment Catalog Data - Use Case 4 Step 1

Step 2

The Import zip file has repository records (for example, PRODUCT repository records) named ProductB with the project tag [P1]. The TagNames.csv file, which exists within the import zip file, has [P1]. Import the zip file to an existing enterprise on which Step 1 is performed.

Because ProductA does not exist in the PRODUCT_DATA.csv file, and ProductA exists in the enterprise with the project tag [P1,P2], it is updated with the project tag [P2] and the project tag [P1] is be removed. If the ProductA existed in the enterprise, its project tag would have been modified or removed. The ProductB is loaded to the Test enterprise with the project tag [P1].

Partial Import of Fulfillment Catalog Data - Use Case 4 Step 2

Step 3

The Import zip file has repository records (for example, PRODUCT repository records) named ProductB and Product C with project tags [P1], [P1,P3]. The TagNames.csv file, which exists within the import zip file, has [P1]. Import the zip file to an existing enterprise on which Step 2 is performed.

Because ProductB exists in the PRODUCT_DATA.csv file with the project tag [P1], and ProductB also exists in the enterprise, it is loaded to the Test enterprise with the project tag [P1].

Because ProductC exists in the PRODUCT_DATA.csv file with the project tag [P1], and ProductC does not exist in the enterprise, it is loaded to the Test enterprise with the project tag [P1].

Partial Import of Fulfillment Catalog Data - Use Case 4 Step 3