Use both UpperBound and LowerBound elements to construct between range filter queries.
A between range filter query returns records with a standard or managed attribute value of type numeric that falls between a lower bound (the LowerBound element) and an upper bound (the UpperBound element).
Between range filters must be inclusive. Therefore, the Inclusive attribute for both bound elements must be set to true, as shown in the example below.
<cs:Request xmlns="http://www.endeca.com/MDEX/conversation/1/0"> <cs:State/> <cs:Operator xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="RangeFilterOperator"> <cs:RangeFilter AttributeName="Price"> <cs:LowerBound Inclusive="true">100</cs:LowerBound> <cs:UpperBound Inclusive="true">250</cs:UpperBound> </cs:RangeFilter> </cs:Operator> <cs:ContentElementConfig xsi:type="RecordListConfig" HandlerFunction="RecordListHandler" HandlerNamespace="http://www.endeca.com/MDEX/conversation/1/0" Id="RecordList" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" /> </cs:Request>
This example returns all bicycles whose price is between $100 and $250. Because both bound elements are inclusive, the returned records include bicycles that cost $100 and $250.