Start any video training course for FREE. More than 500 to choose from. Learn more
Business Intelligence in Microsoft SharePointŪ 2010

Errata for Business Intelligence in Microsoft SharePointŪ 2010

The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted By Date Submitted Date Corrected
Page 74 & 76
Second bullet point and Step 8

DimCategories in the data warehouse is incorrectly referred to as HierarchyCategories. All screenshots use DimCategories

Peter Newhook  Jul 11, 2011 
Printed, PDF
Page 363
1st paragraph

The text reads as if connectivity to SQL WILL work from Office 365 for services like Visio and Excel Services. The text was intended to read as if these types of connections MAY work. The connections in fact don't work in the currently released beta, and it is possible that they will not work when the final version of that software is released. If that is the case, then that makes this page technically innaccurate. The paragraph should instead read as follows: "So what are the options for data connectivity for service applications like Excel and Visio? You may be able to get connected to SQL data that uses a SQL user name and password. Excel gives you the option to save a SQL user name and password in the connection string (which is then saved in the file). In this case, when you open up your data source for read access over the network, Excel Services from Office 365 may be able to connect to it. Another option is to store even your SQL data in the cloud by using SQL Azure. You may be able connect to SQL Azure in the same way from a service application as you would using Excel Services in SharePoint. The downside of this is that the password is stored in the workbook file, which raises security concerns. So that scenario makes sense only when the file is tightly secured, the password used is a read-only account, and the data is not mission-critical or highly sensitive. Note that at the time of this writing Office 365 is still in beta, and it is unclear if this type of data connectivity will be supported in the final version."

John Campbell
John Campbell
O'Reilly Author 
May 13, 2011