Forum Discussion
Advocate IIMeasures in different dataset not visible
Hi J94,
Thanks for followupIt looks like the issue is coming because the Sales table has been imported into the "4 bucket" report. When we use Import mode instead of a Live connection or DirectQuery, Power BI breaks the connection lineage with the original dataset. Because of this, some measures like MTD Month-To-Date or other time intelligence functions may not work properly when used with date fields. This is why your MTD value is only working when you don't add date columns in your visuals.
To fix this, I suggest these two options:
Use DirectQuery mode and connect to the Sales dataset directly, so the model can understand the relationship and time functions work correctly. Or, if Import mode is required, you may need to re-create the logic manually using DAX filters and calculations.
Hope the above provided information help you resolve the issue, if you have any further concerns or queries, please feel free to reach out to us.
Best Regards,
Harshitha.
Advocate IIHi Anonymous
Thanks for your extended reply and suggestions.
The dim_date[Date] does match with the Sales table dates. The relationship is active. I also plotted in seperate visuals with Date, YearMonth, Year, Month. Without success. And in my original Sales dataset, I can just plot the MTD measure without any date columns.
Can it be because table with sales is in import mode in the 4 bucket report (see image)? So the lineage (see image in my first message) goes like this: fact_salesinvoices > Sales dataset > 4 bucket
Maybe this can explain it, even though I am not sure why Sale value current month is visible...
Hi J94,
Thanks for followup
It looks like the issue is coming because the Sales table has been imported into the "4 bucket" report. When we use Import mode instead of a Live connection or DirectQuery, Power BI breaks the connection lineage with the original dataset. Because of this, some measures like MTD Month-To-Date or other time intelligence functions may not work properly when used with date fields. This is why your MTD value is only working when you don't add date columns in your visuals.
To fix this, I suggest these two options:
Use DirectQuery mode and connect to the Sales dataset directly, so the model can understand the relationship and time functions work correctly. Or, if Import mode is required, you may need to re-create the logic manually using DAX filters and calculations.
Hope the above provided information help you resolve the issue, if you have any further concerns or queries, please feel free to reach out to us.
Best Regards,
Harshitha.
- J94
Hi Anonymous
Thanks for your explanation. I've come to the same conclusion. So I am going to use DirectQuery to resolve this issue.
Thanks again and have a nice day