Office 2013 & PowerPivot Issues


Had some issues reported to me the other day regarding some PowerPivot dashboards running in Office 2013 that had originally been created in Office 2010 – I am not running Office 2013 yet but obviously I am going to have to get another virtual machine running on my machine with Office 2013 on it to test a few things as a quick search online revealed Microsoft’s list of known issues with PowerPivot and Excel 2013

Yikes…..that’s a fair list of issues identified already for something going out the door.   But I guess it could be much worse.

But for those who click on the above link, you will find the below specific known Excel 2013 & PowerPivot issues listed in there :


Strange behavior when PowerPivot for Excel 2010 add-in is enabled

If you install Excel 2013 on the same computer where Excel 2010 has the PowerPivot for Excel 2010 add-in enabled, Excel 2013 enables the wrong version of the PowerPivot add-in. You might get several different error messages when opening a workbook containing a PowerPivot model and you can’t make any changes.

Workaround Click File > Options > Add-ins to disable the PowerPivot for Excel 2010 add-in and enable the PowerPivot for Excel 2013 add-in. Only the 2013 version of the add-in will work with Excel 2013.


Workbook won’t upgrade when a new connection is created before upgrading

If before you upgrade a workbook, you create a new connection by clicking Data > Connections > New Connection, you won’t be able to upgrade the workbook.

Workaround Don’t create a new connection before upgrading. First upgrade, and then create the connection.



Unexpected Fields visible in the field list after upgrading a workbook

After you upgrade a workbook in PowerPivot, a “_Count of [Table Name]” calculated field appears in the Field List for each table.

Workaround The field disappears after you refresh the table in PowerPivot or Excel.



Lost diagram and calculation area layout after upgrading a workbook

After you upgrade, diagram and calculated field grid layout and settings are lost in PowerPivot. But no actual data or calculated fields are lost.

Workaround No workaround is available.



Importing data feeds in PowerPivot causes a message about exceeding the maximum received message size

When you import an OData data feed, you might get the following message:

The following exception occurred while the managed IDataReader interface was being used: The size of the received message has exceeded the maximum received message size of 1048576 bytes, increase the Max Received Message Size value on the connection string and try again.

Workaround To import this data feed successfully, change the MaxReceivedMessageSize in the advanced properties of the connection to the OData feed to “4398046511104” (without the quotation marks).


Upgrading PowerPivot workbooks with linked tables

If you used the PowerPivot add-in in Office 2010 to create a workbook with linked tables, when you upgrade the workbook to Excel 2013, you can’t refresh the data in the upgraded workbook.

Workaround Delete the tables and recreate them in Excel 2013.


KPIs from 2010 not working in 2013

If you used the Office 2010 PowerPivot add-in to create a workbook with key performance indicators (KPIs), when you upgrade the workbook to Excel 2013, the workbook can’t be used.

Workaround Use the Office 2010 PowerPivot add-in to remove the KPIs from the workbook before you upgrade it. Change the KPI to a calculated field before upgrading to keep the DAX formula, and then make it into a KPI in Excel 2013.



G’night, Brad


About bradosterloo

.NET Software Developer working for Innovative Systems, LLC in Mitchell, SD
This entry was posted in BI, PowerPivot and tagged , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s