Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.6K 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
- 295 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
Dependency management concepts in Business Central 365
Brainbug
Member Posts: 1
Hi,
I´m new to the world of NAV and BC. I´ve worked with several package management tools (NuGet, npm, pip) before and just started playing around with extensions for BC.
I discovered that methods from extension A can only be called in extension B if A depends on B.
Fields, methods and record data is only visible to depending extensions as fa as I understood.
My goal is to have independant extensions that can "communicate" (trigger function calls, work with record data etc.).
Maybe publisher and subscriber events could help with that.
Also I discovered that if you want to update an extension A and you have another extension B that depends on it, you have to re-install both of them.
How do you plan to work with that? Is it reasonable and how will deployments look like in the future?
What do you think? Any ideas on how to solve these issues?
I´d like read your thoughts and concepts about the BC365 dependency management so far.
Cheers,
Brainbug
I´m new to the world of NAV and BC. I´ve worked with several package management tools (NuGet, npm, pip) before and just started playing around with extensions for BC.
I discovered that methods from extension A can only be called in extension B if A depends on B.
Fields, methods and record data is only visible to depending extensions as fa as I understood.
My goal is to have independant extensions that can "communicate" (trigger function calls, work with record data etc.).
Maybe publisher and subscriber events could help with that.
Also I discovered that if you want to update an extension A and you have another extension B that depends on it, you have to re-install both of them.
How do you plan to work with that? Is it reasonable and how will deployments look like in the future?
What do you think? Any ideas on how to solve these issues?
I´d like read your thoughts and concepts about the BC365 dependency management so far.
Cheers,
Brainbug
0
Comments
I would suggest you take a look at these articles from Gunnar, I think they will help.
https://dynamics.is/?p=3170
https://dynamics.is/?p=3209
I have not tried these myself, but it seems like a great concept for avoiding dependencies.
- Use interface extension
- Design as an API
Check below link for details :
https://redandbundle.com/2018/12/06/slaying-the-behemoth-extension-design-principles/