Howdy, Stranger!
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
- 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
- 310 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
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
OnModify executed twice when exiting page with DelayedInsert enabled
Vhite
Member Posts: 8
Hello,
I have a problem with a page where DelayedInsert is enabled.
When modifying a record and then exiting the page, the OnModify trigger of the table is executed twice even though an error is thrown in this trigger (the data modified in the record leads to this error).
This surprises me as I would expect that the error thrown in the first run of the OnModify trigger would halt all further execution of code.
I'm sure the error is thrown the first time, as I have debugged the code.
The situation can be duplicated as follows:
1) Create a page where the property DelayedInsert is enabled
2) In the OnModify of the SourceTable of the created page, make sure an error is thrown. To visualize the double execution of the OnModify trigger you can add a MESSAGE before the ERROR.
3) Modify a record in the page and then close the page (press the X on the top right).
4) You will see the message before the error twice and then NAV will tell that there are unsaved changes and the page and ask if you want to discard these changes.
We are using Dynamics NAV 2017, version 10.0.24745.0
What causes this double execution of the OnModify trigger and how can I prevent this for occuring?
Kind regards.
I have a problem with a page where DelayedInsert is enabled.
When modifying a record and then exiting the page, the OnModify trigger of the table is executed twice even though an error is thrown in this trigger (the data modified in the record leads to this error).
This surprises me as I would expect that the error thrown in the first run of the OnModify trigger would halt all further execution of code.
I'm sure the error is thrown the first time, as I have debugged the code.
The situation can be duplicated as follows:
1) Create a page where the property DelayedInsert is enabled
2) In the OnModify of the SourceTable of the created page, make sure an error is thrown. To visualize the double execution of the OnModify trigger you can add a MESSAGE before the ERROR.
3) Modify a record in the page and then close the page (press the X on the top right).
4) You will see the message before the error twice and then NAV will tell that there are unsaved changes and the page and ask if you want to discard these changes.
We are using Dynamics NAV 2017, version 10.0.24745.0
What causes this double execution of the OnModify trigger and how can I prevent this for occuring?
Kind regards.
0