Forum Discussion
Query Editor requires credentials?
- 9 years ago
Hi CahabaData,
I got the information from PG that
The query editor cannot read the data stored in the data model. Even if it could, the data in the data model represents the output of the very last step and the query editor wants to be able to show partial output for intermediate steps. That data is never loaded into the data model.
No passwords are stored in the pbix file. The credential for the data source are stored on the machine which have the .pbix created C:\Users\<user name>\AppData\Local\Microsoft\Power BI Desktop\User.zip.
Best Regards,
Qiuyun Yu
Hi CahabaData,
Based on my test in Power BI desktop latest version 2.45.4704.722, create a report use Import mode to get data from the SQL views, either set Windows authentication or SQL Server authentication, after copy to the other machines, we can see the report data when open the .pbix in other machines. But if we want to refresh or open Query Editor, it requires enter credential to connect to data source, because both Refresh and Query Editor is used for connecting data sources, we need to enter valid credential again.
Best Regards,
Qiuyun Yu
- CahabaData9 years agoMemorable Member
Thank you for the reply.
I definitely can understand that one cannot refresh without the credentials in this scenario.
But the restriction of opening the Query Editor does not seem a correct design. There is no inherent linking needed/done to the data source when manipulating/modeling imported data (as I understand) as this is not a Direct Query scenario.
I think many of us that are mobile need to take a pbix file with us and refine the modeling when working in another location - ultimately returning that pbix file to its original location for the linking/refresh.
- v-qiuyu-msft9 years agoCommunity Support
Hi CahabaData,
I have sent a email to consult this scenario internally, will update to you if get feedback.
Best Regards,
Qiuyun Yu- CahabaData9 years agoMemorable Member
Thank you for that update - I appreciate your follow through. I think this issue will be key to the user community.