[DevExpress Support Team: CLONED FROM T299654: Web - RangeFilter does not work as expected when client API is used]
Hi Paul,
It appears like it was our fault. (holds head down in shame) It was a config issue that we found to be a problem that was masking us from seeing your solution fix work. We did however find that there is a difference in 15.7 and the version you sent to us. The difference is in when the dashboard loads the xml up to parse and the table names contain upper case letters. With the 15.7 version regardless of the tablename case it was able to find the appropriate table and bind to it. With in the 15.7.+ version if the casing between the tables is different won't find and load the data. Thus the dashboards not loading any data.
We were able to fix the table names on our side, and thus confirm the range control is working as expected. We will upgrade our solutions to the version you've sent. Thank you for your help, time, patience with this issue!
Table names' case is not taken into account while MySQL database schema is loaded
Answers approved by DevExpress Support
We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.
Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.
With v15.1.8, Dashboards taken into account Table names' case while MySQL database schema is loaded
- v15.2.4Download Official Update
- v15.1.8Download Official Update