OlapPivotTableExtend Wiki & Documentation Rss Feed

New Comment on "Filter List"

Kimvermeij — Thu, 07 Mar 2013 14:24:30 GMT

I really want a feauture that saves my filter settings even though the members (temporarily) dont exist in the cube dimension (anymore). Or is there already a way to save the filter settings?

Updated Wiki: Excel 2013

furmangg — Thu, 15 Nov 2012 15:42:21 GMT

Excel 2013

MDX Calculation GUI

Excel 2013 is the first version to support a GUI for managing MDX calculated measures and members in a PivotTable. After clicking on a PivotTable, these features can be found under the PivotTable Tools... Analyze tab and under the OLAP Tools menu:

The MDX Calculated Measure dialog looks like:

The MDX Calculated Member dialog lets you add a calculated dimension member:

Finally, the Manage Calculations dialog looks like:

The Excel Blog also covered this feature here.

Why Continue Using OLAP PivotTable Extensions?

As you can see, it greatly improves upon the calculation management UI from the OLAP PivotTable Extensions add-in by adding a very nice field list and function list. So why would you continue using OLAP PivotTable Extensions? Starting with release 0.8.0, OLAP PivotTable Extensions adds support for Excel 2013. The add-in also offers these other features:

Excel Data Model

Excel 2013 natively integrates the xVelocity engine behind PowerPivot and allows loading multiple tables into what's known as the Excel Data Model. This is a built-in in-memory Analysis Services database which is deeply integrated into Excel 2013. Teo Lachev wrote up a good overview.

OLAP PivotTable Extensions v0.8.0 adds support for the Excel Data Model. (Disclaimer: The ability to connect to the Excel Data Model and/or PowerPivot from OLAP PivotTable Extensions is using unsupported APIs and as such the behaviour may change or stop working without notice in future releases. This functionality is provided on an "as-is" basis.) All OLAP PivotTable Extensions features are supported except:

