Hi Mynda,
I use Microsoft Office Professional Plus 2013 in workplace. I built a dashboard with power pivot, which works perfectly.
However a few days later, when I tried to open it, I got below message "we found a problem with some content in 'PL Dashboard xlsx'. Do you want us to try to recover as much as we can? if we trust the source of this workbook, click yes.
After clicking yes, there is another message pop up, i have attached it here for your review.
The file was finally open, but all dashboard are gone, the pivot tables have been changed to hard code, the connected data source is also gone.
What make it even weird is that if I open the file on my home computer, ( using different excel version), it works perfectly.
Is there Excel version issue or some sort of IT security setting issue?
Thanks
Hi Vivian,
What version of Excel do you have at home? What version of Excel did you build the report in? Has the report been opened in a different version of Excel prior to the error message?
Yes, there are incompatibility issues between Excel 2010 and 2013 onward as they Power Pivot model was an add-in in 2010 and fully integrated in 2013 onward.
Mynda
I used latest Microsoft at home, I built the report at work using Microsoft Office Professional Plus 2013, it works perfectly and I also could open it after building. The problem was just happened yesterday. And the report has not been opened in a different version of Excel prior to the error message?
I could not open it at work and took it home for testing, which i found out i could open it at home.
Is there anyway i could fix it or i have to rebuild it?
Also how to prevent this kind of problem in the future, it would be embarrassed that if manager open it and dashboard is gone 🙁
Hi Vivian,
I don't know what would be causing this. After opening it at home, did you save it and then try opening it at work again to see if that fixed it? You can send it to me to see if I can reproduce the issue.
Mynda
Microsoft Office Professional Plus 2013 is a very weird version, i would just rebuild it, hopefully it is a one off issue.
If problem come back, we could go from there.
thanks for help
