+1 (855) 920-2583
Login

How to change plan identification during PLM import from plan names to unique IDs

Modified on: Tue, 11 Feb 2025 7:03 AM

In version 3.0, Product Lifecycle Management (PLM) supports plan identification using unique IDs of the plans. Previously, identification was done using plan names.

The change of identification method is done by product line. To change it for plans based on a product line, complete the following steps:

Note: PLM must be updated to version 3.0 or later before completing these instructions.
  1. Access a workstation with access to the Kubernetes cluster, where your CloudBlue Commerce is deployed.
  2. Enter the OSS pod:
    kubectl exec -it oss-node-0 -n <namespace> -- /bin/bash
    Generic
  3. Switch to the build directory:
    cd build
    Generic
  4. Copy the export.py script to that directory.
  5. Identify the UUID of the product line whose plans you need to update.
  6. Run the script, replacing the sample UUID with one of your product line:
    python export.py --productLineUUID=87ccdca6-dd0c-4648-a38e-e8df1437c1f0
    Generic
  7. As a result, a message similar to the following will appear:

    Completed successfully; the export file saved as product_line_87ccdca6-dd0c-4648-a38e-e8df1437c1f0.csv
    Generic
  8. Configure IDs for the plans. Depending on the vendor, do this in one of the following ways:
    • For Microsoft 365 products, download and run the uid_generator.py script file that completes the UIDs automatically. Remember to replace the sample UUID in the file name with the UUID of your product line:
      uid_generator.py script - python uid_generator.py --product-line-csv product_line_87ccdca6-dd0c-4648-a38e-e8df1437c1f0.csv
      Generic
    • For other products, obtain the PPR file that contains plan UIDs and update the file generated in step 7, specifying the UID for each plan based on the data from the PPR.
    • For in-house products without a PPR file source, complete the PlanUID column in the file generated in step 7 with any unique values for each plan, for example, MPN.
  9. Copy the import.py script to the build directory on the OSS pod.
  10. Run the script replacing the UUID of the product line to the one of your product line:
    python import.py --productLineUUID=87ccdca6-dd0c-4648-a38e-e8df1437c1f0 --file=product_line_87ccdca6-dd0c-4648-a38e-e8df1437c1f0.csv
    Generic
  11. From this moment, plan identification during import will be performed using plan IDs.

3 Attachments (Scanned for viruses)

(4.91 KB)
Click here to download import.py Click here to download import.py
import.py is loading
(5.61 KB)
Click here to download export.py Click here to download export.py
export.py is loading
(1.38 KB)
Click here to download uid_generator.py Click here to download uid_generator.py
uid_generator.py is loading