MDX calculated measures and members (as the Excel Data Model doesn't support this)
Clear PivotTable Cache (since the data is local and this feature doesn't make sense for the Excel Data Model)
Change PivotTable Defaults (since "refresh on open" will cause Excel to reconnect to the SQL sources behind the Excel Data Model, potentially causing long delays upon workbook open. If you want to enable this option manually, the native Excel PivotTable Options dialog allows you to set this)
Show Property as Caption (currently the Excel Data Model doesn't provide support for member properties)

Click-to-Run Support

Office 365 as part of the Office 2013 release supports a new install approach called Click-to-Run (more information here). OLAP PivotTable Extensions works in this scenario as soon as streaming installation is complete.

New Comment on "Search"

mivar — Thu, 08 Nov 2012 14:51:47 GMT

First off all add in i super cool. However when I use search within dimension I can't seem to get any values ? Tried many dimensions, So when I look for AMMA in [EGO Booking Types].[Ego Booking Subtype] it doesnt list any members and I have several starting with AMMA. IF I search in field list using standard excel 2010 search it works. Why this difference ? Something in desing of cube we need to be aware ofF `?

New Comment on "Excel 2013"

jeremysechler — Tue, 25 Sep 2012 19:52:07 GMT

Handy and it is working well for me in the 2013 Preview. Thanks!

Updated Wiki: Excel 2013

furmangg — Thu, 30 Aug 2012 14:08:40 GMT

Excel 2013

MDX Calculation GUI

Why Continue Using OLAP PivotTable Extensions?

Excel Data Model

MDX calculated measures and members (as the Excel Data Model doesn't support this)
Clear PivotTable Cache (since the data is local and this feature doesn't make sense for the Excel Data Model)
Change PivotTable Defaults (since "refresh on open" will cause Excel to reconnect to the SQL sources behind the Excel Data Model, potentially causing long delays upon workbook open. If you want to enable this option manually, the native Excel PivotTable Options dialog allows you to set this)
Show Property as Caption (currently the Excel Data Model doesn't provide support for member properties)

Click-to-Run Support

Updated Wiki: Home

furmangg — Sat, 04 Aug 2012 22:32:28 GMT

OLAP PivotTable Extensions is an Excel 2007, Excel 2010, and Excel 2013 add-in which extends the functionality of PivotTables on Analysis Services cubes. The Excel API has certain PivotTable functionality which is not exposed in the UI. OLAP PivotTable Extensions provides an interface for some of this functionality. It also adds some new features like searching cubes, configuring default settings, and filtering to a list in your clipboard. The add-in can be launched from the following menu option in the right-click menu for PivotTables:

Private Calculated Members

Any calculated members which are part of the Analysis Service cube on the server can be added to PivotTables. But there is no built-in UI to define your own MDX calculations. Adding extra Excel calculations in the cells surrounding the PivotTable has some limitations as they are not part of the PivotTable and can be wiped out if the dimensions of the PivotTable change, and plain Excel calculations must only operate on data visible in the PivotTable.

OLAP PivotTable Extensions let you define your own calculated measures which are private to that particular PivotTable:

Those calculations appear in the PivotTable just like any other calculations:

They appear in the Field List pane at the very top under the Values grouping:

For help with advanced calculation properties for these private PivotTable calculations, or for help with MDX expressions, refer to our Calculations Help page.

Thankfully, Excel 2013 does provide a UI for building MDX calculations for the first time. It even includes a drag and drop field and function list. So use OLAP PivotTable Extensions in Excel 2013 for some of the other features it offers, which are detailed below.

Best Practice: In order to ensure a single version of the truth, it is a best practice to define important calculations as part of the cube source code. But some calculations like simple ratios or differences may clutter the cube and may be more appropriate if defined in the PivotTable itself. In addition, certain ad hoc research or prototyping may be more appropriate to be done as calculations private to a PivotTable until they are finalized and are ready to be added to the cube source code.

Limitation: If you run "OLAP Tools... Convert to Formulas" on a PivotTable with private calculated members in Excel 2007, the private calculated members will show N/A. There is no known workaround at this point other than upgrading to Excel 2010 or having your OLAP administrator define these calculated members in the cube itself.

Calculations Library

Since all calculations you define are private to that one PivotTable, OLAP PivotTable Extensions automatically creates a Calculations Library for you which contains all the calculations you create. This allows you to pick any previous calculation you've used from a dropdown and add it to the current PivotTable:

You can also perform Calculation Library maintenance by importing, exporting, and deleting calculations:

View PivotTable MDX

If a PivotTable is performing poorly or returning incorrect numbers, it may be necessary for the Analysis Services administrator to troubleshoot the MDX query which the PivotTable is using. The MDX tab of the OLAP PivotTable Extensions dialog shows you this MDX.

Starting with release 0.7.3, you can check the checkbox in the top right in order to send your MDX query to a web service for formatting, thanks to Nick Medveditskov.

The MDX is exactly what is sent to the server with one exception. Any private calculations you've created for your PivotTable are defined as session calculated members. The MDX query exposed on the MDX tab displays the formulas for these calculations as query calculated members in the WITH clause of the MDX query. This allows an administrator to copy and paste the MDX query and troubleshoot it more easily in Management Studio or MDX Studio.

Filtering PivotTable to a List

A common scenario is having a list of items you wish to research in a PivotTable. Instead of manually checking each item in the filter dropdown, you can use the Filter List feature from OLAP PivotTable Extensions:

Changing PivotTable Defaults

Certain settings must be manually changed after creating a new PivotTable. For instance, if your dimensions have calculated members you wish to see in your PivotTable, you must manually right click on the PivotTable, choose PivotTable Options, flip to the Display tab, then check "Show calculated members from OLAP server". The Defaults tab of OLAP PivotTable Extensions lets you default this setting to be on in any new PivotTables you create in the future. If checked, it also automatically sets "Refresh data when opening the file" on the connection properties:

Searching

Finding what you’re looking for in a cube can sometimes be challenging, but the Search feature of OLAP PivotTable Extensions can help. It lets you text search the items in the Field List and their descriptions. It also lets you text search the dimension members in your cube.

For more detailed information about the Search feature, see the dedicated Search page.

Distributing PivotTables

OLAP PivotTable Extensions need only be installed on computers which need to create new private PivotTable calculations. After those calculations have been defined, the PivotTable can be distributed to others without problem. If you distribute the Excel 2007 workbook to other Excel 2007 users, they will be able to continue designing and manipulating that PivotTable without problem. If published to Excel Services, the private calculations you define will still be active in the PivotTable.

The Calculation Library does not need to be distributed unless other users wish to start brand new PivotTables and reuse certain calculations you have created using OLAP PivotTable Extensions.

Using Excel 2007/2010/2013 and OLAP PivotTable Extensions to edit an Excel 2003 format .xls workbook with a PivotTable and add a private calculated member will work. This PivotTable can be saved and distributed to users of Excel 2003 and the private calculated member will show up and work.

Other Features

Other features include:

Installation Requirements

Excel 2007, Excel 2010, or Excel 2013 is required.
Access to a cube on an Analysis Services server is required.
.NET Framework version 3.5 SP1 is required.
See the Download tab for the 32-bit version and the 64-bit version of OLAP PivotTable Extensions.

Troubleshooting Installation

If OLAP PivotTable Extensions is not visible in Excel, please consult the Troubleshooting Installation page.

Feedback

To report bugs or suggestions, please post an item to the Issue Tracker tab.

To ask questions about MDX formulas such as the formulas used for private PivotTable calculations, see our Calculations Help page, or post a question to the Microsoft Analysis Services Forum, or contact your Analysis Services administrator.

To discuss OLAP PivotTable Extensions, please start a thread on the Discussions tab.

Updates

To keep up-to-date with future enhancements, subscribe to the Release RSS feed or to the All Project Updates RSS feed.

Acknowledgments and Additional Information

For links to other resources about PivotTables, view our Acknowledgments and Additional Information page.

Updated Wiki: Excel 2013

furmangg — Sun, 29 Jul 2012 00:58:59 GMT

Excel 2013

MDX Calculation GUI

Why Continue Using OLAP PivotTable Extensions?

Excel Data Model

MDX calculated measures and members (as the Excel Data Model doesn't support this)
Clear PivotTable Cache (since the data is local and this feature doesn't make sense for the Excel Data Model)
Change PivotTable Defaults (since "refresh on open" will cause Excel to reconnect to the SQL sources behind the Excel Data Model, potentially causing long delays upon workbook open. If you want to enable this option manually, the native Excel PivotTable Options dialog allows you to set this)
Show Property as Caption (currently the Excel Data Model doesn't provide support for member properties)

Click-to-Run Support

Office 365 as part of the Office 2013 release supports a new install approach called Click-to-Run. OLAP PivotTable Extensions works in this scenario as soon as streaming installation is complete.

Updated Wiki: Search

furmangg — Sat, 28 Jul 2012 23:16:31 GMT

Search

Finding what you’re looking for in a cube can sometimes be challenging, but the Search feature of OLAP PivotTable Extensions can help. It lets you text search the items in the Field List and their descriptions. It also lets you text search the dimension members in your cube.

There are 4 primary use cases for the Search feature:

USE CASE #1: Finding a field in the field list

Let’s say that you have been directed to cut costs company-wide. You want to research anything related to costs, so you pull up a PivotTable and begin to scroll through the enormous field list trying to find anything related to cost.

Then you install OLAP PivotTable Extensions and can text search the field list for the term “cost.” You quickly see that there are several measures showing various costs, and there is also a Standard Cost attribute of a Product. You check the ones you want and add them to the PivotTable.

USE CASE #2: Finding where a member resides in the tree

Let’s say that you want to slice a PivotTable to see the data for a particular employee named Kim Ralls. You have no idea who manages her so do not know where to look in the tree. (But you do know she is not very senior, so she is probably quite deep in the Employees hierarchy. In fact, she’s 4 levels deep in Adventure Works.) So you add the Employees hierarchy to the filter area, then you right-click on that hierarchy in the PivotTable and choose “Search…”

The OLAP PivotTable Extensions window pops up, it preselects that you just want to look in the Employees hierarchy, and then you search for “ralls”:

Checking Kim T. Ralls and clicking “Add to PivotTable” will set the filter to that employee.

You can also right-click on dimension hierarchies on rows or columns and search them in a similar manner. If the dimension member you find and choose to add to the PivotTable is part of a hierarchy on rows or columns, OLAP PivotTable Extensions tries to make sure that hierarchy is expanded so that the member is visible. However, in some situations, other filters or lack of fact data may cause that member to be invisible even after you click the “Add to PivotTable” button.

USE CASE #3: Finding which dimensions contain information about a term

Let’s say that you are the sales manager for the Northwest part of the Unites States. You are obviously interested in the Northwest, so you can search the cube’s dimensions to see what references to the northwest there are:

You see that the Sales Territory dimension and the Organization dimension both contain a member related to the Northwest. There is also a reseller with an address containing that search term.

USE CASE #4: Searching descriptions of fields

Unfortunately, Excel 2007/2010/2013 does not display the description property as a tooltip in the field list like it should. The Search feature of OLAP PivotTable Extensions lets you search the description property of every field in the field list:

The “description” property (and the “Folder” property) is only searched when you uncheck “Exact match.”

Add To Current Filters

Release 0.7.1 adds a new feature which is the ability for your search results to be added to existing filters:

This button applies when you are searching Dimension data and when the dimension member(s) you're adding come from a field that is in the Filters section of the PivotTable currently (or from a field that's not currently in the PivotTable and will thus be added to the Filters section of the PivotTable when you click "Add to PivotTable"). Checking "Add to current filters" will add the members you check to the existing members checked in that Filter field. You will end up with a multi-select. This is also helpful when you want check more than one member from the same field and want the filter to reflect a multi-select that includes all items you just checked in the Search dialog.

Search Speed

Cubes contain a vast amount of metadata, and dimensions can be very large, so it is good to know how expensive each type of search will be...

FASTEST: Searching the Field List is the fastest search operation as it is simply searching metadata. If you uncheck “Exact match” it also searches the Description property and the Folder property, but this does not impact performance significantly.
FAST: Searching a particular hierarchy by choosing it out of the “Look in” dropdown, and checking “Exact match” will be very fast as it uses the hash indexes for that dimension.
QUICK: Searching dimension data with “Exact match” checked and “Search member properties” unchecked is fairly quick as it uses the hash indexes for the dimensions.
SLOW: Searching dimension data with “Exact match” unchecked is slow as it has to run one query per hierarchy and scan every dimension member. Dimensions are scanned in order of smallest to largest (since smaller dimensions are often used more frequently), so you may see the progress bar moving slower and slower the further it gets.
SLOWEST: Searching dimension data with “Search member properties” checked is very slow as it has to run one query per hierarchy and scan every dimension member and every member property in addition to the member’s caption. Dimensions are scanned in order of the smallest to the largest.

Warning: If you have ROLAP dimensions, this searching dimension data could be very slow, so it is recommended that you search individual hierarchies by picking them out of the “Look in” dropdown. Talk to your Analysis Services administrator to determine if you have any ROLAP dimensions.

Note: The search feature code was designed so that the CubeSearcher class has no knowledge of Excel. That makes it completely standalone so it can be reused in other custom UIs. Just be sure to credit this project and post a discussion topic if you make enhancements so we can consider pushing those enhancements back into OLAP PivotTable Extensions.

Updated Wiki: Calculations Help

furmangg — Sat, 28 Jul 2012 23:15:49 GMT

Calculations Help

This page is a resource for the OLAP PivotTable Extensions if you are creating private PivotTable calculations and need help. The formula used is a standard Analysis Services MDX expression. All formulas are executed on the Analysis Services server.

The best place to ask for help with MDX expressions is at the Microsoft Analysis Services Forums.

Example Calculations

The following calculations work against Microsoft's sample Adventure Works cube:

Ratio

IIf(
 [Measures].[Internet Order Count] = 0
 ,null
 ,[Measures].[Internet Tax Amount] / [Measures].[Internet Order Count]
)

MDX References

MDX Function Reference
MDX Function Usage Examples
VBA functions you can use in MDX expressions.
If Excel 2003 or later is installed on the Analysis Services server, these Excel functions can be used in your MDX expressions.

Advanced

The following are advanced tricks that may require more advanced knowledge of Analysis Services, your cube, and MDX.

Calculated Members on Dimensions

If you type in simply "My Calculation" or "[Measures].[My Calculation]" into the Calculation Name field in Calculations tab of OLAP PivotTable Extensions, you are creating a calculated measure. Calculations can also be placed on dimensions. This is appropriate when the calculation applies across to all measures.

As an example, you could define the following calculation:

Calculation Name: [Product].[Product Categories].[Bikes].[Road Bikes + 25%]
Formula: [Product].[Product Categories].[Bikes].[Road Bikes] * 1.25

These dimension calculated members then show up in the PivotTable just like normal dimension members:

NON_EMPTY_BEHAVIOR

The formula you provide for a calculation can include the NON_EMPTY_BEHAVIOR property which is a performance hint for MDX query execution on the server. While this property can drastically improve performance, do not use it unless you know what you're doing as it will cause incorrect numbers to be returned if you use it incorrectly. You may want to have your Analysis Services administrator check your calculations and NON_EMPTY_BEHAVIOR settings by exporting and sending him/her your Calculations Library.

For more information on NON_EMPTY_BEHAVIOR in Analysis Services 2005 see the Performance Guide and search for "NEB". Do not include a NON_EMPTY_BEHAVIOR if your PivotTable is running off an Analysis Services 2008 cube.

You can also set the FORMAT_STRING, BACK_COLOR, and FORE_COLOR properties (though since you can format the data in the PivotTable with native Excel functionality, this isn't strictly necessary). You may also set the SOLVE_ORDER property for situations when multiple calculations intersect on a particular cell.

The following is an example of setting such properties:

[Measures].[Internet Tax Amount] / [Measures].[Internet Order Count]
,NON_EMPTY_BEHAVIOR = [Measures].[Internet Tax Amount]
,FORMAT_STRING = "$#,##0"

Putting Calculations in Folders (AS2008 only)

When you build a private calculation in a PivotTable, it goes in the Values folder at the top of the field list. If your server is Analysis Services 2008, you can put that measure into a subfolder in the Values folder by using the DISPLAY_FOLDER property:

[Measures].[Internet Sales Amount] * 2
,DISPLAY_FOLDER = 'My Folder'

Or you could put it in the folder for a measure group:

[Measures].[Internet Sales Amount] * 2
,ASSOCIATED_MEASURE_GROUP = 'Internet Sales'

Or you could put it in a subfolder inside a particular measure group:

[Measures].[Internet Sales Amount] * 2
,DISPLAY_FOLDER = 'My Folder'
,ASSOCIATED_MEASURE_GROUP = 'Internet Sales'

AS2000 Syntax

For PivotTables running off an Analysis Services 2000 cube, note that the syntax for calculated members in AS2000 was less flexible. You must surround your entire MDX with single quotes like:

'[Measures].[Internet Tax Amount] / [Measures].[Internet Order Count]'

PowerPivot

For PowerPivot, here is the official policy. If it's not done using the Excel UI, it's not supported by Microsoft. So using OLAP PivotTable Extensions (which uses the Excel API) won't be supported by Microsoft. So use OLAP PivotTable Extensions on top of PowerPivot PivotTables at your own risk.

That being said, using OLAP PivotTable Extensions to add calculations to a PowerPivot PivotTable works fine most of the time. It lets you do things which are not possible with PowerPivot itself, for example, adding calculated members to dimensions (so that the calculation applys to every measure).

Note the Solve_Order workaround mentioned in the following discussion # VALUE when using AGGREGATE() against PowerPivot. Also note the tips on troubleshooting DAX errors in PowerPivot mentioned in that discussion. Finally, note that the calculations you can add in OLAP PivotTable Extensions are MDX calculations, not DAX calculations.

Unfortunately, PowerPivot for Excel 2013, which comes installed with Excel, but has to be activated under COM Add-ins, has removed the ability add MDX calculations to PivotTables. For more about Excel 2013 and the Excel Data Model, see the Excel 2013 page.

Updated Wiki: Unsupported Language Configuration

furmangg — Sat, 28 Jul 2012 22:32:56 GMT

Unsupported Language Configuration

Starting with OLAP PivotTable Extensions version 0.7.4, language configurations are handled properly. Unfortunately, there is one niche scenario which it is impossible for OLAP PivotTable Extensions to support. We are at the mercy of two conflicting limitations. On one hand, if you do not have the Office Language Pack installed for your Windows Language set in the regional settings, Excel API calls may encounter an Old format or invalid type library error, and the workaround is to set the CurrentCulture to the Excel UI language before making the API call which OLAP PivotTable Extensions does. However, when the "Retrieve data and errors in the Office display language when available" setting on the connection is unchecked, the PivotTable connects to Analysis Services using the Windows Language. When both of these scenarios occur at once, OLAP PivotTable Extensions warns you that you are running an unsupported language configuration. It is impossible for Excel API calls to avoid both the "Old format or invalid type library" error and the LocaleIdentifier error. The following table summarizes the supported language configurations:

Has installed Office Language Pack matching Windows Regional Settings?	Connection has Retrieve in Excel UI checked	Supported configuration
Yes	Yes	Yes
Yes	No	Yes
No	Yes	Yes
No	No	No

Because you are on this page, you are probably running an unsupported configuration. The About tab lists your language configuration and shows if it's unsupported. For example, on this machine the two Office Language Packs installed are English and Spanish. Since the Windows Language is set to French and that Office Language Pack isn't installed, and since the connection has "Retrieve data and errors in the Office display language when available" unchecked, this language configuration is unsupported:

Solutions

If you want to use OLAP PivotTable Extensions without errors, you must do one of the following:

Install the Office Language Pack matching your current "Windows Language" as identified in the About dialog.
Change the Windows Regional settings to a language for which you have an Office Language Pack installed. To change this, see the instructions below.
Check "Retrieve data and errors in the Office display language when available" on each PivotTable connection.
Include LocaleIdentifier on the connection string as described in the workarounds section of a that KB article. Note that Locale Identifier (with a space) does work for Excel, but isn't visible to OLAP PivotTable Extensions. So use LocaleIdentifier (without a space). A list of LocaleIdentifier values can be found in the "LCID Dec" column of this table.
Use the xllex.dll trick mentioned in Kim A's comment

Windows Regional Settings can be changed from Start... Control Panel... Clock, Language, and Region... Region and Language:

To see which Office Language Packs are installed, go to Start... All Programs... Microsoft Office... Microsoft Office 2010 Tools... Microsoft Office 2010 Language Preferences, then look under Display Languages. In this screenshot, English and Spanish Language Packs are installed:

If this LocaleIdentifier errors happens to you frequently, vote for this Connect issue so the Analysis Services team knows to prioritize a resolution for this issue.

Updated Wiki: About Tab

furmangg — Sat, 28 Jul 2012 22:32:16 GMT

About Tab

The About tab tells the user which version of OLAP PivotTable Extensions they are using and whether Excel is 32-bit or 64-bit. It also displays some troubleshooting information around Windows and Excel languages in use. If you want to report bugs or feature suggestions, follow the link provided, and be sure to include the version and language information in your bug report.

The About tab also tells the user the PivotTable version and, if not the latest version, gives instructions on how to upgrade.

Background on PivotTable Versions

As this article describes, different functionality is available with different PivotTable versions. For example, some of the Excel APIs used by the Search tab are not supported on PivotTable versions older than 2007. This article describes some specific functionality differences with calculated dimension members that depend on the PivotTable version.

If a PivotTable was created under an old version of Excel, or if a PivotTable was created in Excel 2007/2010/2013 while compatibility mode was on (i.e. when File... Options... Save files in this format... .xls is set), then a PivotTable may not be the current version. Upgrading generally involves saving the workbook as .xlsx and then refreshing the PivotTable, but the About tab will display any other atypical instructions about other scenarios (like if UpgradeOnRefresh has been disabled, etc.)

Updated Wiki: Home

furmangg — Sat, 28 Jul 2012 22:29:49 GMT

Private Calculated Members

Any calculated members which are part of the Analysis Service cube on the server can be added to PivotTables. But there is no built-in UI to define your own MDX calculations. Adding extra Excel calculations in the cells surrounding the PivotTable has some limitations as they are not part of the PivotTable and can be wiped out if the dimensions of the PivotTable change, and plain Excel calculations must only operate on data visible in the PivotTable.

OLAP PivotTable Extensions let you define your own calculated measures which are private to that particular PivotTable:

Those calculations appear in the PivotTable just like any other calculations:

They appear in the Field List pane at the very top under the Values grouping:

For help with advanced calculation properties for these private PivotTable calculations, or for help with MDX expressions, refer to our Calculations Help page.

Best Practice: In order to ensure a single version of the truth, it is a best practice to define important calculations as part of the cube source code. But some calculations like simple ratios or differences may clutter the cube and may be more appropriate if defined in the PivotTable itself. In addition, certain ad hoc research or prototyping may be more appropriate to be done as calculations private to a PivotTable until they are finalized and are ready to be added to the cube source code.

Limitation: If you run "OLAP Tools... Convert to Formulas" on a PivotTable with private calculated members in Excel 2007, the private calculated members will show N/A. There is no known workaround at this point other than upgrading to Excel 2010 or having your OLAP administrator define these calculated members in the cube itself.

Calculations Library

View PivotTable MDX

Filtering PivotTable to a List

Changing PivotTable Defaults

Searching

Distributing PivotTables

Other Features

Other features include:

Installation Requirements

Excel 2007, Excel 2010, or Excel 2013 is required.
Access to a cube on an Analysis Services server is required.
.NET Framework version 3.5 SP1 is required.
See the Download tab for the 32-bit version and the 64-bit version of OLAP PivotTable Extensions.

Troubleshooting Installation

If OLAP PivotTable Extensions is not visible in Excel, please consult the Troubleshooting Installation page.

Feedback

Updates

To keep up-to-date with future enhancements, subscribe to the Release RSS feed or to the All Project Updates RSS feed.

Acknowledgments and Additional Information

For links to other resources about PivotTables, view our Acknowledgments and Additional Information page.

Updated Wiki: Excel 2013

furmangg — Sat, 28 Jul 2012 22:08:33 GMT

Excel 2013

MDX Calculation GUI

Why Continue Using OLAP PivotTable Extensions?

Excel Data Model

MDX calculated measures and members (as the Excel Data Model doesn't support this)
Clear PivotTable Cache (since the data is local and this feature doesn't make sense for the Excel Data Model)
Change PivotTable Defaults (since "refresh on open" will cause Excel to reconnect to the SQL sources behind the Excel Data Model, potentially causing long delays upon workbook open. If you want to enable this option manually, the native Excel PivotTable Options dialog allows you to set this)
Show Property as Caption (currently the Excel Data Model doesn't provide support for member properties)

Updated Wiki: Excel 2013

furmangg — Sat, 28 Jul 2012 21:51:42 GMT

Excel 2013

MDX Calculation GUI

Why Continue Using OLAP PivotTable Extensions?

Updated Wiki: Excel 2013

furmangg — Sat, 28 Jul 2012 21:44:57 GMT

Excel 2013

MDX Calculation GUI

Why Continue Using OLAP PivotTable Extensions?

Updated Wiki: Excel 2013

furmangg — Sat, 28 Jul 2012 21:42:47 GMT

Excel 2013

MDX Calculation GUI

Excel 2013 is the first version to support a GUI for managing MDX calculated measures and members in a PivotTable. After clicking on a PivotTable, these features can be found under the PivotTable Tools... Analyze tab and under the OLAP Tools menu:

<image>

The MDX Calculated Measure dialog looks like:

<image>

The MDX Calculated Member dialog lets you add a calculated dimension member:

<image>

Finally, the Manage Calculations dialog looks like:

<image>

Why Continue Using OLAP PivotTable Extensions?

Updated Wiki: Office 2013 Primary Interop Assemblies

furmangg — Sat, 28 Jul 2012 19:44:33 GMT

Office 2013 Primary Interop Assemblies

Installation Instructions

OLAP PivotTable Extensions requires Office Primary Interop Assemblies. Currently, the Office 2013 Primary Interop Assemblies Redistributable is not yet available. However, you can install the Primary Interop Assemblies for Office 2013 (also known as .NET Programmability Support) as follows:

On Windows XP, go to Start... Settings... Control Panel... Add or Remove Programs. Click on your version of Microsoft Office 2013 and click Change. Choose Add or Remove Features.

On Windows 2003, go to Start... Control Panel... Add or Remove Programs. Click on your version of Microsoft Office 2013 and click Change. Choose Add or Remove Features.

On Windows Vista or Windows 2008, go to Start... Control Panel... Classic View... Programs and Features. Right click on your version of Microsoft Office 2013 and choose Change. Choose Add or Remove Features.

On Windows 7, go to Start... Control Panel... Uninstall a program. Right click on your version of Microsoft Office 2013 and choose Change. Choose Add or Remove Features.

Make sure .NET Programmability Support is set to "Run from My Computer" as shown in the following image:

Updated Wiki: Office 2013 Primary Interop Assemblies

furmangg — Sat, 28 Jul 2012 19:44:18 GMT

Office 2013 Primary Interop Assemblies

Installation Instructions

Updated Wiki: Office 2013 Primary Interop Assemblies

furmangg — Sat, 28 Jul 2012 19:43:50 GMT

Office 2013 Primary Interop Assemblies

Installation Instructions

Updated Wiki: Troubleshooting Installation

furmangg — Sat, 07 Jul 2012 15:38:13 GMT

Troubleshooting Installation

This page is the guide for troubleshooting installation issues with OLAP PivotTable Extensions.

Restarting Excel After Installation

The first thing to try is to restart Excel. If you install OLAP PivotTable Extensions while Excel is open, it must be restarted. Close all Excel documents and close Excel. Then open Excel again to see if that solves the problem.

Is Your PivotTable an OLAP PivotTable?

If you click on the PivotTable then press Alt-F11 then Ctrl-G then paste the following into the Immediate window and press enter:

?ActiveCell.PivotTable.PivotCache().OLAP

Does it say True?

If not, then you PivotTable is a native PivotTable that's summarizing some table or other data in the spreadsheet or SQL table. You have to have an OLAP PivotTable (that is, one connected to an Analysis Services server) for my add-in to work.

Repairing the OLAP PivotTable Extensions Installation

Starting with Release 0.7.0, the installer should fix all of the issues listed below. So if OLAP PivotTable Extensions is not working, try to repair the installation as follows, and that should fix the problem.

On Windows XP, go to Start... Settings... Control Panel... Add or Remove Programs. Click on OLAP PivotTable Extensions and click Change, on the next screen choose to Repair OLAP PivotTable Extensions, and click Finish.

On Windows 2003, go to Start... Control Panel... Add or Remove Programs. Click on OLAP PivotTable Extensions and click Change, on the next screen choose to Repair OLAP PivotTable Extensions, and click Finish.

On Windows Vista or Windows 2008, go to Start... Control Panel... Classic View... Programs and Features. Right click on OLAP PivotTable Extensions and click Change, on the next screen choose to Repair OLAP PivotTable Extensions, and click Finish.

On Windows 7, go to Start... Control Panel... Uninstall a program. Right click on OLAP PivotTable Extensions and click Change, on the next screen choose to Repair OLAP PivotTable Extensions, and click Finish.

Manual Troubleshooting

If you prefer to troubleshoot the installation manually, then use the following information and screenshots. Note, with Release 0.7.0, the following screens will say "OlapPivotTableExtensionsShim.dll" instead of "OlapPivotTableExtensions.dll.manifest".

Is It Disabled?

The first thing to check is whether OLAP PivotTable Extensions is disabled. Click on the Office button (in the top left) and choose Excel Options. Click on the add-ins tab, then scroll down and see if OLAP PivotTable Extensions is disabled:

If it is disabled, then select "Disabled Items" from the Manage dropdown at the bottom and click Go. Then enable the add-in using this dialog:

Then check whether the add-in is inactive using the following instructions.

Is It Inactive?

Then check whether OLAP PivotTable Extensions is inactive. Click on the Office button (in the top left in Excel) and choose Excel Options. Click on the add-ins tab, then scroll down and see if OLAP PivotTable extensions is in the inactive list:

If it is inactive, then select "COM Add-ins" from the Manage dropdown at the bottom and click Go. Then check OLAP PivotTable Extensions and click OK.

Then repeat the instructions above making sure it is now active, not inactive.

Is It Recognized By Excel?

If you have installed OLAP PivotTable Extensions version 0.7.0 or higher and still OLAP PivotTable Extensions doesn't appear anywhere in the list of add-ins above, then the installer may have failed. Uninstall OLAP PivotTable Extensions, then reinstall using the following method (instead of running the EXE).

Open a command window (on Vista or later, by right clicking and running the command prompt as an administrator) then CD to the appropriate directory with the MSI from the installer and run the following command:

msiexec /i "%TEMP%\OlapPivotTableExtensionsSetup\OlapPivotTableExtensionsSetup.msi" /log install.log

Post that log file under the Issue Tracker tab.