Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 270 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
Options
Lookup not working in RTC
DKFFox
Member Posts: 12
I have a problem with a table lookup in RTC. One table has several fields which lookup to other tables, most of these work but there are two that just do nothing when clicked and I have no idea why.
The story is like this:
Originally these fields were using coded lookups which worked fine.
In order to bring them in line with Nav standards I removed the coded lookups and added a table relation to the main table and made sure the LookupFormID is defined in the tables being looked up. I compiled everything and everything worked fine.
Next I realised I had missed two fields so I made the same changes for these and recompiled, and these are the two lookups that don't work any more. Not sure if it is a coincidence but it seems that Nav has made some decisions deep down that it doesn't want to change.
These two fields now can't be looked up from anywhere, even if I create a new table with a new field linked to the Run Type table it still refuses to lookup. ](*,)
Any ideas?
Fyi, none of the fields being looked up are key fields - though I will try that and see if it makes any difference. The fields doing the looking have ValidateTableRelation and TestTableRelation set to No.
The story is like this:
Originally these fields were using coded lookups which worked fine.
In order to bring them in line with Nav standards I removed the coded lookups and added a table relation to the main table and made sure the LookupFormID is defined in the tables being looked up. I compiled everything and everything worked fine.
Next I realised I had missed two fields so I made the same changes for these and recompiled, and these are the two lookups that don't work any more. Not sure if it is a coincidence but it seems that Nav has made some decisions deep down that it doesn't want to change.
These two fields now can't be looked up from anywhere, even if I create a new table with a new field linked to the Run Type table it still refuses to lookup. ](*,)
Any ideas?
Fyi, none of the fields being looked up are key fields - though I will try that and see if it makes any difference. The fields doing the looking have ValidateTableRelation and TestTableRelation set to No.
0
Comments
remove all code including any local variables and try..
-Mohana
http://mohana-dynamicsnav.blogspot.in/
https://www.facebook.com/MohanaDynamicsNav
But the good news is that I have fixed the problem. All I had to do was delete the fields and recreate them from scratch. The new fields have exactly the same properties as the old ones, including the field numbers, except that they work - if in doubt wipe it out. Go figure.
So as I suspected Nav is remembering something somewhere and not letting it go.
btw I created test forms in classic and had the same problem/solution in there.
http://www.epimatic.com