Forum Discussion
Advocate IProblems with Data columns with Live connection
Hi,
I'm using Live connection to on-premises SSAS Tabular 2019 and have some issues with Data columns. It seems that Power BI cannot understand their data type (it's decimal) and cannot perform any aggregations.
Some details:
- Data column properties:
- How I see it in Power BI Desktop:
- If I try to add Target column to a Chart or Card (that expect some aggregation) it can't be done, I simple can't select it. I can add it to the Table though, but it seems that it's been treated as Text, not Decimal.
- The only workaround I've come up with so far is to create a new measure Target_Measure = SUM('Fact_Target'[Target]), but I'd prefer to have it as a last resort and figure out the issue with Columns first.
Any ideas on what I'm doing wrong here? It works perfectly with the same model stored in the Power BI dataset in Import mode, not with Live connection.
Thanks,
Misha
I've figured out why that happened: there was a setting discourageImplicitMeasures set to be true in the on-premises Tabular model. Should have probably turned it on while experimenting with calculation groups. Problem is solved now.
6 Replies
- amitchandak
Super User
romanovmv , clear power bi cache from the options and try.
If not log an ticket at - https://community.powerbi.com/t5/Issues/idb-p/Issues
v-jingzhangCommunity Support
It looks weird. These columns lack the ∑ symbol and are not recognized as able to be summarized, which caused this unexpected result. Do you use the latest Power BI Desktop? Does this occur only on decimal columns or on other numeric columns either?
Best Regards,
Community Support Team _ Jing Zhang
romanovmvHi v-jingzhang and amitchandak ,
I use the latest version of Power BI Desktop with clean cache.
I think it's not a problem of Power BI, but the problem of MS SSAS Tabular (or maybe both). I've tried to connect to the same model from Excel and PBI Service but got the same result.
Interesting thing is when I've started to build the same Tabular model again from scratch - it worked fine. So what I'm planning to do now is to finish that new model so that it fully replicates the existing one step by step and try to capture which table (or measure, or relashionship, etc) causes this bug. I'll updated you with the result of my experiment.
Thanks,
Misha
- v-jingzhang
romanovmv Thank you for this info. Hope your experiment goes smoothly.
- romanovmv
I've figured out why that happened: there was a setting discourageImplicitMeasures set to be true in the on-premises Tabular model. Should have probably turned it on while experimenting with calculation groups. Problem is solved now.
