Its often very useful to have a handy source of all of the standard Dynamics 365 Object Type Codes. Well, here they are for your viewing pleasure.
Keep this page bookmarked.
Continue reading “Object Type Codes Cheat Sheet for Dynamics 365”
James Hall's Dynamics 365 Blog
Yet another Dynamics 365 blog
Its often very useful to have a handy source of all of the standard Dynamics 365 Object Type Codes. Well, here they are for your viewing pleasure.
Keep this page bookmarked.
Continue reading “Object Type Codes Cheat Sheet for Dynamics 365”
I have recently updated my Visual Studio Template for holding Microsoft Dynamics Assets. Its available on the Marketplace by searching for Hallstudios, or you can download it using the button below.
Just recently updated the CRM utilities extension with the following fixes :
As usual, you can get the update from the Marketplace, or by downloading here :
How did I not know about this. After all this time, using the Dynamics Web Interface, or XrmToolbox to explore standard attributes and entities, I found this. Very useful indeed.
I recently wanted to try out Visual Studio 2019 with the SSIS Package designer (and to also try out the KingswaySoft extensions for dealing with Dynamics 365 data integration/migrations. Getting it all to work turned out to be a little bit of a challenge, so here I am documenting the issues I encountered, and what I did to fix it.
Continue reading “SSIS and Visual Studio 2019 – Issues and fixes”The other day, I was investigating some solution import issues, and I need to see who was guilty of importing a solution into an environment that it should never have been imported into.
I fired up the old XrmToolbox, to use the Plugin called Solution History which I always found a nice handy little tool for getting at the history of when and who imported solutions.
It was at that point that I realised that CRM now supports a Solution History view within the user interface. I have no idea when this appeared, but it seems to be sometime this year.
Since then, I have found this invaluable for investigation solution issues, and also for updating environments where you need to follow the exact pattern of solution imports that were done within a test environment.
To use it, simply get to your Settings area of Dynamics, and choose Solution History from within the Customization section.
This will then give you a nice list of the solutions that were imported, exported, succeeded and failed.
I have just updated the CRM Utilities for Visual Studio package to work with Visual Studio 2019 as well. The version is now at 3.6.2 and is ready to download from the Marketplace.
Just search for James Hall on the extensions window of Visual Studio or visit the marketplace.
https://marketplace.visualstudio.com/publishers/JamesHall
It can also be downloaded directly from here :
Here is a bit of useless information for you!
I setup a trial of a V9 instance of Microsoft Dynamics 365 for some testing, and I found that the Adxstudio 7 solutions would not import. The installer goes in, but installing the base portals solution fails.
To get round this, I converted the instance to a sandbox, reset it to V8.2, installed the solutions, and I intend to upgrade it to V9, although I will have to wait a week for the scheduled update to work.
So there you have it. You cannot set up a new V9 instance to run old portal code on.
Recently I had an issue where all of a sudden, a solution would not export from the development environment, even though it was previously fine, and as far as I knew, it had not changed. Dynamics would throw a very unhelpful error, with no details of what went wrong.
I tried creating a new solution, and adding the exact same components and that one also failed, so I knew it was not the solution itself, but its contents.
After a bit of trial and error, I discovered that it was the SLA’s that were causing the issue. Turns out that it was because one of the SLA’s had not been activated. Never thought it needed to be, but in this case, it was causing an issue.
So, if it ever happens to you, make that one of the first things you check, it might save you some time.
This was a version 8.2 on premise install, but I didn’t have access to the actual server.
I was getting this error when trying to import a solution into an On Premise Dynamics 365 environment.
This was a solution that I knew had previously imported into other environments, so I was very confused why it would not import. Turns out, the Sandbox Processing Service on the server was not actually running.
Restarting the Service allowed the solution import to proceed.
I believe this must have happened as we had experienced a power cut, and I have certainly seen Dynamics services not restart properly when a server is not safely switched off correctly. Also, it may have had something to do with the fact that this one little Virtual Machine server was running about 20 different CRM Organisations at once.
Anyway, never assume that its an issue with your solution. Nine times out of ten, it is, but always remember to check your environment as well.