Developer forum

You should be able to get the information from the priceviewmodel:

https://doc.dynamicweb.dev/api/Dynamicweb.Ecommerce.ProductCatalog.PriceViewModel.html

That is the result of the calculated price in the context - for this user, at this time, in this currency etc.

But you cannot get the valid from and to - as that is a condition in this case and not part of the priceviewmodel. To get that information out you would need some coding in the template.

Hello Nicolai,

- I do understand its the result of the calculated price in a context, but since it returns one price, then should it be possible include the valid from + valid to + quantity from that price. That must be a minor change for you to include this ;-)

That would make it so much easier to provide these details in a feed (out-of-the-box) and in many cases could it also be a great helper, when trying to find the exact price that have been returned if also the PriceId as returned.

Br. Michael Knudsen

Hello Nicolai,

- I have found that there are actually 'Quantity' (and UnitId) on <Prices> using the XML feed provider so can't this be expanded to include 'valid from' and 'valid to'?
And are your statement "feed quantity would always be 1" still valid?

Br. Michael Knudsen

On the calculated price

For the calculated price on a product, quantity is always 1 in a feed. Quantity only varies in a cart context.

On the Prices loop (quantity prices)

This loop is different. It holds the prices that could apply in the cart right now — i.e. the prices that would come into effect if you changed only the quantity or unit (as happens when adding the product to the cart). It's essentially the set of currently-applicable price tiers.

We can add the ValidFrom / ValidTo dates to the view model, but it's worth being clear that they behave differently from the other properties (Quantity and UnitId):

• Quantity and UnitId describe variations you can still reach — change the quantity or pick a different unit, and that tier's price applies.
• The dates would not work that way. The loop only ever contains prices whose date range includes today, because the prices are resolved at calculation time (now). A price that was valid in the past, or only becomes valid in the future, can never be triggered by adding the product to the cart today — so it isn't in the list at all.

In other words: adding the date fields lets you display the validity window of the currently-active prices, but it does not let you browse past or future prices. Only prices valid as of today are ever included.

If your goal is to list past or future prices, we need to do something else - because that would be a behavior we cannot change without compatibility issues.

Hello Nicolai, 

- and thanks for the detailed explanation. My goal isn't to list past or future prices, but it's actually to show the valid from / valid to date range for the price.

Should I created it as a feature request on GitHub?

For the calculated price, the XML could look like this:

For the price loop, the XML could look like this:

PS.  if I need a price in the past or in the furture, I have to adjust the date in the feed or in the url (&Time).

Br. Michael Knudsen