Update – This appears to be fixed in Service Update 5 for 8.2.0
Today I upgraded a Dynamics CRM 2016 Online Update 1 instance to Dynamics 365. Everything seemed to be going well. However when using Global Search I was getting the error below.
Query Builder Error – The specified field does not exist in Dynamics 365. If you contact support, please provide the technical details.
Are you scoping a new applications project and think Dynamics 365 could be all or part of the solution?
Starting a Dynamics CRM or Dynamics 365 Project can be a daunting task even for the most experienced decision maker. All your research might indicate that Dynamics 365 is a good fit for your business, but if you don’t know enough about the benefits, pitfalls and how it fits with your business, how can you be sure it’s the route you really want to go down?
You might be considering some of the following points?
- Maybe you’ll need to use a few in-house business analysts to do some configuration.
- Some bits may look complex so maybe some you need some .NET developers involved too?
- Should you start with Waterfall methodology or Agile or SureStep or a Human Centred Design approach?
- What training do you need?
- Fixed Price or Time and Materials?
- What licences should you buy?
- On-Premise or Cloud?
- Maybe you should go out to tender, but what if you don’t frame the requirements correctly? Should we get some training first?
- Is offshoring Dynamics 365 consultancy a good idea – can it be achieved remotely?
Microsoft has surely been looking at Salesforce for the past few years, feeling somewhat envious of their ‘apps’ market. If you take Salesforce at their word, they have over 1.4 million registered developers, so the apps market for Salesforce is clearly not a flash in the plan.
With the recent launch of Dynamics 365, there appears to be a concerted effort at Redmond to build an ecosystem around Dynamics 365, but how has this been implemented and what do application developers need to know?
“Dependency hell is a colloquial term for the frustration of some software users who have installed software packages which have dependencies on specific versions of other software packages.”
Source : Wikipedia
It’s often tempting to spin up a new trial online instance to do some custom development. The intention is normally to use it temporarily, then export your masterpiece as an unmanaged solution so you can import it into a target vanilla non-trial, more permanent instance.
With Dynamics 365, if you check all the boxes when setting up, CRM will be provisioned with a lot of supplementary solutions as well on top of what you know as a vanilla CRM instance – think Project Service, Field Service and maybe a few extra dependent solutions thrown in there for luck too.
If you need to install Dynamics CRM 2013 in an environment without internet access, you may prefer to install some of the Dynamics CRM 2013 pre-requisites manually before running Setupserver.exe. The main problem in the past has been, how do I find them?
Well courtesy of Fiddler2, here are the URLs CRM 2013 pings for the some of the pre-req files. This is based on a Windows Server 2008 R2 server, which has had CRM installed on it before, so there may be some missing here. If there are any missing that you need, please let me know and I will add to the table.
Today I spent some time trying to track down an error with a fresh install of the Dynamics CRM 2011 311 Portal Accelerator. Having spent a fair amount of time setting it up on a VM and wanting to bulk out the content a bit, I discovered that when trying to edit content from the Front End, I was getting various errors, such as :
- An error has occurred while saving your content. Your changes have not been saved.
- An error has occurred while loading content required for this feature.