I did some tests. I believe you are right that there’s a bug, but for the wrong reasons.
First, my philosophy would be (or I expected it to be):
- Do not use part table for pricing
-
Make a “base price” price list and assign it to all customers always
a. This goes in Customer Maintenance > Billing > Price Lists
b. Or, to simplify it, just assign it to customer groups instead (Price Lists tab)
c. Point is, you can make them expire and still retain the old data - you can’t do that with the part table -
Then assign discount lists in a hierarchy
a. This goes in Customer Maintenance > Billing > Discount Price Lists
b. Part discounts at the top
c. Product group percentage discounts on the next row
In reality, we don’t do #3 where I work - it’s a flat percent. But I’m saying if we did it your way (which is perfectly reasonable).
But I tried this, and it only half worked.
I made part 10017 have
- Base price list (“unit” type) = $10.00 each
- Discount PART list = $6.49 each
- Discount PRODUCT GROUP list = 25% off
I assigned the base list as the customer’s “price list” and the others as their “discount price lists.”
I used Price List Inquiry and entered the following:
And it came up with $10 each, not 6.49 as I expected and wanted:
But when I look at its logic, it’s right: $10 base…
…And $6.49 discount price (and no prod grp discount):
So why won’t it use the $6.49?