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
- 304 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
xxx is inaccessible due to its protection level AL(AL0161
rcverbeek
Member Posts: 32
Hi,
We are in the process of migrating our C\AL application towards AL. One of the issues we need to deal with is that in some page extensions we would like to access the value of a global variable in the base page. However this is impossible, getting the message "xxx is inaccessible due to its protection level AL(AL0161)"
For instance: we extended the Sales Prices page by adding an OnClosePage custom trigger. Here we would like to use the SalesTypeFilter variable, but we can't.
Now, I understand where it comes from, it is by design, but I guess many of you have dealt with this before and I just wonder if there is some kind of design pattern that we can use to deal with AL0161?
We are in the process of migrating our C\AL application towards AL. One of the issues we need to deal with is that in some page extensions we would like to access the value of a global variable in the base page. However this is impossible, getting the message "xxx is inaccessible due to its protection level AL(AL0161)"
For instance: we extended the Sales Prices page by adding an OnClosePage custom trigger. Here we would like to use the SalesTypeFilter variable, but we can't.
Now, I understand where it comes from, it is by design, but I guess many of you have dealt with this before and I just wonder if there is some kind of design pattern that we can use to deal with AL0161?
0