NAV2009 SP1 Wildcard * Filtering Issue

RoddyMcLean

I’ve found an issue filtering on fields as follows, there is a field in my table called RequisitionID: -

RequisitionID
100-100-1
100-100-2
200-100-1

Filtering using *1 should give a result set with 2 records, instead it returns 0 records. Testing on earlier version of NAV including plain old 2009 this returns 2 records (records 1 and 3)

Has anyone encountered this and is there a service pack/update to resolve?

Thanks
Roddy

Alex_Chow

You have to do *1*.

Very retarded, I know...

RoddyMcLean

Hi Alex,

Thanks for the reply, this will show all 3 records so it won't work for me.

I can't believe *1 does not work in 2009 SP1. Why would they do such a thing?

Roddy

Alex_Chow

according to some users, this is done for "performance" reasons.

Doesn't make any sense to me...

RoddyMcLean

Its worse than that, this is basic functionality that will break many modifications, *1 has always worked. Is it worth trawling partnersource for a service pack or is this official?

Thanks
Roddy

matteo_montanari

RoddyMcLean wrote:

Its worse than that, this is basic functionality that will break many modifications, *1 has always worked. Is it worth trawling partnersource for a service pack or is this official?

Thanks
Roddy

Hi

Look at this thread:

http://www.mibuso.com/forum/viewtopic.php?f=23&t=42460

Bye

Matteo

RoddyMcLean

This one is definitely not collation related, I have two databases one on 2009 and one on 2009 SP1 and the collation is identical. The only variable is Navision. However, *-1 appears to work for me. Annoying when an app that worked before stops working.

Thanks
Roddy

RoddyMcLean

Eto,

Your right. The two databases look like they have the same collation when viewed from NAVISION - file - database -alter. From SQL it is Latin1_General_CI_AS and Latin1_General_100_CI_AS. Latin1_General_CI_AS works fine.

Roddy