on
RE:
agreed and upvoted!
RE:
I couldn't agree more with this frustration. Even when using the tenant ID to connect, there still seems to be some leakage from the user's parent organizational workspace (e.g., Connections appear even when on the client tenant). Often, refreshes end up pulling the user back to the parent workspace, as well. It makes supporting clients less than ideal without asking them to create an internal user account, leading to its own challenges.
RE:
A must-have feature for retailers.
RE:
Would be great if those improvements would be available for both lakehouse & warehouse destinations... as currently in the copy activity with a lakehouse destination I can at least choose between "append" and "overwrite" whereas with a warehouse destination I do not have this option and need to use a pre-copy script in order to truncate the destination table for example.
RE:
Hey Power BI team, get your act together and finally implement this useful and simple feature!!!
RE:
This is still very much needed. The barcode scanning to apply a filter works great. We just need the same scanner to be able to read QR codes as well.
RE:
Agreed. This is super difficult for partners to work efficiently across multiple clients. Also, orgs with multi-tenant environment.
RE:
The current functionality of removing the email record is a large efficiency loss for my team and a setback as we migrate to the Dynamics platform. It does not build confidence in the use of a new CRM system when a 20 year old, outdated platform allows more functionality.
RE:
In an ideal scenario, customers would be able to generate an embed token via API for a report using a DirectLake dataset using either a service principal and master user using the https://api.powerbi.com/v1.0/myorg/groups/{{workspace_id}}/reports/{{report_id}}/generatetoken or https://api.powerbi.com/v1.0/myorg/generatetoken endpoints.
RE:
will this be taken into consideration any time soon?