NAV Team: Few tips about filters usage in latest Dynamics NAV RTC builds - Dynamics CRM: Blogs

Blog bot · 25.11.2011, 16:27

I want to describe few tips about filters usage in Dynamics NAV RTC. This can be useful for users who worked with classic client and came to RTC.

In Dynamics NAV Classic Client we can construct filters in filters window using following operators:

.. Range

& And

| Or

< Less than

<= Less than or equal to

> Greater than

>= Greater than or equal to

<> Different from

* Forms a part of value

@ Case-insensitive

Let’s say for example we want to find item in item list ending with “Front” then can construct filter on description: *front

And we have results

Now try the same in RTC.
In RTC we have “Filter Pane” and we don’t need to call filter window. So here we just change filter field to description and ad the same filter value:*front

But ***Это спам-сообщение***, result is different:

It also includes items which starts with ‘front’ and even has ‘front’ in the middle of description.

What is wrong? Nothing, this is feature of RTC filters: whatever we add to this filter, it will be translated to string by adding ‘@’ in front and ‘*’ in end. So our filter string ‘*front’ becomes ‘@*front*’ and RTC filters for any description includes ‘front’ in upper or lower case.

We can see this transformation if open “About this page” filter section:

If we know this feature, then we can use it very smart: if we know how description starts, we just type begin of it without any filter operators and we have all description, which begins with this string, filtered. Fast work, is it?

But what to do if we really want to filter only descriptions which end with ‘front’. Then we have 2 options:
1. Use apostrophes for filter string for example enter “ ‘*front’ ” instead of “ *front ”, then RTC filter exactly on this string:

or
1. Expand Filter Pane and filter on exactly what we want:

That’s all what I want to say.

Ps. If you have question “why I filter on ‘front’, but results always includes ‘Front’”, then answer is: my db SQL collation is not cases sensitive, so SQL doesn’t see difference here and shows upper and lower case values.

These postings are provided "AS IS" with no warranties and confer no rights. You assume all risk for your use.

Gedas Busniauskas

Microsoft Lithuania
Microsoft Customer Service and Support (CSS) EMEA

Источник: http://feedproxy.google.com/~r/Micro...tc-builds.aspx