Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more

Reply
romanovmv
Advocate I
Advocate I

Problems 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:

  1. Data column properties:
    romanovmv_1-1608026340740.png

     

  2. How I see it in Power BI Desktop:
    romanovmv_2-1608026399207.png

     

  3. 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.
  4. 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

1 ACCEPTED SOLUTION

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.

View solution in original post

6 REPLIES 6
romanovmv
Advocate I
Advocate I

Hi @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

@romanovmv Thank you for this info. Hope your experiment goes smoothly.

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.

Thank you very much for this update. I believe it will help people who have similar problem.

I found an article about this setting and its limitation with Power BI for anyone who might want to refer to: https://docs.microsoft.com/en-us/analysis-services/tabular-models/calculation-groups?view=asallprodu...

 

v-jingzhang
Community Support
Community Support

@romanovmv 

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

amitchandak
Super User
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

Share with Power BI Enthusiasts: Full Power BI Video (20 Hours) YouTube
Microsoft Fabric Series 60+ Videos YouTube
Microsoft Fabric Hindi End to End YouTube

Helpful resources

Announcements
Power BI DataViz World Championships

Power BI Dataviz World Championships

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!

December 2025 Power BI Update Carousel

Power BI Monthly Update - December 2025

Check out the December 2025 Power BI Holiday Recap!

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.