Forum Discussion
Power ParticipantLakehouse and Power BI Aggregations
Hi DennesTorres
If you create a report in "live" mode, and then do "Make changes to this model", it is switching the report into a composite (aka proxy) dataset, to allow you to personalize/customize it.
That means you are going from:
Report -> Core Dataset, to
Report -> Proxy Dataset -> Core Dataset
Aggregations are not expected to work in the Proxy Dataset above, because the proxy dataset is running in SSO mode, and aggregations are likely to be dangerous in SSO mode. This is pretty standard behavior for datasets, so not really specific to Lakehouse.
Hi DennesTorres
If you create a report in "live" mode, and then do "Make changes to this model", it is switching the report into a composite (aka proxy) dataset, to allow you to personalize/customize it.
That means you are going from:
Report -> Core Dataset, to
Report -> Proxy Dataset -> Core Dataset
Aggregations are not expected to work in the Proxy Dataset above, because the proxy dataset is running in SSO mode, and aggregations are likely to be dangerous in SSO mode. This is pretty standard behavior for datasets, so not really specific to Lakehouse.
Power ParticipantHi,
What do you mean SSO mode? I missed the meaning of this, I don't think it's single-signOn.
Just to be sure weare talking about the same implementation, the proxy dataset is a composite one. The aggregated table comes from another connection, a SQL Endpoint connection.
If this doesn't work, it's just a bit strange it allows to configure the aggregation without any complain.
Kind Regards,
Dennes
Hi DennesTorres ,
SSO here means Single Sign On. Essentially it means: the user's credential (who opens the report), flows automatically through the system to the underlying source datasets.
Datasets in Direct Query mode against another core dataset are always in SSO mode.
Hope this helps. Please let me know if you have any further questions. Glad to help.