[Nav2013] Missing trigger "OnAfterInput"

peterchenpan
Member Posts: 2
Hello everyone.
At first of all I am new in Navision in general. I am missing a trigger which was very useful in 2009 but to be disappeared in 2013. My issue is to catch an input before it is validated because it is maybe necessary to filter and modify it – otherwise I will get an error by handling the input. In 2009 I used the trigger “OnAfterInput” but unluckily I am missing this trigger (it was set on forms) and cannot reproduce it just with pages and actions in Navision 2013.
The trigger „OnValidation“ reacts to late; there will be thrown an error in case of an invalid input without filtering or modifying. I need an option to react right after the input and right before the validation.
I would be very thankful for any advice or maybe better any kinds of solution. Thank you very much for your effort.
With best regards,
Patrick
At first of all I am new in Navision in general. I am missing a trigger which was very useful in 2009 but to be disappeared in 2013. My issue is to catch an input before it is validated because it is maybe necessary to filter and modify it – otherwise I will get an error by handling the input. In 2009 I used the trigger “OnAfterInput” but unluckily I am missing this trigger (it was set on forms) and cannot reproduce it just with pages and actions in Navision 2013.
The trigger „OnValidation“ reacts to late; there will be thrown an error in case of an invalid input without filtering or modifying. I need an option to react right after the input and right before the validation.
I would be very thankful for any advice or maybe better any kinds of solution. Thank you very much for your effort.
With best regards,
Patrick
0
Answers
-
There is also no "OnAfterInput" trigger in NAV2009 pages, just for information.
I think this is technical because of 3-tier architecture.0 -
I can expect performance issue with this trigger.0
-
You need to rethink your implementation, i guess i want to enter any kind of value in a input field, then do something with it without checking it's datatype, relation validation etc. Well that can be achieved very simply by using a text variable as SourceExpr instead of the real field you would set. This way you can use the OnValidate() Trigger and do what you want and after you do your processing you can still call a validate to the table field.
In fact that is the only and the right way to achieve something like this. If you are moving from classic client to Role Tailord Client you will find many such small changes where you're forced to rethink your implementation. Thinking outside the box is the key!0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K 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
- 320 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