Forum Discussion
Deleted
Deleted
Thank you so much for all the suggestions it has been resolved now π
It was do with the workspace settings.When I published it in the same workspace it worked abosulutely fine.
Cheers
Arti
5 Replies
- AnonymousNot applicable
Hi agarwala ,
This looks like it has to do with the connection mode you have when you publish, and it may also have to do with the workspace permissions you are in, such as query caching.It is only available on Power BI Premium or Power BI Embedded, for Import semantic models. It is not applicable DirectQuery or LiveConnect semantic models that use Azure Analysis Services or SQL Server Analysis Services.
Hope it helps!
Best regards,
Community Support Team_ Scott ChangIf this post helps then please consider Accept it as the solution to help the other members find it more quickly.
- agarwalaHelper I
Thank you so much for all the suggestions it has been resolved now π
It was do with the workspace settings.When I published it in the same workspace it worked abosulutely fine.
Cheers
Arti
- AnonymousNot applicable
- agarwalaHelper I
Hello,
Thanks for getting back.
I am the workspace administrator and using Power BI Premium with import models.
Do you think it can be the version of tabular editor ?
I am using the latest version of tabular editor 3.
I am just concerned that this semantic model for which I am adding field descriptions is being used at a number of places by number of reports.
So it being overwriting the default settings of semantic model is bit suspicious to me and might need more regressive time for testing whihc I dont have currently.
Has someone tried using Tabular Editor 3 for this purpose?
Cheers
Arti
- AnonymousNot applicable
Hi agarwala ,
I have no experience using this, but I looked up the information for you:
Editing through XMLA endpoint | Tabular Editor Documentation
Hope it helps!
Best regards,
Community Support Team_ Scott ChangIf this post helps then please consider Accept it as the solution to help the other members find it more quickly.