Aggregated Table - no options to select reference table in Manage aggregations

[szczawek]

Hello,

Hope it will be quick question but i can't find proper solution to it.
I have a simple model with date and PROD as dim and Fact. Fact Agg is aggregation of two columns from Fact (Value, Volume) by Date.
I would like to mark FactAgg as agregated column but all options are greyed. The data type of all columns are the same, relations use the same column in both cases.
Any idea why it is not working? all tables in this case are import from Excel (to test solution).

 Kind regards

[lbendlin · Accepted solution]

The standard implementation is to use a direct query data source for the raw table and have the aggregation be in import mode.  The point of aggregations is to avoid having to go back to the data source for the most common queries.

Most likely you will have to switch your tests to a SQL Server based data source.

[Anonymous]

Hi @szczawek ,

I wanted to check and see if you had a chance to review our previous response. Please let me know if everything is sorted or if you need any further assistance.

Thank you.

[Anonymous]

Hi @szczawek ,
Could you please confirm if the issue has been resolved on your end? If a solution has been found, it would be greatly appreciated if you could share your insights with the community. This would be helpful for other members who may encounter similar issues.
Thank you for your understanding and assistance.

[Anonymous]

Hi @szczawek ,
Thank you for the helpful response @lbendlin !
I wanted to check in on your situation regarding the issue. Have you resolved it? If you have, please consider marking the reply that helped you or sharing your solution. It would be greatly appreciated by others in the community who may have the same question.
Thank you.

[szczawek]

So in general if I have huge full import model (due to size and company policy) my only option for aggregation tables is to have one in model but i need to write propper DAX to use it as it can't be used when all tables are in import mode?

[lbendlin · Accepted solution]

If your data source is in import mode only then aggregation tables don't make that much sense (apart from the queries performing differently between the main table and the shadow table).  You can still implement the concept, but it is like with non-folding incremental refresh - you will only see half of the intended benefits.

[lbendlin · Accepted solution]

The standard implementation is to use a direct query data source for the raw table and have the aggregation be in import mode.  The point of aggregations is to avoid having to go back to the data source for the most common queries.

Most likely you will have to switch your tests to a SQL Server based data source.