Price Setting Tips
- Jana Volencová (Deactivated)
- Jan Panoušek
Dos and Don’ts
Topic | Tip | Details |
|---|---|---|
Maximum LPG size | Do not put more than 1,000,000 records to an LPG, otherwise the performance for the user can be impacted. If you need a bigger LPG, then it is recommended to split it into two LPGs. | |
Storing prices in LPG | Do not store store historical, active and future prices as LPG items. It is good practice to have historical prices stored in Analytics, active prices in LPG and future prices in Price Lists. | |
Caution with mass actions and large LPGs | Do not use mass actions involving approval workflow for large LPGs (tens of thousands of items). It is extremely time consuming, especially when group approval is used. However, even for smaller LPGs this is not recommended. The design idea for LPG is to use auto-approval (or single step manual approval which does not generate the workflow overhead) for the majority (90% or more) of items. Having approval on each item (or the majority) is an anti-pattern. An alternative procedure be converting LPG to a Price List which can be approved as a single unit. |
Tips and Notes
Topic | Tip | Details |
|---|---|---|
PL header logic executed in Syntax Check | The price list/grid header logic is always executed in the Syntax Check mode, even for results calculation. As a consequence, some functions (e.g. | |
PL header logic does not behave like in Quotes | Price list header logic is not similar to a "header" logic of quotes. This header logic is executed completely separately from the price list calculation. i.e. it is NOT anyhow included in the process of recalculation of the price list (like it is in quotes). The price list header logic acts more as a dashboard, which sits on top of the price list detail page. | |
Deleting price lists is not immediate | The delete operation does not immediately remove all the line items and metadata associated with the Price List. A background job is run to wipe all these items and the whole process can take up to an hour. | |
Rounding of result price | In a Price List, the result price is rounded to 5 decimal places. If you want to have rounding/trimming of values under control, you need to do that before returning the value from logic. | |
When Last Updated/Created By fields are empty | The Last Updated By and Created By columns in the Price Lists table are intended for the current user to filter out only Price Lists updated/created by him/her. If the Price List was last updated or created by other user, the field is empty. | |
Last Updated/Created By fields in Manual Price Lists | The Last Updated By and Created By columns in the grid show the name of the user who last updated / created the Price List. However, if the user name changes, the existing records will still show the old user name. Changing individual line items in the Price List will not update the Last Updated By column value in the Manual Price Lists (header) table. |
Found an issue in documentation? Write to us.