Can we use extensions concept for codeunit in NAV 2017?
Harikiran
Member Posts: 39
Hi everyone, I m trying to learning some more things about extensions. While trying to use extensions concept from on NAV 2017 I got an error code upgrade cannot be done.
I know that NAV 2016 extensions was not upgrading code. Now, I guess NAV 2017 extensions also have a same problem.
But the main question running in my mind is why was extensions introduced if its not upgrading successfully for all object of NAV?
Can someone clarify me this question or am I wrong with my thinking? Please correct me.
Suggestions welcome.
I know that NAV 2016 extensions was not upgrading code. Now, I guess NAV 2017 extensions also have a same problem.
But the main question running in my mind is why was extensions introduced if its not upgrading successfully for all object of NAV?
Can someone clarify me this question or am I wrong with my thinking? Please correct me.
Suggestions welcome.
Harikiran BM | ERP Specialist
0
Best Answer
-
we can create extensions only when standard object is not modified except adding fields in table/page etc.
we cannot add any code in any type of object. It is same in NAV2017 as well.
about your error, we always need to add upgrade codeunit along with our extension.
https://msdn.microsoft.com/en-us/library/mt703362(v=nav.90).aspx
you can create codeunit with 2 functions (atleast blank)
OnNavAppUpgradePerDatabase
OnNavAppUpgradePerCompany5
Answers
-
can you be more clear what you are trying to do and exact error message.0
-
Can we use extensions in 2017 to upgrade base codeunit?Harikiran BM | ERP Specialist0
-
what do you mean by upgrade base codeunit?0
-

Thanks for your reply @mohana_cse06 ,
Attached is the image which explains the error I received when trying to use extensions concept of some add-on for 2017..
I tried to create a extensions package and received this error
"Package contains database schema that are not handled in upgrade code".
So, I just wanted to know is this error is because it cannot handle the custom changes of codeunit? or something different?
Because I do remember Extensions in 2016 was not working for the custom base codeunit(modified codeunit, ex: codeunit 80 with some customization).
I guess now you have understood my question.
Harikiran BM | ERP Specialist0 -
we can create extensions only when standard object is not modified except adding fields in table/page etc.
we cannot add any code in any type of object. It is same in NAV2017 as well.
about your error, we always need to add upgrade codeunit along with our extension.
https://msdn.microsoft.com/en-us/library/mt703362(v=nav.90).aspx
you can create codeunit with 2 functions (atleast blank)
OnNavAppUpgradePerDatabase
OnNavAppUpgradePerCompany5 -
Categories
- All Categories
- 75 General
- 75 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.8K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 611 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 253 Dynamics CRM
- 103 Dynamics GP
- 6 Dynamics SL
- 1.5K Other
- 991 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 28 Design Patterns (General & Best Practices)
- Architectural Patterns
- 9 Design Patterns
- 4 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1K General Chat
- 1.6K Website
- 77 Testing
- 1.2K Download section
- 23 How Tos section
- 249 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
