Search filter on the "Row Label" and "Column Label" does not work if you enter whole word, but works OK if you don't enter first character of word. This happens regardless of case, at all levels of all dimensions in all the cubes created so far. (Apart from this problem, XMLAConnect is brilliant, working really well).
Example: We have a customer type "Internal Accounts". If we type "nternal" or "ccounts", in upper case or lower case or mixed case, the customer type is found, but if we type "Internal" or "Accounts" (any case) the customer type is not found.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Further experimentation shows this is the same problem as "Problem with searching in Excel's Filter Drop DownList" posted by Vladimir Cibulka on Wed Mar 23, 2016. The problem goes away if we ensure that all of our dimension caption columns are lower case only, which is consistent with the explanation already provided on that previous post.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have implemented the solution suggested in post "Problem with searching in Excel's Filter Drop DownList" by using reJ to alter the relevant bytecode in the mondrian jar file. Tested it over the last couple of days and it seems to be working well.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Experiencing issues where the search function in a label dropdown box only works when omitting the first character of the search term can be frustrating. This issue suggests there might be a bug or a limitation in the dropdown's search predovac functionality, possibly related to how the search algorithm or filtering mechanism is implemented.
Last edit: zamirmewelldy 2024-07-16
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This issue may arise from an off-by-one error in the code that processes user input, such as substring matching that starts at the second character instead of the first. It could also result from a debounce or delay function interfering with the initial keystroke. To resolve this, developers should inspect of cumming primary care the event listener tied to the search input and ensure that the full value of the string is being captured and compared properly from the very first character.
Last edit: jhone smith 2025-06-19
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Mondrian running on Jasper Server
Search filter on the "Row Label" and "Column Label" does not work if you enter whole word, but works OK if you don't enter first character of word. This happens regardless of case, at all levels of all dimensions in all the cubes created so far. (Apart from this problem, XMLAConnect is brilliant, working really well).
Example: We have a customer type "Internal Accounts". If we type "nternal" or "ccounts", in upper case or lower case or mixed case, the customer type is found, but if we type "Internal" or "Accounts" (any case) the customer type is not found.
Further experimentation shows this is the same problem as "Problem with searching in Excel's Filter Drop DownList" posted by Vladimir Cibulka on Wed Mar 23, 2016. The problem goes away if we ensure that all of our dimension caption columns are lower case only, which is consistent with the explanation already provided on that previous post.
I have implemented the solution suggested in post "Problem with searching in Excel's Filter Drop DownList" by using reJ to alter the relevant bytecode in the mondrian jar file. Tested it over the last couple of days and it seems to be working well.
Experiencing issues where the search function in a label dropdown box only works when omitting the first character of the search term can be frustrating. This issue suggests there might be a bug or a limitation in the dropdown's search predovac functionality, possibly related to how the search algorithm or filtering mechanism is implemented.
Last edit: zamirmewelldy 2024-07-16
This issue may arise from an off-by-one error in the code that processes user input, such as substring matching that starts at the second character instead of the first. It could also result from a debounce or delay function interfering with the initial keystroke. To resolve this, developers should inspect of cumming primary care the event listener tied to the search input and ensure that the full value of the string is being captured and compared properly from the very first character.
Last edit: jhone smith 2025-06-19