SHARED DATASET: Composite model is not hitting the aggregate table.. why?

[plopper_n0k]

Hello - 

I have created a data model that has the past year of data saved in an aggregate table (import mode).  All aggregation settings are set up and when you work in the model pbix itself.. aggregate table hits.  Great.

Now - we want to publish this model to PBI Online and reference it in other workbooks but.. the aggregate table DOES NOT hit.

There are no RLS settings set up and the aggregate table is un-hidden yet.. when working in a "satellite" workbook connected to the shared dataset - the aggregate table is completely ignored.

I know it seems like the time difference is not substantial but as we get into more difficult queries - load time = 13-15 seconds.

Any ideas?

MODEL OVERVIEW:

Main table

Aggregate table

[GilbertQ]

Hi @plopper_n0k 

I would suggest taking the DAX query and running the same query in PBI desktop and to see why it is not working. Typically this could either be the DAX measure and the way that it is written. Or the way the data is modelled.

Unfortunately you will have to try different things to get it to work as expected. A bit of trial and error on your side due to your data being unique to you.

[plopper_n0k]

@GilbertQ thank you for the reply - for added context, I have copied the query and ran it in the "satellite" report connected to the shared dataset and cannot run DAX Studio (most likely due to XMLA settings which I have the admins looking into).  Would the XMLA settings also affect the query from hitting aggregate tables in workbooks connected to the shared dataset?

If I take the query and run it directly in the model pbix itself, no issues hitting the aggregate table:

[GilbertQ]

Hi @plopper_n0k 

You would need to use DAX studio when connected directly to the imported version of the report.

You could also use SSMS to connect via XMLA to the dataset and then use SQL Profiler to see if the agg tables are getting hit?