cancel
Showing results for 
Search instead for 
Did you mean: 

USERELATIONSHIP Bug when using Live Connection (SQL 2014 compat. 1103)

While doing a very simple operation that has worked for me in the past countless times, I ran into a bug when using Power BI and a live connection to a Tabular model.

 

It seems that when multiple relationships have been created on a datefield, and you have used the USERELATIONSHIP function, it will not always work properly in Power BI - Live Connect. The bug only happens in this combination:

Power BI - Other sources = Expected Behavior

Power BI - Live Connection SASS Tabular = Bug

Excel - Other sources = Expected behavior

Excel - Connection SASS Tabular = Expected behavior.

 

As a result, I cannot include an example file (as it will work properly in that case and the bug will not show). I did fake the situation in Excel, show you can show what I mean:

 

001.pngExample (Datamodel)002.pngExample (Report)

Status: New
Comments
Frequent Visitor

Thanks a lot! Appologies for my lack of patience, we're just very eager to continue! Smiley Happy

Moderator

Hi @JesperP,

 

The issue doesn't occur if we get the data from the latest SSAS 2017 version 14.0.226.1 (CU10) in Power BI desktop 2.62.5222.601 64-bit (September 2018). Please file a QFE request against the SSAS server product if they don't want to upgrade. To file a support incident, the user can start from https://support.microsoft.com/en-us. 

 

Best Regards,
Qiuyun Yu 

Frequent Visitor

Hi Qiuyun Yu,

 

Obviously we would very much like to upgrade to SSAS 2017, but we've already invested quite a lot in the 2014 license (purchased it not long before 2016 came out at the time).

 

This is a feature that is supposed to work on SSAS 2014 + Power BI as well. So it would make sense to me it should get fixed, or you should provide us with an alternative solution. We'd be interested to discuss a posibile discount for an upgrade and be done with it. We've invested time to very clearly documented the issue, and have been waiting more than a month, without a clear sign of a solution. Our project is complety on hold.

 

I do not think it is fair of you to ask me to file yet another bug at another team and start at zero again. besides that, i have no idea what a QFA request is, and in the link you've provided I do not see any input form.

 

I really hope we can come to a solution, I've been an active Power BI user from the start, and have always been very enthusiastic about the product. 

Moderator

Hi @JesperP,

 

Sorry for the late response. 

 

As the SQL Server 2017 doesn't have issue while SQL 2014 has, it make sense to get a QFE for SQL 2014 on SQL side. Please open a ticket to SQL server in this site: https://support.microsoft.com/en-us/gp/support-options-for-business?wa=wsignin1.0&forceorigin=esmc. When you open the ticket to SQL team, you can share this Power BI incident for them to understand the issue better: https://icm.ad.msft.net/imp/v3/incidents/details/83934292/home

 

Best Regards,
Qiuyun Yu 

Moderator

Hi @JesperP,

 

You can create a SQL 2014 ticket in this site: https://support.microsoft.com/en-us/getsupport?wf=0&tenant=classiccommercial&oaspworkflow=start_1.0....

 

Best Regards,
Qiuyun Yu 

Frequent Visitor

Still no solution for this Smiley Sad