I love getting these error messages when using the Dynamics SDK!
I immediately know where to go to resolve the problem when it happens 🙁
If you are trying to diagnose precisely where the issue is in your code, the “Reason” member won’t have this data – probably because it’s not at the top of the stack and you need to dig deep to see what’s what.
To get to the nitty gritty of what is happening you will need to dig into the InnerFault of the Detail member to see what has really happened.
When deploying solutions, you can’t include Business Units in your solution file and if you are needing to create many of them, this can be a bit of a hassle.
I recently had this problem where I was working on a project that had many units that I didn’t want to create manually, so I turned my eyes to the SDK in order to take this task from 20 minutes to 1.
The Parent Business Unit
The most important thing with Business Units is to remember their hierarchy. Irrespective of how you have setup your system, you will always have a top-level unit that everything else inherits from.
When trying to find this unit (to then extend from) all you need to do is query for the businessunit that does not have a parent
In the USD you can create Options that you can use within your Actions/Events/etc in the Unified Service Desk Configuration.
You can also access these values from within your own control via C# relatively easily.
To access the value within my USD Custom Hosted Control via C# all that is needed is the following code.
GetConfigurationValue("FoodforThought");
And now I can use this value within the USD without having to create my own configuration files et al in C#.
A follow-up to my post on Getting Started with the Dynamics Web API – on a recent project, I was building a custom hosted control in the USD that leveraged the Dynamics Web API.
However, when I went to deploy my control, my USD instance would implode and not load whatsoever.
Turns out the issue was a result of me using a higher version of the Microsoft.IdentityModel.Clients.ActiveDirectory dll (the latest 3.19) than what is supported in the USD (using 2.22).
The resolution was to downgrade my implementation of this dll to use 2.22 et voila, my solution deployed perfectly and my USD was no longer imploding.
I should note that for the above this is all done using v2 of the USD on a Dynamics 8.2 instance.