I'm seeing odd behaviour when I try to import products with entries in PricingLevel01, PricingLevel02 etc. This is using an Excel CSV.
If I enter L or D05 straight into the fields the data doesn't get written to the field. If I export the database to have a look at products where I have set up Customer pricing in QW I see there is a lot of white space around the L or D05 data. If I replicate that in the Excel file I can import it and the Customer Level pricing works.
I'm keen to use PricingLevels but this seems a bit random and I'm not really filled with much confidence. Can anyone explain what is going on and how I might make this a bit more robust?
Best Answer
B
Brian Laufer
said
over 6 years ago
If you are just using the PricingLevelXX.Amount Field and the PriceModifier of "C" and still running into issues, I would ask that you contact QuoteWerks Technical Support directly and they will be able to assist you further.
The PricingLevel01 field should only be used when importing from fields exported from QuoteWerks. It is actually several fields combined into one which is why the "spacing" exists. You will need to use the &PricingLevel01.Amount Field (see below). Additional details on Importing can be found in our helpfile: https://www.quotewerks.com/helpfile/qwhelp.htm?tipsonimportingandmappingfields.htm
If you have additional questions, please feel free to contact Technical Support directly.
I
Iain Shaw
said
over 6 years ago
Thank you. That works beautifully although there seems to be a slight anomaly. If I map to the &PricingLevel01.Amount field the import wizard insists that the Price Modifier be set to V not C. When I do that it works. When I bring the item into the Document Items grid the Price Modifier shows as C.
Brian Laufer
said
over 6 years ago
The PricingLevelXX fields are intended for Volume or Customer Based pricing. What are you trying to accomplish by using these fields if not using customer or volume based pricing?
I'm using them for Customer Based pricing but when I tried to run the import wizard with C as the Price Modifier it rejected it and said I had to use V. It seemed odd behaviour.
Brian Laufer
said
over 6 years ago
Answer
If you are just using the PricingLevelXX.Amount Field and the PriceModifier of "C" and still running into issues, I would ask that you contact QuoteWerks Technical Support directly and they will be able to assist you further.
Iain Shaw
I'm seeing odd behaviour when I try to import products with entries in PricingLevel01, PricingLevel02 etc. This is using an Excel CSV.
If I enter L or D05 straight into the fields the data doesn't get written to the field. If I export the database to have a look at products where I have set up Customer pricing in QW I see there is a lot of white space around the L or D05 data. If I replicate that in the Excel file I can import it and the Customer Level pricing works.
I'm keen to use PricingLevels but this seems a bit random and I'm not really filled with much confidence. Can anyone explain what is going on and how I might make this a bit more robust?
If you are just using the PricingLevelXX.Amount Field and the PriceModifier of "C" and still running into issues, I would ask that you contact QuoteWerks Technical Support directly and they will be able to assist you further.
Additional Reference Information: https://www.quotewerks.com/kbase/showArticle.asp?articleid=5303
QuoteWerks Technical Support: https://www.quotewerks.com/support.asp
- Oldest First
- Popular
- Newest First
Sorted by Oldest FirstBrian Laufer
Iain,
The PricingLevel01 field should only be used when importing from fields exported from QuoteWerks. It is actually several fields combined into one which is why the "spacing" exists. You will need to use the &PricingLevel01.Amount Field (see below). Additional details on Importing can be found in our helpfile: https://www.quotewerks.com/helpfile/qwhelp.htm?tipsonimportingandmappingfields.htm
If you have additional questions, please feel free to contact Technical Support directly.
Iain Shaw
Thank you. That works beautifully although there seems to be a slight anomaly. If I map to the &PricingLevel01.Amount field the import wizard insists that the Price Modifier be set to V not C. When I do that it works. When I bring the item into the Document Items grid the Price Modifier shows as C.
Brian Laufer
The PricingLevelXX fields are intended for Volume or Customer Based pricing. What are you trying to accomplish by using these fields if not using customer or volume based pricing?
QuoteWerks Pricing Methods: https://www.quotewerks.com/helpfile/qwhelp.htm?itempricingmethodandrelatedfields.htm
Iain Shaw
I'm using them for Customer Based pricing but when I tried to run the import wizard with C as the Price Modifier it rejected it and said I had to use V. It seemed odd behaviour.
Brian Laufer
If you are just using the PricingLevelXX.Amount Field and the PriceModifier of "C" and still running into issues, I would ask that you contact QuoteWerks Technical Support directly and they will be able to assist you further.
Additional Reference Information: https://www.quotewerks.com/kbase/showArticle.asp?articleid=5303
QuoteWerks Technical Support: https://www.quotewerks.com/support.asp
Iain Shaw
All good Brian thank you. I can't replicate the issue.
-
Product upload via excel options
-
Product Import Wizard
-
Importing a price list with marked-up price
-
Import Quote Headers
-
Populate configurator data on backend
-
New product import template
-
Product Export prices have | instead of decimal
-
Price Update
-
import - recurring
See all 17 topics