How to change plan identification during PLM import from plan names to unique IDs
Modified on: Tue, 11 Feb 2025 7:03 AMIn 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.
- Access a workstation with access to the Kubernetes cluster, where your CloudBlue Commerce is deployed.
- Enter the OSS pod:
- Switch to the build directory:
- Copy the export.py script to that directory.
- Identify the UUID of the product line whose plans you need to update.
- Run the script, replacing the sample UUID with one of your product line:
-
As a result, a message similar to the following will appear:
- 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:
- 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.
- Copy the import.py script to the build directory on the OSS pod.
- Run the script replacing the UUID of the product line to the one of your product line:
- From this moment, plan identification during import will be performed using plan IDs.