Developer forum

Forum » Development » Price range facet: MaximumValue not working as expected

Price range facet: MaximumValue not working as expected

E-mail notifications
Martin Gammelholm
Martin Gammelholm
Reply
Posted on 29/08/2023 14:22:10

Hello!

I have set up a price range filter and want to get the maximum price for the slider. However, as soon as the query is applied the tag is updated to reflect the current productlist and not the productlist without the query, which I would expect.

Here the most expensive product costs 25406,25:
https://elma.dw9.1stweb-staging.net/produkter?Search=protimeter

As soon as the price filter is added, the MaximumValue is changed to 2887, but I would expect the tag to stay at 25406.
https://elma.dw9.1stweb-staging.net/produkter?Search=protimeter&PriceWithVatRangeMin=925&PriceWithVatRangeMax=3000

Is this intended or a bug?

If it is intended, how can we get the max value of a product rendered, even tho the price filter is added?

 

image_(6).png

Replies

 
Martin Gammelholm
Martin Gammelholm
Posted on 01/09/2023 08:56:02
Reply

Bump :)

 
Steffen Kruse Hansen Dynamicweb Employee
Steffen Kruse Hansen
Posted on 01/09/2023 12:39:18
Reply
This post has been marked as an answer

Hi Martin,

Yes, normally this is intended, so you only see the options which is relevant for the current list of product. There is a setting available on the Product Catalog, where you can define if you want to see options, which is not part of the current result, which could maybe fix this issue.



But it would affect all facets, so you might need to do something extra in the template to remove all the unneeded options

I hope it helps you.

Best regards,

Steffen

Votes for this answer: 1
 
Martin Gammelholm
Martin Gammelholm
Posted on 04/09/2023 07:57:00
Reply

Hi Steffen,

Thanks for the reply! :)

I know about this option, but I don't think this is the right way to go around the issue. I would rather like the maximum value tag to show the value of the product with the highest price in the list, no matter the price filter.

 
Tomas Gomez
Posted on 04/09/2023 14:19:42
Reply

Hi Martin,

Maybe you're looking for this parameter: facet.MaximumFacetValue
See more info at https://doc.dynamicweb.com/forum/development/development/range-price-facet

Regards,
Tomas

 
Thomas Larsen
Posted on 06/09/2023 09:24:19
Reply

Tomas - That is the parameters that we are using - The issue is that the values is not correct

Steffen 
I know that facet options is limited to only showing options that i relevant for the current list, to avoid a no products found result.

But none the less, if we on a normal facet, select one facet options, the list of possible facet options is not limited to the current list of products. And i will mean that the range filter min and max parameteres should do the same.

BR
Thomas

 
Martin Gammelholm
Martin Gammelholm
Posted on 12/09/2023 09:05:41
Reply

Bump :)

 
Kasper Legarth
Posted on 05/10/2023 00:15:33
Reply

Bump :)

 
Steffen Kruse Hansen Dynamicweb Employee
Steffen Kruse Hansen
Posted on 24/10/2023 11:07:48
Reply

Hi Martin,

I think you should be able to make it work by chaning the implementation a little, so instead of having two parameters per range, you should have only one, and use the "Between" parameter.

So your setup should look something like this:

Parameters:

 

Expression:

Then when you select something in your range filter, the result in the querystring should look like this http://r4.local.dynamicweb.dk/e-bikes/classic-e-bikes?PageSize=12&SortBy=&PriceRangeMin=1199,8225

If done like this, my tests have shown that the facet will keep all the values.

I hope it solves the issue

Best regards,

Steffen

 

You must be logged in to post in the forum