You’re offline. This is a read only version of the page.
60
We have purchased a large set of modules from a third party and they are currently in the process of customising this.
This is a large project for a big company. I will be taking on this at one of my work streams and looking after it after the third party have finished the work.
I would like to get access to the solutions. As they have a team of developers and I presume most of this work has been produced using the SDK. I am a developer myself with this skillset. However they insist its Intelletual property and that we dont need to have access to these solutions. Im concerned that there may be issues as we intend to expand and maintain this solution. They insist we can just create new ones and disable them? This is a new area to me so I would like a second opinion...I see the entities can be modified which is the default option I believe so this part of the customisation is available to change.
Thanks for the help. As I understand it. We can see much of what has been done in the Managed solution and there is not much hidden in the DLL's.
However the issue I can see moving forward is if the solutions are Managed we cant install them? For example if we set up a brand new instance is it possible to re-install them there? In addition if a new release of Dynamics was released and broke a managed solution, we would be able to fix? Just trying to weigh up the pros and cons here...
I feel like if we only have managed solutions we will be at the mercy of the implmenters for allot of maintenance and development going forward?
Obviouslly this all depends on the implmentation and scope of customisation and depth of development but just looking for a general consencus on this...
Hi
As suggested above, any component that is allowed for customization can be customized from the default solution or by adding the component to a new solution. However, I would recommend that you get the unmanaged solution from them if possible. If you can get hold of the unmanaged solution, this will allow you to do the customization on a Dev environment and then deploy to UAT and Prod environments. Perhaps you could tell them that you want to maintain proper development - testing - deployment pipeline and that's why you need the unmanaged solution.
For any code, plugin/ custom workflow activities, they will have to give you source code for you to fix any bug or make any changes in the future. If they do not give you access to the source code you won't be able to fix any bugs in the future and you won't be able to make any changes. The plugin or CWA will just be like a black box.
You might have to convey the message to your management and get your case across and find a way to get access to unmanaged solutions and source code. You try your best to get as much as possible.
Ok the entities piece seems easy enough for us to maintain and see and no problem moving forward...
What I am worried about is if the solutions have been coded and plugins and workflows have been created how do we know what these do? Let alone maintain and update them? It seems akin to a black box?
Hi braddev,
You can make customization on components that are enabled to be customizable even if the solution state is managed.
But you should notice that it's unavailable to edit these components directly in managed solution.
There are 2 methods to customize the customizable components in managed solution.
1. Customize the components in Settings > Customizations > Customize the System
2. Create a new solution and add existing components from other managed solution into your new solution.
These points are referred from this article:
Hope those would help.
Regards
Clofly
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
