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

Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!

Line Charts with Constant Lines are not displaying properly in the Service

We have lots of reports that use Line Charts with two Constant Lines to mark the "Good" (97) and "Acceptable" (93) levels.

 

Starting today this charts are not displaying properly in the Power BI Service (in Desktop they look fine).    The charts are only displaying the range between the two constant lines (93-97).    Any values that fall outside this range can't be seen.

 

The Y-axis Start and End are set to Auto.

 

This is happening with reports that updated today as well as with reports that have not been updated recently and that used to display properly.

 

Republishing the reports has not helped.

Status: New
Comments
DrDon
New Member

I am having the same issue with all but the trend line.

Anonymous
Not applicable

Issue seems to have been fixed for me guys. Can you check from your end and confirm?

Anonymous
Not applicable

Yes all fixed for me now 👍🏼

leoPBI
Advocate II

Yes, fixed for me too.
Not heard from MS on this, but glad it got fixed 🎉

Anonymous
Not applicable

Issue fixed for me as well ✔️ 🎉

DrDon
New Member

Did not fix it for me.  I am displaying a AVG constant line: 

Before:

DrDon_0-1604356052427.png

 

 

After publishing:

DrDon_1-1604356168416.png

 

 

Anonymous
Not applicable

I had this issue too. Seems to be resolved. 

albertginete
Advocate I

This issue seems to have recurred. This happens to me in my scatter plots.

Did you guys notice its recurrence?

 

I reported an issue thru here:

https://community.powerbi.com/t5/Issues/BUG-Scatter-plot-X-and-Y-constant-lines-are-not-displayed-in...

 

Regards,

Albert

LFilipeDJ
New Member

I am having the same problem with bar charts, the constant line is there in the Desktop, but once I publish it disappeared in the report in the Server

albertginete
Advocate I

I was told here that this will be fixed on June. Looks like we'll just have to wait.

 

Regards,

Albert