OnLookUp trigger - OnValidate trigger
Luc_VanDyck
Member, Moderator, Administrator Posts: 3,633
I noticed that, when programming an OnLookUp trigger for a field in a table, Navision Attain executes the OnValidate trigger of the same field afterwards.
Before (NF 2.60, NF 2.01, ...), the OnValidate trigger was never executed, when the OnLookUp trigger was fired.
Can someone confirm this behaviour?
Before (NF 2.60, NF 2.01, ...), the OnValidate trigger was never executed, when the OnLookUp trigger was fired.
Can someone confirm this behaviour?
No support using PM or e-mail - Please use this forum. BC TechDays 2024: 13 & 14 June 2024, Antwerp (Belgium)
0
Comments
-
That's right.0
-
Don’t program a lookup in the lookup trigger in a table. Program it in a function in a table witch you call from the onlookup trigger in a form field. Just be sure you fill the Text variable and the expected Boolean. Now Navision will not automatically validate. And you won’t see the difference between a programmed or a standard lookup.
Greetz,
Emiel Romein
The Netherlands"Real programmers don't comment their code.
If it was hard to write, it should be hard to understand."0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.8K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 328 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions