Manage Price Lists Growth

Why

Unless explicitly archived or deleted, the set of price lists (PL) in a PFX instance will grow over time. Also, a PL line item can be quite a heavy object in the underlying database. Hence any search requests for PL prices within a logic can get slower over time.

When to Use

Given that PLs generally get overridden by newer versions, the current active set of PL line items is generally not so big in comparison with the overridden ones.

On one project, in order to improve the performance of the logic, a Data Logic job was put in place to ‘maintain’ an Analytics table with the current set of ‘active’ prices coming out of PLs. The benefit is that this Analytics table has less items than the total of all PL line items. Then the logic can call Analytics to get the current active price without the need to query the PLs.

Another approach could be to store the active Analytics prices within a Price Parameters table. The goal is again not to have to query the PL data directly.

Found an issue in documentation? Write to us.