SQL Server Analysis Services (SSAS) Data Integration with SharePoint

Microsoft SQL Server Analysis Services (SSAS) can be integrated and synchronized codeless with SharePoint on-premise using the Layer2 Business Data List Connector. In case you are looking for Online data integration, you will find the right tool here.

Benefits of SQL Server Analysis Services (SSAS) Data Integration in SharePoint

• Very easy to setup in a few minutes: Create a SharePoint list, click "Connect to external data source" in the list settings, select the data provider, enter connection settings and data query as shown below. That's it.
• No changes in the ODBC data source required: No programming, no additional tools.
• Connected list data always up-to-date: The connected ODBC data query updates automatically in background (via SharePoint Timer Job), or alternatively, on-demand (Action Menu / Ribbon Button, URL, via workflow, API).
• One-way and optional two-way connection: You can write-back the changes made in the SharePoint list to the external ODBC data source automatically with full CRUD (Create / Update / Delete) functionality. The SharePoint list can act as a full-featured front-end for external systems.
• Well-known BCS "external list" issues and limitations are completely solved: ALL list features are to you. Views, sorting and grouping, filters, calculated fields, search, managed metadata. Lookups, additional columns and attachments can be created as normal. All kind of lists can be used, e.g. contacts, tasks, calendar, or custom lists. You can take external data offline via Outlook.
• Workflows and notifications on external data change: List workflows and change notifications per RSS or email can be used to take business actions in SharePoint, when external ODBC data records are changed.
• Application logging, reporting, and notifications: A SharePoint list is used to store settings and log information. SharePoint item versioning and workflows can be used to manage reporting and notifications. Direct notification per email in case of errors is supported as well.
• Highest Security, best performance, easy to maintain: SharePoint Secure Store can be used to store security relevant configuration information safely in one central place. Users are working with the SharePoint lists as an external data cache with highest security and performance. Large data sources can be synchronized.
• 100+ more external systems supported: Layer2 Data Providers included (e.g. for external SharePoint or Office 365, Exchange, Dynamics ERP/CRM, OData, XML/RSS, SOAP), vendor specific data providers can be used (e.g. SQL Server Oracle, MySQL etc.), 3rd party data providers also supported, e.g. for custom ERP/CRM, Facebook or Twitter. See here for supported systems and applications.

SQL Server Analysis Services (SSAS) Specific SharePoint List Configuration Settings

In the Business Data List Connector the data connection must be configured as follows:

Figure 2: Example connection configuration to connect a native SharePoint list to a SQL Server Analysis Services (SSAS) data entity via Layer2 Business Data List Connector.

• ​Please select the .Net Framework Data Provider for OleDb from the list of data providers. The MS OLAP OLEDB Data Provider must be installed. It comes with the SSAS package.
• You can use a connection string like this to connect:
  Data Source=localhost; Provider=MSOLAP.5; Cube=Adventure Works; Initial Catalog=AdventureWorksDW2014Multidimensional-SE
  More about SSAS connection strings here.

• Primary key for data sync must be set to any column(s) having unique values (together). In this case:
  [Product].[Category].[Category].[MEMBER_CAPTION], [Product].[Subcategory].[Subcategory].[MEMBER_CAPTION], [Product].[Product].[Product].[MEMBER_CAPTION]
• You can map your data fields to specific external source fields in the Layer2 Business Data List Connector. Please take care about data types (simple type conversions are supported).
• Bi-directional synchronization is NOT supported.
• No installation or changes are required at the data source or data destination despite the CData providers.
• No programming required for setup a connection and sync.
• No need to open your local network for access from outside.

SQL Server Analysis Services (SSAS) Data Connection Details

​Provider:
.Net Framework Data Provider for OleDb

Connection string sample:
Data Source=localhost; Provider=MSOLAP.5; Cube=Adventure Works; Initial Catalog=AdventureWorksDW2014Multidimensional-SE

Select Statement sample:
Select non empty CrossJoin([Product].[Category].children,[Product].[Subcategory].children, [Product].[Product].children) on rows, {[Measures].[Internet Sales Amount],[Measures].[Internet Freight Cost]} on columns from [Adventure Works] where {[Date].[Calendar Year].[CY 2013]};

SharePoint Integration via SQL Server Analysis Services (SSAS) - Limitations, Known Issues and Workarounds

• There could be issues with pre-formatted data like currencies. Please make sure that this data is passed through without format and let SharePoint do the formatting.
• Bi-directional sync is not supported. The connection is for reading data from the SSAS OLAP cube and write to SharePoint

Please contact [email protected] for help.

Ready to go next steps?