![]() ![]() ![]() Unfortunately, when you change the Price Method in GP the value in the Price field for the existing Price Level does not remain the same, it will zero out (if done manually in GP) or reflect the value in the Percent field (if updated through SQL). This worked out as we wanted to change the current Price List Items to reflect Currency Amount as well. Thus we could not have the DISCOUNT level which had a method of % of List Price and our NEW level with a method of Currency Amount. The first thing we came across was that for each Price List Item the corresponding Price Levels all had to share the same Price Method. This pushed us to have to make the change via the third party application, Scribe, as a change to the price method through the native import tool is not available. The caveat was that the current price method used for existing Price Levels (we will call ‘GENERAL’ and ‘DISCOUNT’) was ‘% of List Price’ and the client wished to track these Price List Items as ‘Currency Amount’. The goal was to add existing inventory items to a newly created Price Level which we will call ‘NEW’ for the purpose of this article. I recently worked on a project to work with Price List Items in GP, a platform which traditionally is not my forte.
0 Comments
Leave a Reply. |