Forum Discussion
Helper IIMany restrictions in Desktop
Hi,
I have several limitations in Power BI Desktop which our IT department/PBI Admins don’t know how to solve.
Field parameters etc is greyed out:
Data view is missing:
Semantic model not appearing despite being on the October release.
Why is a Directquery connection needed for accessing Power Query? And can I mess up anything by adding a local model?
We use Import mode and our data model is stored in SQL Server.
Please note that everything that needs to be activated in PBI Desktop is already turned on.
Do you know why we are so restricted at my organization?
Thanks!
mrclay82 , yes that's why you're limited, in order to have these access you want , it should be worked on the published dataset.
so you need to download the power bi file that have the dataset from power bi service and do the changes in it.
because in your scenario, you're just reading the data from the dataset in service, but you don't have them in your file.
8 Replies
- Idrissshatila
Super User
Hello mrclay82 ,
are you sure you're reading directly from a sql server, because it looks like it's reading from a power bi shared dataset from power bi service.
as this https://learn.microsoft.com/en-us/power-bi/connect-data/desktop-report-lifecycle-datasets
mrclay82No, sorry. You are correct. I am connecting to a dataset on PBI Service. What I meant was that the datamodel/dataset somehow is stored in SQL Server and published to Service.
- Idrissshatila
mrclay82 , yes that's why you're limited, in order to have these access you want , it should be worked on the published dataset.
so you need to download the power bi file that have the dataset from power bi service and do the changes in it.
because in your scenario, you're just reading the data from the dataset in service, but you don't have them in your file.