There's a bug in BV 5.5.

I was recently trying to create dynamic categories for some of my product types..

MinPrice - MaxPrice
0 - 0.99 - Dynamic category works...
1 - 1.49 - Fails to find products... (but 1 - 1.50 works)
1.50 - 2.00 - Dynamic category works...
2.00 - 2.49 - Fails...

The problem is that running an equivalent query against the DB resulted in several 100's of products for each of those ranges... So I decided to dig in.

It turns out that it's a data type issue with "bvc_Product_ByCriteria_s" stored procedure... It does not properly define the scale/precision for decimal parameters. Consequently, the min/max prices are truncated/rounded to a single digit which means I was effectively searching for products between 1.00 and 1.00.

Not sure if this has been addressed or fixed in 5.6, but those interested might want to fix that stored procedure.

Before:
...
@MinPrice decimal = NULL,
@MaxPrice decimal = NULL,
...

After:
...
@MinPrice decimal(18,10) = NULL,
@MaxPrice decimal(18,10) = NULL,
...

Hopefully this isn't against the rules, or in the wrong section...