With this event you can stop the loading process of a new configuration.

 

It is implemented in the Configuration Check routine which checks whether a (new) configuration already exists when saving it.

 
Example

If you would like to set a new price for the old configuration that is loaded, you can trigger this event.

The event is located before the data load for the "Overview" block.

If you use it, you can e.g. now prevent the price, price list, description and new item code fields from being taken over from the "old" configuration by using BeasScript (in the file "prd_links2.src"). The script must end with "return failure".