I have a client that uses Serenic Dynamics NAV and for which I am developing various JetReports. In data fields such as project or country, @NONE is used when the value is otherwise blank where no project or field has been assigned to the data record. When using the NL function, JetReports does not include any data where @NONE is the field value. Wildcard parameters don't end up including @NONE. Anyone encountered this elsewhere and know of a solution or workaround?
Gary
Date
Votes
1 comment
-
Jet Reports Historic Posts Hi Gary,
This is interesting because the '@' character is a special filtering character in NAV, so making it part of a value like that is probably not advisable, particularly at the beginning of the value. When you filter in NAV, @ at the beginning of a filter means to make the filter case insensitive. So if the database had the values 'Bob' and 'BOB' in a text field and you specified a filter of @bob, you would get both Bob and BOB as results (whereas without the @, you would get neither one). Note that text fields are case sensitive whereas code fields are not.
Therefore in Jet in your case, filtering for @NONE is getting passed to NAV and NAV is interpretting the @ symbol as a special filter character to ignore case rather than as part of the filter string. In Jet, you could try surrounding the filter with single quotes (therefore, it would be "'@NONE'"). Single quotes generally tell Jet that this is a literal value and that special characters like @ are part of the value. The real question is whether that will work in NAV itself when Jet passes the filter to NAV. If you open the NAV classic client and open the table from the object designer and try filtering that field to get the @NONE values, you should be able to tell whether this will work or not. Whatever works there should also work in Jet.
Regards,
Hughes
Please sign in to leave a comment.