We have a new NAV deployment, and have our items with their initial pricing defined against Customer Groups in Item Card/Sales/Prices.
We are ready for new pricing for a range of products to kick in in a few weeks. So I am testing Data Migration to do this. The process I am following is:
Export Sales Price table
Change Pricing for each item
Enter Starting From date
Now all this seems to work pretty well, the new pricing is in there - however, once the Starting From date passes, the new pricing does not come into play - the existing pricing stays in effect.
All the original prices were entered without a start or end date - obviously it isn’t always known when a price will no longer apply. So I entered an end date against a price, and viola, the new price is used.
So my question is about the price selection logic. It appears to be:
“Use the price that has a price starting date less than today, unless there is a record with a blank starting date, then use that”
Whereas I would expect that a price record that has a starting date takes precedence over one that doesn’t - ie “use the price that has a starting date less than today, unless there isn’t one, then use a price record with a blank starting date”
In other words a blank starting date “wins”. If this is the case, then I can’t see a straightforward way to manage the pricing - each time there is a change, we can simply add the new prices, but we will have to go bakc to each record individually and add an ending date to the existing pricing.
Is there a better way to do this?