Change Product Segmentation

Owned by Ondřej Tesař
Sept 30, 2024
2 min read

Technical Requirements for Bootstrapping

Detailed description of requirements can be found at Hierarchical Lookups | Configuration Of Bootstrapping.

Change Segmentation Check List

  1. These configurations need to be updated:

  2. Choose one of these two options:

    • Run “Price Setting Package - Upgrade” in PlatformManager Marketplace if you have the newest version of Accelerator. If you do not have the newest version, but you want to upgrade it anyway, follow Upgrade Steps (Price Setting).

    • Do it manually:

      • Deploy all Temporary Hooks. These are added to this page as attachments. You can change their folder, if you want new PPs to be created in another place.

      • Check for any changes in “CF_BuildPricingTables” in Accelerator repository, if there was any fixed bug.

      • Run logic named “CF_BuildPricingTables”. It can be done through CF or as a debug (with “Allow object modification” checked in).

  3. Clean up.

    • Remove Price Parameters which are not used anymore.

      • Price Parameters from old Dependency Configuration are not removed automatically.

      • There are a few restrictions on changing Dimensions, so always check if column names have been updated correctly. If the number of keys decreased and one of the keys moved to a previous position, then PP could become corrupted. Then it needs to be removed and added manually.

    • Add values to new Hierarchical Tables.

Troubleshooting

  • If you run bootstrapping during calculation, calculation is almost sure to fail. Most configurations are kept in cache for all products in PL/PG. Be sure to rerun after bootstrapping is finished.

  • If bootstrapping did not work properly for any reason, a bug should be reported. However, wrong generation of Hierarchical Price Parameters will damage the whole Accelerator. If you are going to fix any issues manually, before Accelerator Team can respond:

    • Make sure that you have the newest, not modified version of CF_BuildPricingTables.

    • Remember to deploy TemporaryHooks every time before you run bootstrapping.

    • Do not be afraid to run bootstrapping multiple times. The worst thing that can happen is that config is lost (which should be backed up anyway) or there are more leftover PPs on the partition (if the config is different every time).

    • Bootstrapping just creates Hierarchical Price Parameters (and removes Temporary Hooks). It can be done manually, but it will be time consuming. Config describing how data is read is in Price Parameters PriceSettingDimensions and DependencyConfiguration.