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
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 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
Extension usage in ordinary objects
MaW
Member Posts: 74
Hi,
In NAV 2018 MS plans to move all localization elements to extensions. That has all ready started with the Danish localization.
FIK, OIOUBL etc, is now extension based. Read more here: https://dynamicsuser.net/nav/b/admin/posts/dynamics-nav-2018-localization-s-as-extensions
How do we use these localization elements in "ordinary" AL objects? More specific, how do we use the FIK code? Before we used codeunit 13650 FIK Management, but that has moved to extensions, so how to use that in a report now?
Thanks.
In NAV 2018 MS plans to move all localization elements to extensions. That has all ready started with the Danish localization.
FIK, OIOUBL etc, is now extension based. Read more here: https://dynamicsuser.net/nav/b/admin/posts/dynamics-nav-2018-localization-s-as-extensions
How do we use these localization elements in "ordinary" AL objects? More specific, how do we use the FIK code? Before we used codeunit 13650 FIK Management, but that has moved to extensions, so how to use that in a report now?
Thanks.
0