E
egarcia
Guest
Hello Peggy, Thank you for your feedback. The JSDO processes the filter expressions from the Kendo UI DataSource using the JSON Filter Pattern (JFP) if mappingType=JFP has been specified in the Business Entity. The mapping for the "contains" operator is done using INDEX instead of CONTAINS so that it can be used with any character field, not only those with a Word Index. The suggestion from Mike is possible. You could change the code in _convertToABLWhereString() to use CONTAINS instead of INDEX. This would also allow you to use operators such as ^ and | rather than using them as the literal characters. Do you expect to be able to use these operators? Another alternative, would be to use a custom mappingType where you get the raw JSON filter on the server and process it on the Business Entities. Please let me know if you would like to know more about this approach. I think that in a future version, we could enable the usage of CONTAINS (instead of INDEX) by identifying the fields in the catalog as supporting Word Index (wordIndex=true). I will add a story to our backlog to look into this for a future version. Thank you and regards, Edsel
Continue reading...
Continue reading...