Intersoft Community - Crosslight - How to Use Crosslight with CompositeFilterDescriptor On Strings and Nulls?

How to Use Crosslight with CompositeFilterDescriptor On Strings and Nulls?

Arief — Wed, 19 Aug 2015 10:23:02 GMT

Hi Jimmy,

You can uses ToQueryString which you can find in here:
http://developer.intersoftsolutions.com/display/crosslight/OData+Support+Using+Query+Descriptor

It can convert QueryDescriptor to ODataQuery automatically including it's qualifier.

Here is my example i have String in my Search Parameter:
string adasd = this.QueryDescriptor.ToQueryString<SearchParameter> ();

this is the result:
$filter=(startswith(PropertyType, 'Apartment') eq true and startswith(SubArea, '') eq true and startswith(Apartment, '') eq true and startswith(Area, '') eq true and startswith(City, '') eq true and startswith(Price, '') eq true and Bedroom eq 0)

hope that'll helps!

How to Use Crosslight with CompositeFilterDescriptor On Strings and Nulls?

jtungol@silentpartnersoft.com — Tue, 18 Aug 2015 11:36:27 GMT

So there are specific FilterOperators used for strings or nulls. Okay, I guess that answers the question then. But what about for dates... are there specific filter operators for them too? Where can I find these information where it can tell us which operators to use for which data types. We did used FilterOperator.IsEqualTo and FilterOperator.IsNotEqualTo for some strings or nulls because it should filter specifically equal values. Using starts with or ends with operators will also validate other records that we don't want to de displayed (e.g. if we want results for 'John', we only need records for John and not records for Johnny, Johnson, etc). Using starts with operator will basically include those records that we don't need, correct me if I'm wrong.

So yes, we did add qualifiers to values being passed to a FilterDescriptor to conform to OData specifications when using strings. That leads to my question of how to properly use those filter descriptors. That being said, we need to find guides in doing so because this section the sample was comment out. Anyway, we hope you can give us more information about this.

Thanks!

How to Use Crosslight with CompositeFilterDescriptor On Strings and Nulls?

Arief — Tue, 18 Aug 2015 04:07:27 GMT

Hi Jimmy,

Just confirmation, you want to pass the string qualifier, so when it' converted to OData specifications, it will be treated as is. You want to tell the server that you are sending String value, is this right?

As far as i knows and uses, usually we use specific filterdescriptor for string and null, For null there are FilterOperator.IsNullOrEmpty and for string usually we use FilterOperator.StartsWith

I'm not sure about why you need to pass the qualifier except to conform ODATA specification, because we already could specifiy the value and type of get from inside the controller using WebAPI

How to Use Crosslight with CompositeFilterDescriptor On Strings and Nulls?

jtungol@silentpartnersoft.com — Mon, 17 Aug 2015 23:30:36 GMT

Hi,

We've looked at Dynamic Data Access with Query Descriptor, and we didn't find any filter that use strings or nulls, it's all numbers. Now, the reason why we noticed this is when using a FilterDescriptor with a string value or null, Crosslight converts string values without a valid qualifier, which violates OData specifications. The same is true when you specify null as a value, the result of the assigned value is blank. Now in order to workaround this, we needed to add quotes (') as qualifiers for strings (e.g. "'Beverages'") and pass a null value as string (e.g. "null"), instead of the actual null object. Surely the samples from your documentation will work because numbers when converted to OData specifications will be treated as is, but this is not the case for strings, dates, etc.

Is this how we should do this with Crosslight or is there a proper way of doing it that we might be missing? Please advise.