Posted on 29/12/2023 10:51:16
Hi Tomislav
That setting belongs to the old product catalog 'for template tags' and is based on prices in the database. That is not very visible in the UI, I agree. If the product have a price in the database, but the price is calculated to 0 in NAV after the products have been retrieved from database, you will see this behavior.
If you are using product catalog 'for viewmodel' - it can only run on top of a lucene query, so if products needs to be left out of the list, it has to be in the index - and that means personalized prices that are calculated when shown, cannot be taken into consideration. So if the product never has a price for any user, it should be indexed with price 0 and those products can be removed using an expression in the query. But if the product has a price and removed when calculated, it cannot be removed in the query.
If only some users have a price of 0 and that means they cannot buy it, you need to find another solution. Just hiding them when rendering the product list will break paging on lists with many products so is usually a bad solution. Alternative is to remove the price and add to cart button but still display the product. Yet another alternative is to use assortments that can remove products from users that are not allowed to buy a given product.
