While trying to setup a PowerBI connection to one of our CRM Online instances I kept getting the same error over and over again as I repeated what turned out to be the same mistake.The instructions in the PowerBI setup was to go to CRM Online and get the service endpoint for the OData connection. So I navigated to the CRM instance, went to developer resources, copied the link as shown below and then pasted it into the dialog window for PowerBI. The issue is that even though the OData service url contains a trailing slash and that is how it works in the browser and programatically to retrieve the connection, PowerBI doesn’t like it and will return an ‘Unable to Connect’ error.It appears PowerBI doesn’t know to strip it out or otherwise deal with it.
Note how the OData url has a trailing space where the other endpoints don’t. This is what bit me.

OData Service URL

OData Service URL

This is the error you get when you paste the endpoint url into Power BI with the trailing slash.

PowerBI Unable to Connect Error

PowerBI Unable to Connect Error

So here is the culprit, don’t do like I did and be so literal and copy and paste the URL without deleting the trailing slash.  BTW, try this experiment. Past the url into your browser without the trailing space and then hit return. Guess what, it regenerates with the trailing space.

OData Trailing Slash Error

OData Trailing Slash Error

Years ago it was bandied about quite a bit that the core sales technique of a large mainframe company was their ability to use FUD to win the business. Don’t know what FUD is? It’s an acronym for Fear Uncertainty and Doubt. It was an very effective process when used strategically to put competitors on the defensive and strong arm the prospect in making the ‘safe’ decision to go with the traditional ‘big’ company.

It’s been used extensively by sales people since those days in the 70’s. Right now it seems to be rearing it’s ugly head in our world with the release of Windows 10 and how Dynamics CRM does or does not work with it.

Let me be clear with what we know today based on official posts from Microsoft and the CRM product team.

1. Dynamics CRM 2011, CRM 2013, and CRM 2015 are supported on Windows 10 with the web client. The supported browser is Internet Explorer 11.

2. Support for Microsoft Dynamics CRM 2015 on the new Edge browser will be available for CRM 2015 with Update 0.2 (7.0.2) and Update 1.1 (7.1.1) in September.

3. Support for Microsoft Dynamics CRM 2013 via Edge will be introduced in Update Rollup 4 for Service Pack 1 (6.1.4).

Here is where some confusion may be entering into the roadmap discussions and contributing to FUD.

1. Support for Dynamics CRM 2011 is available for IE 11. A complete browser reference for CRM 2011 for all major platforms is posted online.

2. CRM for Outlook for CRM 2011 and CRM 2013 does have a known issue with Windows 10 with IE 11 that unfortunately didn’t show up until very late in the Windows 10 release cycle. This prevents the CRM for Outlook client to install on Windows 10 machines. The CRM product team is aware of the issue and is working on a fix. There has been a workaround suggested on the community site which purports to solve the issue allow the installation successfully. I haven’t tried it myself but it has been verified as an answer by another community member.

3. Once Office 2016 releases, support will be available.

 

If you would like to reference the original post you can do that here.

 

Even though we just focus on Dynamics CRM here at CRM Innovation, Windows 10 is going to permeate everything in the computer space and will ultimately have an impact on the CRM space. For us it has hit already as we are now migrating  some of our ISV solutions from Silverlight to HTML 5 so they work in the new wonderful Edge browser.  If you need to get up to speed on Windows 10 as a designer, developer, or administrator Microsoft has some great resources available. Take a look at the learning opportunities below.
Learning Resource  Remarks
 Visual Studio Download
Everything a developer needs to know to write apps
Online training for Windows 10. Grab a beer and some popcorn, put it on the big screen and enjoy.
More great online resources for Windows 10 videos presented in the fun easy going format of Channel 9.
A live event on August 14th
We have a dashboard that tracks our project time for client work and for our ISV solutions. When getting ready to do the billing for this past month, as usual, I needed to export from a grid view a table of all the project time cards for the month. From the dashboard I clicked on the grid view link to open up the full view in a new Window. Then I proceeded to beat my head against a wall for about 30 minutes trying to figure out why I couldn’t export to a static sheet. I kept clicking on the Static Worksheet button – see image below. It kept getting exported as a worksheet that was designed to be re-imported into CRM – not what I wanted.This is an issue with CRM Online 7.10

Export to Excel no Static Export

Export to Excel no Static Export

This was getting very frustrating. So by chance I went directly to the entity grid view for the project time cards. And guess what, when I clicked on the Excel button the drop down displayed two Static Worksheet buttons, one for the good old plain jane export and the one for re-import.

Export to Excel Static Worksheet

Export to Excel Static Worksheet

 If you agree that this is a UI issue/bug that should be fixed, please vote for my suggestion on Connect – https://connect.microsoft.com/dynamicssuggestions/Feedback/Details/1651833

The following is a known error in the 1.0.0.0 release of the Office 365 Groups managed solution. As of August 5, 2015 it is on track to be fixed in the next .x release of the solution. Keep looking for it in the solutions area of your CRM Administration page in O365. In the interim trying refreshing the page and the error should go away. The group is being created.

Office Groups Exception occured in RetrieveOfficeGroupsSetting: 1

Office Groups Exception occured in RetrieveOfficeGroupsSetting: 1