Forum Discussion
Composite Model: If week number not on aggregation table, go back to fact table?
- Anonymous4 years ago
Hi swolfe2 ,
Sorry for that the information you have provided is not making the problem clear to me.
According to this: However, once a user selects a week that is NOT on the aggregation table, but is on the date table, DAX studio shows that it's still an aggregation hit and the measure returns null.
It shouldn't be possible for it to have found a match on the agg table since this week number doesn't exist on it.
Actually I think It's an expected behavior:
Best Regards,
Eyelyn Qin - 4 years ago
Yes, that's the same behavior I'm seeing on my side.
I suppose the DAX that's being generated is just looking for "Is there an aggregated column based off of the year?" and not also "Does this year exist on the aggregated table, too?".
Hi swolfe2 ,
Sorry for that the information you have provided is not making the problem clear to me.
According to this: However, once a user selects a week that is NOT on the aggregation table, but is on the date table, DAX studio shows that it's still an aggregation hit and the measure returns null.
It shouldn't be possible for it to have found a match on the agg table since this week number doesn't exist on it.
Actually I think It's an expected behavior:
Best Regards,
Eyelyn Qin
- swolfe24 years ago
Helper I
Yes, that's the same behavior I'm seeing on my side.
I suppose the DAX that's being generated is just looking for "Is there an aggregated column based off of the year?" and not also "Does this year exist on the aggregated table, too?".