Hit Reply and let us know what you think of the DirectQuery for Power BI datasets and Azure Analysis Services. To learn more about this feature, please visit this blog post or our documentation.
Here are some areas that we'd like to hear about in particular:
Thanks and we look forward to hearing your feedback!
- The Power BI Modeling Team
@jeroenterheerdt Is it still necessary to give access to the compilation of reports with more than one set of PRO licenses?
Maybe this is a known bug? Refreshing two datasets where both datasets have a relationship between tables of the same name in both datasets causes a "Sequence contains more than one matching element" error.
I tried to workaround this (without renaming one of the tables) by setting the data load settings to not load in parallel, but no luck. (Given you can add the datasets individually without issue.)
BTW. discovered this when trying to pull together a report based on the two datasets, no fancy interlinking being done either.
NB: below pic has different table names showing, but underlying dataset has identical naming.
I did find it interesting that this is an issue given the table exclusion rules are being set by lineage tag.
Thanks for this, I've just started getting the same bug and couldn't work out what it meant - for me it happened when I tried to build a new report on top of the working model, any refresh of the new one hit this error message, while the old one carried on working.
While we understand that a developer would require build access to all datasets in the chain, it is unclear to us why a reader would also require build access to all datasets in the chain (why not just read access). To us this is the main reason why we cannot use this -otherwise great- feature at this point as this way we would not be GDPR compliant. Will this change? Or is there perhaps a workaround?
this was launched on April 4th: https://powerbi.microsoft.com/en-us/blog/update-to-required-permissions-when-using-composite-models-.... Please note that this is for Premium and PPU for now.
Hi - really pleased when this blog announcement came out. I had every user who needed access to anything as a Member of the Premium workspace. I've changed them all to Viewers but now multiple users are only seeing an error on any visualisation from 1 'base' dataset that's part of the composite model. They can see visualisation from the others datasets that make up the model in the same reports, just not that one. That report set is published by another user, from a SQL database, to the workspace. Is this a known exception or should I open a support ticket?
Good afternoon! How cool, our licensing here at the company is PRO, do you imagine that the resolution of the technical problems reported to enable the solution for PRO should be resolved soon?
Getting the below message while trying to link 2 tables in one dataset to a date dimension held in another dataset. Any plans to allow this behavour? or how would you suggest completing what would be a common scenario for us?