If I create filter in header using #connector_text_filter, it can only filter one condition (like %value% by default), but sometimes only one condition is not enough. For example, there is a field “length” in one table, and I want to find the length in a specified range, then the client user must input two values, one is upper limit， the other is lower limit. To solve the problem above, I have to provide two text field to receive the data for filtering.
You can still use one field but use custom filtering code on server side.
You can use the beforeFilter server side event to convert filter value from clientside to some SQL code that will be used for actual data filtering.