In the jsFiddle under the demos, we were inspecting the responses of the
/select requests when filters are being applied and we had some observations that we were not sure of. We’ve prepared a video and jsFiddle to show our observations:
Thank you for writing to us and for providing an example, video, and a screenshot.
We have carefully checked the reported behavior on our side. Indeed, in such a scenario the response contains extra data. It happens when several filters are applied together.
In your custom data source API implementation, there is no need to respond with data that does not meet the filter criteria.
Speaking of the error in the console, we will investigate this question and get back to you with the result of our research.
Please let us know if any other questions arise.
We will be glad to help you.
Our team has tested the behavior you described to see if the error appears on our side too.
Please find detailed info about our investigation below.
To simulate the custom data source API implementation, we specified the
url property of the
dataSource as a function, which returns responses depending on the request type and query.
Please see the following example: https://jsfiddle.net/flexmonster/ksfhjoa2/.
On 250-845 lines in the JS box, we coded the logic of responses to the
/select requests, namely:
The following steps have been tested via UI:
Getting to the point, please have a look at the code on 421-492 lines. The data in response meets filtering criteria. There is also a commented code of response that does not meet filtering criteria.
On our side, we have not noticed any errors in the console.
Please note that our team has also tested this example using the 2.8.20 version of Flexmonster.
Do not hesitate to contact us in case you have any questions regarding the example above.
Also, please let us know if you can modify the example to reproduce the issue or if the question is already solved.
Thank-you for providing a thorough investigation! We actually had a difficult time reproducing the error again on our side, but after some digging, we found a very peculiar way of reproducing it – we’ve prepared a new fiddle and video for convenience:
Thank you for researching the case further and for providing the video and the example.
The fix for the error is going to be provided with the minor update ETA 8 March.
We will notify you as soon as the version with the fix is available to download.
Do not hesitate to contact us if you have any questions.
We are pleased to inform you that the exception when setting conditional formatting with specific filters was fixed.
This is available in the 2.8.28 version of Flexmonster: https://www.flexmonster.com/release-notes/.
You are welcome to update the component.
Here is our updating to the latest version guide for assistance:
Please contact us in case any questions arise.
Thanks again to you and the team!
Our team would like to kindly take an interest in whether you updated to the latest version.
If so, could you please confirm that everything works as expected?
Looking forward to hearing from you.
Yes, we’ve updated to the latest version and have confirmed that the error no longer appears. Thanks much to you and the team!