ADDON best Practice

cavalcanti_space
Member Posts: 49
Hi guys,
We are an ISV and we will develop and ADD-On solution.
I have some question and hope you could advise me.
Is it correct to create on ADD-On which will insert some code on the codeunit 80?
Our problem is that we will have to create several field on the table sales header, but we are concerned with the number of the fields. We know the table has limit size.
Our idea was to create another table linked to header and enter the data on that table. But the problem is the post. We will need to delete the data from that new table and post the value to a new table linked to the sales invoice header.
We really dont want to create the fields on the sales header due to its size limit.
do you guys have any ideas?
Thanks and Regards,
Edson
We are an ISV and we will develop and ADD-On solution.
I have some question and hope you could advise me.
Is it correct to create on ADD-On which will insert some code on the codeunit 80?
Our problem is that we will have to create several field on the table sales header, but we are concerned with the number of the fields. We know the table has limit size.
Our idea was to create another table linked to header and enter the data on that table. But the problem is the post. We will need to delete the data from that new table and post the value to a new table linked to the sales invoice header.
We really dont want to create the fields on the sales header due to its size limit.
do you guys have any ideas?
Thanks and Regards,
Edson
0
Comments
-
People often forget that the ONLY purpose of the posted sales invoice is to be able to reprint an invoice. So if you have fields that you are passing to the posted sale invoice that will NOT be printed on the invoice, then the design of your Add-On is completely wrong and needs to be rethought out and possibly redesigned from scratch.
In most cases where I see ISVs making this mistake what they should have been doing is creating a Ledger Entry table specific to the Add-On, but for some reason people don't do that any more.
Code unit 80 should be calling a posting routine in your Add-On that handles all the fields that you require.David Singleton0 -
Hi David,
Thanks for your reply.
I reckon the best idea is to create a ledger entry as we will have many fields.
Do you think it is correct to call a post routine from codeunit 80. What I mean is as we sell the add-on to many clients we will always have to do a merge of the codeunit as most of the clients have this codeunit customized.
thanks0 -
There is no problem in adding things to codeunit 80, as long as you design it correctly like David reccomends.
I hate advertizing, but my book describes a lot of these design patterns and best practices. Why don't you start there.0 -
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
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions