What Parameters Can Be Changed Safely (Price Setting)

This page tells you what parameters can be changed afterwards without redoing deployment or configuration.

Here is some general advice on how to handle configuration Price Parameters:

• All configurations work based on column names (UI name) and/or column labels/metadata (technical names). 
  They do not work based on column labels (UI name) or labelTranslation (technical name). 

• Do not change the name of any configuration PP column. It might be especially tempting in “DependencyConfiguration” PP, but don’t do it.

• Column names of sample data can be freely changed assuming that the configuration will be properly adjusted.

• Values of dynamically created Price Parameters can be changed without redeployment. They act as standard Pricefx Price Parameters. The full list can be found here. Values can be added/removed as needed. If the user wants to handle all products without fallback to another DependencyLevel, we recommend to have one value with an asterisk "*" on every key. It provides a fallback without leaving the scope of the current Dependency Level configuration.

• Changing dynamically created Price Parameters requires caution, but can be done according to this guide.

• PriceSettingConfig and other configuration PPs should be changed with extreme caution. Technically every configuration can be changed during the system run but changes can affect a lot of things. That is why you should be careful here and customers are not even recommended to do this on their own in PROD environments without testing changes on some QA instance.

• Making changes to price setting levels is tricky. See Adjustments after Changing the PP PriceSettingLevel.