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
- 302 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
Disable Event Subscribers
jordi79
Member Posts: 275
Hi,
We are using NAV2017. We are facing some performance issues which is traced to Workflow subscriber events. Is there a way to disable Event Subscribers apart from making modifications directly into the Event Subscriber codeunit?
Jordi
We are using NAV2017. We are facing some performance issues which is traced to Workflow subscriber events. Is there a way to disable Event Subscribers apart from making modifications directly into the Event Subscriber codeunit?
Jordi
0
Comments
The page is non editable, and the table this page refers to is a virtual table. There is no way to turn it off on this page. At least in NAV2017 this is not possible.
I understand. I am not turning off events, but I am disabling the subscriptions to these events. As some of these subscriptions to these evetns are causing performance issues. E.g. in workflow, when a GenJnlLine is deleted, it performs a check on a table. Imagine, if 50,000 lines are posted in GenJnlLine, this check is done 50,000 times. And not to mention, if there is a subscription, (I think...) it also disables the SQL bulk delete feature, and delete is sent to SQL sequentially 50,000 times.