The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi All
I´m adding perspectives to some of our Semantic Models.
I´ve when working on one of our models two Tables with column and Measures I worked on in a previous model show up in the Perspective. They are marked with ! in yellow dimond and obviously don´t work.
I´ve tride deleted Perspective republishing then added Perspective again and republishing but can´t get rid of erroneous Tables, Columns and Measures, they refuse to disapear.
Any Ideas what is causing this and how to solve it?
Solved! Go to Solution.
Thanks for reply
Turned out that perspective worked fine when I published an Other report using same perspective.
So the solution I ended up using were to recreat original report and publishing it.
Hope this will help if someone gets same issue.
Can add that I have retrived the .bim from services using Tabular Editor and erroneous tables don´t exist in perspective in .bim
Hi,@Mary78
Regarding the issue you raised, my solution is as follows:
1.First, you can try clearing the cache using the modeling tool you're using (e.g., Power BI, SSAS).
Here is the official link:
Solved: Data Cache Management Options - Microsoft Fabric Community
2.Second, make sure that there are no dependencies or references to these tables, columns, or measures in your model. Sometimes, other calculations or relationships can cause them to persist. Of course, duplicate naming can also cause the same problem.
Here are links to similar issues:
Solved: Unable to delete measures after changing data sour... - Page 2 - Microsoft Fabric Community
3.Finally, try deleting and reposting.
Perspectives in Analysis Services tabular models | Microsoft Learn
At present, the resources we can find are as above, I hope it will be helpful for you to solve the problem, of course, if you have new discoveries, please feel free to contact us.
Best Regards,
Leroy Lu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thanks for reply
Turned out that perspective worked fine when I published an Other report using same perspective.
So the solution I ended up using were to recreat original report and publishing it.
Hope this will help if someone gets same issue.