I simplify the problem as follows:

Given a Excel 2013 pivot table report with one dimension X linked to a slicer, sourced from SSAS 2012 tabular model (v11.0.3000.0), put on Sharepoint 2013, and viewed by Excel Service. If applying row filtering makes X become empty, the slicer will fail to refresh, halt the row filtering, and the report will display the cached information to the Sharepoint user.

My question is:

1) Why the slicer refresh fails if X becomes empty? Should it display "all values are filtered out"?

2) Is it possible to clear the pivot table caches and slicer caches before putting the report on Sharepoint 2013? That's may be my workaround if no solution can be found.

• Edited by MarioLeung Monday, July 07, 2014 3:44 AM Simplify the problem to make it easier understand
• Changed type Ed Price - MSFTMicrosoft employee, Owner Thursday, October 23, 2014 11:04 PM No response

Any suggestions for Mario?

Thanks!

Hi Ed.,

I have shortened my question to make it easier to understand. 

Hope someone could help me. Thanks!!!!!

Hi Ed.,

I have shortened my question to make it easier to understand. 

Hope someone could help me. Thanks!!!!!

Thanks Mario! That helps a lot.

Could someone take a look at these questions?

Thanks!

I asked for some more help. Thanks!

Mario, any progress with this?

Thanks!

Currently I have no solution. 

What I do as a workaround is to empty the power pivot cache before publishing, so that even if the refresh fails, users only see a report with no data.

In the future, we will move away from power pivot and use other BI technology like Power BI.