Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 262 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 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
Options
Global variables in a single instance codeunit
norseny
Member Posts: 19
Hi experts 
I am wondering if there are any recommendations about using global variables in single instance codeunits in Business Central/NAV. Generally, in modern object oriented programming defining and using global variables should be avoided at all costs.
Are there any official guidelines for BC?
Here is an example where it is really tempting to use single instance codeunit global variables: I am using two subscribers - OnValidate Qty on Warehouse Receipt Line (1) and OnValidate Qty on Purchase Line (2).
(1) should update values on both Warehouse Receipt Line and on Purchase Line.
(2) should update only values on Purchase Line.
The problem is that when I call (1), it triggers my code in subscriber (2) - I don't want to do that. I don't have a handled boolean here in parameters, as those are standard OnValidate triggers.
What is the best approach? Is using single instance codeunit global variables a no-go here?
I am wondering if there are any recommendations about using global variables in single instance codeunits in Business Central/NAV. Generally, in modern object oriented programming defining and using global variables should be avoided at all costs.
Are there any official guidelines for BC?
Here is an example where it is really tempting to use single instance codeunit global variables: I am using two subscribers - OnValidate Qty on Warehouse Receipt Line (1) and OnValidate Qty on Purchase Line (2).
(1) should update values on both Warehouse Receipt Line and on Purchase Line.
(2) should update only values on Purchase Line.
The problem is that when I call (1), it triggers my code in subscriber (2) - I don't want to do that. I don't have a handled boolean here in parameters, as those are standard OnValidate triggers.
What is the best approach? Is using single instance codeunit global variables a no-go here?
0
Answers
In tis case i:
1. create global variable (SkipTrigger) in Purchase Line
2. Create function SetSkipTrigger to set value for global variable SkipTrigger
3. Create function GetSkipTrigger to get value for global variable SkipTrigger
4. In (1) before update value in Qty field I set skipTrigger on TRUE. (Rec.SetSkipTrigger);
5. In (2) if Rec.GetSkipTrigger = TRUE then EXIT;
and I don't like to use single Codeunit in this case.
Still wondering if there are any recommendations about single instance codeunit, anyone else?