Strange behavior in SETFILTER

Egnaz wrote:

I wanted to use a simple SETFILTER like this SETFILTER("No.",'%1*',MyNo)

MS KB 951233 wrote:

SYMPTOMS
Consider the following scenario. You use the C/AL command SETFILTER in Microsoft Dynamics NAV 4.0. The filter includes a wildcard character and a field replacement. For example, the wildcard character is an asterisk or a question mark. In this scenario, the filter may not be applied correctly.
CAUSE
This problem occurs because Microsoft Dynamics NAV 4.0 cannot handle wildcard characters when it applies a filter and must perform a field replacement action in the filter.
WORKAROUND
To work around this problem, separate the field replacements into a different step. For example, you use the following command:

Rec.SETFILTER("No.",'%1*','100');

Note You can use %N as a field replacement. N represents a number.

Microsoft Dynamics NAV 4.0 replaces %1 with 100. Therefore, the command resembles the following command:

Rec.SETFILTER("No.",'100*');

If you change the C/AL code to have specific filters as in this example, the SETFILTER command works as expected.

To avoid the problem that is described in the "Symptoms" section, make sure that you do not combine field replacements (%) with wildcard characters. If you must use such a combination, convert the filter into a string. Then, use the string as the filter instead.

For example, you use the following command:

Item.SETFILTER("No.",'%1*','100');

Change the command to use the string as follows:

TempString := STRSUBSTNO('%1*','100');
Item.SETFILTER("No.",TempString);