Jon von der Heyden
MrExcel MVP, Moderator
- Joined
- Apr 6, 2004
- Messages
- 10,907
- Office Version
- 365
- Platform
- Windows
Hi
I have another issue I cannot figure out. My colleague is building pivot tables in Excel by going Data > Get Data > From Power Platform > From Power BI.
The pivot tables effectively read from a shared Dataset.
Everything is fine initially, though an unknown trigger causes the Pivot Table to lose connection, and even stop working as a pivot table. I.e. when activating it, the Pivot Table ribbons don't activate. Right-click contextual menu on pivot shows the Pivot Table controls, but they are all greyed out. The grouping buttons in the Pivot remain visible, but do not do anything. The connection to the dataset is still visible in the connections pane; so it is still there.
I have attempted running Refresh, but it does nothing. I have checked trust center settings and the config relating to connections seems fine (set to prompt).
Any idea what is happening?
Thanks
Jon
P.S. worth mentioning that I do not witness this behaviour in any of my own reports. I have one single colleague that is impacted by this (AFAIK).
I have another issue I cannot figure out. My colleague is building pivot tables in Excel by going Data > Get Data > From Power Platform > From Power BI.
The pivot tables effectively read from a shared Dataset.
Everything is fine initially, though an unknown trigger causes the Pivot Table to lose connection, and even stop working as a pivot table. I.e. when activating it, the Pivot Table ribbons don't activate. Right-click contextual menu on pivot shows the Pivot Table controls, but they are all greyed out. The grouping buttons in the Pivot remain visible, but do not do anything. The connection to the dataset is still visible in the connections pane; so it is still there.
I have attempted running Refresh, but it does nothing. I have checked trust center settings and the config relating to connections seems fine (set to prompt).
Any idea what is happening?
Thanks
Jon
P.S. worth mentioning that I do not witness this behaviour in any of my own reports. I have one single colleague that is impacted by this (AFAIK).