Track an Event / Trigger when we click a Navigation button..
vipinkuruvilla
Posts: 143
Hai,
I have written validation for some fields in the onquerycloseform event(). It validates when we try to close the form.
However if I navigate to another records and from there if I try to close the form, it does not validate the previous record and closes the form. The previous record gets saved without validating the fields.
Can anyone let me know how to track this when I clcik on the navigation button??
Thanks in advance.........
Vipin...
I have written validation for some fields in the onquerycloseform event(). It validates when we try to close the form.
However if I navigate to another records and from there if I try to close the form, it does not validate the previous record and closes the form. The previous record gets saved without validating the fields.
Can anyone let me know how to track this when I clcik on the navigation button??
Thanks in advance.........
Vipin...
0
Comments
-
you can try with on OnFindRecord-trigger or the OnNextRecord-trigger.
But in this case you also will have to program them to also handle the navigating.
In general it is very difficult to do that kind of validation. It is best (=easiest) to validate the record when a user wants to use it.
For example when creating a customer-record, you can automatically block the record and when the user wants to un-block it, you can test your fields.Regards,Alain Krikilion
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!0 -
Kriki,
I had put some code in the triggers which u have mentioned. But even the break point didnt get activated in those trigger when I clicked the navigation button......
Kindly advice....0 -
You might try to use OnAfterGetCurrentRecord, but remember you MAY NOT HAVE AN ERROR HERE, otherwise the form closes.vipinkuruvilla wrote:Kriki,
I had put some code in the triggers which u have mentioned. But even the break point didnt get activated in those trigger when I clicked the navigation button......
Kindly advice....
But like I already said:In general it is very difficult to do that kind of validation. It is best (=easiest) to validate the record when a user wants to use it.
For example when creating a customer-record, you can automatically block the record and when the user wants to un-block it, you can test your fields.Regards,Alain Krikilion
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!0
Categories
- All Categories
- 75 General
- 75 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
- 611 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 253 Dynamics CRM
- 103 Dynamics GP
- 6 Dynamics SL
- 1.5K Other
- 991 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 28 Design Patterns (General & Best Practices)
- Architectural Patterns
- 9 Design Patterns
- 4 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1K General Chat
- 1.6K Website
- 77 Testing
- 1.2K Download section
- 23 How Tos section
- 249 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions