You are here
AZ tech council
A while back I had set up a Hyper-V virtual machine, but it had been a while since I've needed to use it again. The time came again recently as I needed a VM to do some OS-specific testing. I got everything set up and started my VM, but was given an error message that said "Virtual machine [name] could not be started because hypervisor is not running." I was a little surprised to see it, since I could see that I had created a VM in the past - however, I remembered a change related to Hyper-V that I had made recently.
Have you given your independent sales reps CRM licenses so they can access CRM directly, rather than going through the Portal? Do you want them to have visibility only to the accounts, opportunities and leads that they are personally working?
The following steps will help you achieve this via the use of Access Teams:
If you've been using the class "CrmConnection" in the Microsoft.Xrm.Client assembly, starting with the CRM 2016 (and subsequent) SDK versions (version 8.x), it's no longer available. Instead, you'll need to connect using the CrmServiceClient class which is found in the Microsoft.Xrm.Tooling.Connector assembly. You can view the details here.
After upgrading from CRM 2016 to Dynamics 365, we noticed that the Notes control on a form for one of our custom entities was no longer working properly. It would display, but there was no longer any way to add notes to the record:
When it should be displaying like this:
Sometimes you run into an error message that can mean any one of several things has gone wrong, and there's no real way to know what is the true solution. The error "Managed Metadata Service or Connection is currently not available" in SharePoint is one of those error messages.
Whether you’re a user that just wants to share a view with someone or you’re an administrator/manager that would like to create and distribute personalized views, sharing personal views is a very common thing, so it’s surprising that CRM for Tablets does not support it. Shared views that a user does not own do not display in the mobile app. Even worse, if the user has access to a dashboard that contains personal views, they’ll receive a generic error:
While working in Dynamics CRM, I needed to add several options to a few different optionsets on the Lead entity. Adding the options isn’t difficult, but can be tedious and repetitive, so I didn’t want to do it manually. I decided to leveraged the CRM SDK and used a LINQPad query to populate the optionset as shown in Figure 1.