Share
Report
811On each listpage in ax 2012 there is the "quick filter" field on the right top of the listpage, just above the grid section.
The problem here is, when a user enters a search word, ax applies wildcards in backgroud - you have no control over it.
Eg, you search for a user by name and you enter "Bob Hope". Ax will search using "*Bob Hope*" and in sql it becomes "And name like '%Bob Hope%'.
Anyone who knows a little bit about sql knows that putting a wildcard in front of a search is a killer for performance. It even has as a result that even if you would have an index on that field, the index is not used because of the wildcard in front.
In our case, one of our clients has more than 2.000.000 customers in its system and when searching for a customer using the quick filter, it takes forever to find results. But when using the same search term using the right click "filter by field" the results are found instant.
It is pretty hard to explain to our client why he should not be using this quickfilter, "why is there when we can't use it"?
So my question is: can anyone tell me why this is was designed like this AND, even better, if we can tweak this behaviour. (I took a trace, but can't find a tweak-point, it seems like a part of this behaviour is handled in kernel code).
Thanks for your reply!
Kr,
Sven
*This post is locked for comments
All responses (
Answers (
