The ability of a candidate to get the job done well will not be relevant if they do not fit in with the culture of the company. The culture of a company is an essential factor holding an organization together. It is not only important that each member of a team has the skill-set to complete their individual job, but it is also equally important that the entire team works together seamlessly. Company turnover due to a poor cultural fit can cost the company between 50-60 percent of the position’s annual salary.
You are here
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:
Lately I've been experimenting a bit with Azure Logic Apps, in combination with an On-premises data gateway. If you've ever used Logic Apps, you may have noticed that you have a set of actions for a SQL Server connection. What you may not know is that you can connect to a local database on your machine using a data gateway.
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.