You’re offline. This is a read only version of the page.
5
Hi! Hope I can start a healthy discussion on the implementation of D365 BC from scratch, and the best approach to getting it to function optimally for our business.
We are working with consultants to picture how our many processes will work in D365 BC. Vanilla? Build? or Buy? I have been surprised at the amount of push back we have had when researching and considering third-party add-ons. It seems to me that they want to develop everything as customization, rather than consider add-ons as a way to reduce customization. The theory behind using add-ons was that a single consultant group will not be a guru in every functional area, and by choosing the right add-ons could connect us to experts who have thought a lot about specific challenges. It "deepens our lineup."
understandably, D365 BC is going through a big transition with Extensions and I think this is where the holdup is. When we bring up a mid-size or smaller shop's add-on, we get groans about how that is a bad direction to go.
So:
1. Does the challenge to integrate 3-4 add-ons (for areas like pricing, commissions, web shop,...) incur a high risk and stability concerns?
2. Am I correct in thinking that add-on's from a larger pool of industry-specific shops is the future of how D365 BC will be built, to reduce the amount of company-specific customizations necessary to get things up and running.
3. If the answer to #2 is yes, are we on the way to this goal but not there yet, and therefore I need to accept the high amount of caution toward using add-ons in our implementation?
Mine absolutely personal opinion: if you've found the right addon for your business, go for the addon. Otherwise I prefer specific customizations than mixing N different addons that covers not all what I need.
Remember also that N addons are not always natively born to "interact together", some customizations could be needed for sure to have a better workflow for your needs.
Share
Report
All responses (
Answers (
