-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feedback from users #12
Comments
Hello! Thank you a lot for the work you've done, your project helps me in my Power BI workflow so much! I would like to ask if there is currently a way to use LibPQ on Power BI Service? |
Thank you for your feedback! I'm glad you find LibPQ useful :) I have never tested LibPQ with PowerBI service, and I have no access to the service to do such tests. When I started writing this reply my initial idea was that LibPQ should work fine as long as you use only web sources in LibPQPath, but then I did some googling... It seems that the base URL for Web.Contents has to be static, which is not the case for LibPQ at the moment. I have some ideas on how to fix that, but I will need your help to test the changes in PowerBI service. Please join me here 👍 |
LibPQ disabling Power Query intellisense?I apologize if I'm missing something, but it appears that adding LibPQ breaks the Power Query intellisense. In Excel workbooks where I don't have LibPQ/LibPQPath, I get the intellisense function list, arguments, etc. But for those where I've integrated LibPQ, the intellisense only reads objects that were defined within the existing module. Almost all my work is done directly in M in the Advanced Editor. Having intellisense makes that process easier, but now that I've discovered the wonderful LibPQ, I don't want to give that up either! Any suggestions? |
Hello! If you are using LibPQ (or have used, or have tried to use it but something didn't work out for you) - please leave some feedback in comments below.
Any feedback beside the three points above is also greatly appreciated! Thank you!
The text was updated successfully, but these errors were encountered: