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
- 301 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
Application Area in NAV 2018 for on premise installations
borealis
Member Posts: 35
On the item card page there's a field "Type" where the visibility is set in OnOpenPage based on whether an Application Area Setup record with basic or suite values enabled exists. Yet everywhere else I see in code, that is governed by the ApplicationArea property of the field/action which, if no Application Area Setup record exists, appears to show it by default. Since the documentation explicitly says that this is for Dynamics 365, and not recommended for use in on premise installations, this seems to me to be a bug for on premise installations. The consistent thing to do would be to simply set the ApplicationArea for the type field to #basic,#suite, which if application areas were being used would correctly show or hide the field.
Does anybody have any insight on whether this is intentional or part of a new usage for the Application Areas?
Does anybody have any insight on whether this is intentional or part of a new usage for the Application Areas?
0