Line charts no longer connecting the dots

There seems to be an update earlier this week where line charts seem to no longer be connecting the dots. I'm using a smoothed line chart here and the dots used to be connected, but are no longer. There is no option under the chart properties for changing how missing data points are configured. Interestingly... different people in our organization have started to see this behavior at different times, which makes me think it's a client-side (javascript) change that has rolled out gradually.

rtruxlerwf_0-1717676682927.png

 

 

Solved Solved
1 2 998
1 ACCEPTED SOLUTION

I was able to find a solution. The regression appears to be further related to the fact that my X axis is a floating point number (it was tenths of hours). When I truncated the division of hours to 4 decimal places, the visualization started behaving again. This leads me to think that there's some change in number handling (perhaps in key generation or sorting of x values) in the javascript visualization code that was messing things up. I was able to replicate my issue with a bigquery public data set, then also fix it using truncation.

View solution in original post

2 REPLIES 2

I posted this in reddit as well because I couldn't see my post here at first. It looks like my post is now live, so I'll add a couple of updates here.
https://www.reddit.com/r/LookerStudio/comments/1d9hs9r/bug_with_latest_looker_studio_line_charts_and...

This issue appears to be localized to using breakdown dimensions to add multiple series. If you remove a breakdown dimension, it connects the dots. So the workaround here is to avoid breakdown dimensions in line charts, which means to achieve the same result, you'd have to create one new metric per dimension you want to break down by. This is not sustainable for many charts, but could work for a small number of dimensions.

 

I was able to find a solution. The regression appears to be further related to the fact that my X axis is a floating point number (it was tenths of hours). When I truncated the division of hours to 4 decimal places, the visualization started behaving again. This leads me to think that there's some change in number handling (perhaps in key generation or sorting of x values) in the javascript visualization code that was messing things up. I was able to replicate my issue with a bigquery public data set, then also fix it using truncation.