Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.6K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 295 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Filtering on Customers
sabzam
Member Posts: 1,149
Dear All,
I am using Navision 5.1. For some strange reason whenever I filter on a customer no. which does not exist and remove all filters using the show all, the fitlers remain fixed onto the first customer and tries to re-create it. Has anyone ever encountered this issue?
Regards
I am using Navision 5.1. For some strange reason whenever I filter on a customer no. which does not exist and remove all filters using the show all, the fitlers remain fixed onto the first customer and tries to re-create it. Has anyone ever encountered this issue?
Regards
0
Comments
Often we find users applying field filters on the card form and the system will not release these filters from the tabular form. The filter must be release from the card from. From time to time, we have even had to go to the table filters via the card form and manually back out the filters in order to get the filter to release.
The filter is released from the card form and not form the list and this should be enough as the card filter supercedes that of the list. Still for some reason there still seems to be an issue with some filtering, which besides it's not the same number which was filtered before.
I found out that this error exists in the default objects. I have tried to find an official fix from Microsoft but could not find any. Has anyone ever met this issue before, and hopefully the solution?