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
- 298 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
Erratic Behavior when Partially Entering Text in a Field
JosephGress
Member Posts: 36
In NAV, you can enter partial text in a field with a table relation and NAV will automatically complete the text with the closest match from the underlying table.
Does anyone know how the user can set a filter on the field so that NAV will exclude some values from the underlying table when it searches for the closest match?
For example, our client is entering Payroll Control Codes in the Time Journal Line table. They report that they used to be able to type in "INCEN" and NAV would complete this with "INCENTIVE BONUS" which is what they want. However, when they enter "INCEN" this week, NAV selects "INCENTIVE AMT" which is not what they want.
It makes sense that NAV selects "INCENTIVE AMT" since that comes before "INCENTIVE BONUS". However, my client reports that "It didn't work that way last week. Make it work the way it did last week."
I suspect that somehow my client had a filter set on Payroll Control Codes that excluded "INCENTIVE AMT" and that that filter was removed inadvertently last week. However, I cannot figure out any way of "making it work the way it did last week".
Can anyone help me be a hero to my client?
Does anyone know how the user can set a filter on the field so that NAV will exclude some values from the underlying table when it searches for the closest match?
For example, our client is entering Payroll Control Codes in the Time Journal Line table. They report that they used to be able to type in "INCEN" and NAV would complete this with "INCENTIVE BONUS" which is what they want. However, when they enter "INCEN" this week, NAV selects "INCENTIVE AMT" which is not what they want.
It makes sense that NAV selects "INCENTIVE AMT" since that comes before "INCENTIVE BONUS". However, my client reports that "It didn't work that way last week. Make it work the way it did last week."
I suspect that somehow my client had a filter set on Payroll Control Codes that excluded "INCENTIVE AMT" and that that filter was removed inadvertently last week. However, I cannot figure out any way of "making it work the way it did last week".
Can anyone help me be a hero to my client?
Joseph Gress
0
Comments
Regarding "Did "INCENTIVE AMT" exist previously?", Yes, it did. I verified this in an older backup. And, I verified this with the user.
Regarding Jannestig's comment regarding sorting, are you referring to changing the primary key for the table? I don't think that anyone changed the primary key. When I look at the keys, I don't see any that would make INCENTIVE BONUS come before INCENTIVE AMT unless they select to "Sort Descending".
For what it's worthg, someone did change the length of an unrelated field last week. That could have caused the user to lose a filter or sort in their zup file. I just can't figure out how to get any filters or sorts to work they way that the user reports that they worked last week.