Created attachment 115269 [details] Trendline not visible in chart I use pivot tables to create XY scatter charts. Once I realized that after reorganizing pivot table one of trendlines is not visible any more. The regression equation and R2 of the trendline shows certain values, which means that something is calculated. It is not possible to get visible trendline for that data set at any way except creating new chart. Trendline is not visible even if the chart is copied to another document. Sample chart, copied to another spreadsheet is attached to this report. Ubuntu 32 bit, Libreofffice 4.4.3.2
Created attachment 115281 [details] printscreen from 5.0 Printscreen of 5.0 I see red trend line, but I should see also blue trendline? I cannot add new trendline into data series E. Please attach test file with pivot table and chart.
(In reply to raal from comment #1) > Created attachment 115281 [details] > printscreen from 5.0 > > Printscreen of 5.0 > > I see red trend line, but I should see also blue trendline? Yes, that is missing. I cannot add new > trendline into data series E. Please attach test file with pivot table and > chart. Unfortunately, it is not existing any more. I deleted wrong chart from original file. The attached file is reconstruction of what I did. The first sheet contains original pivot and chart with 2 visible trendlines. Second sheet contains updated pivot and chart with visible 1 trendline. After changing pivot I rearranged data sources in the chart, but it didn't affect visibility of the second trendline.
Created attachment 115283 [details] Pivot tables with correct and wrong charts
Your charts are not linked to pivot table, they have own Chart data table. Please provide a clearer set of step-by-step instructions on how to reproduce the problem. thanks I tried to change values in Chart data table, copy table and trend line is still present.
Probably it is enough to consider a problem, because it is not possible to make visible trendline in the first attached file? As soon as I'll have same free time I'll create sample file.
I see what is causing the problem. Trendline is not visible when data for X is empty in 1st row of data table. Edit the chart with missing trenline and show data table. You will see no value X in row 1. Enter any value and the trendline appears.
Thank you! It looks easy to solve.
Created attachment 116313 [details] Example of chart with invisible trend line Description: Trendline not visible if first value of X-value is text. Steps to reproduce: 1. Enter XY data with a first line of text 2. Select data with labels in fist line and Insert Chart 3. In wizard, Select XY (Scatter), Next 4. Uncheck "First row as label" (label is now considered as data), Finish 5. Right click on the series > Insert Trend line (let default option), OK Actual behavior: Trendline is invisible Expected behavior: Trend line should be visible, as it is expected when you check trend line equation. A workaround is to modify Data Ranges, as indicated in Comment 6, to remove the first line from X-values, or to check "First line as label". Test made with Version: 4.3.7.2 Build ID: 8a35821d8636a03b8bf4e15b48f59794652c68ba
Confirmed with Version: 4.3.2.2 Build ID: edfb5295ba211bd31ad47d0bad0118690f76407d
Confirmed with Version: 5.0.0.0.beta1 Build ID: 0a16c3dda4150008d9be6f24cbd15ac198d116d3 Locale : fr-FR (fr_FR)
Confirmed with: - Version: 4.2.0.0.alpha0+ Build ID: cb14b1e56d2aab70d28afca8bf039a27f89671c8 TinderBox: Win-x86@6, Branch:master, Time: 2013-07-11_04:05:08 - Version: 4.2.0.0.alpha0+ Build ID: 4a8f7ddc290d1ea3131de6611b6833b77ac7ab1f (2013-08-28) - Version: 4.2.0.0.beta1 Build ID: f4ca7b35f580827ad2c69ea6d29f7c9b48ebbac7 - Version: 4.2.0.4 Build ID: 05dceb5d363845f2cf968344d7adab8dcfb2ba71 NOT confirmed with: - Version: 4.2.0.0.alpha0+ Build ID: 4ba92ec1d565848c86c5e802b30f17862ad6505f (2013-06-27) - Version: 4.1.6.2 Build ID: 40ff705089295be5be0aae9b15123f687c05b0a Note that equation is visible, but not the trend line. If file is exported to XLS, Excel is able to see the trendline. If file is opened with
*** This bug has been marked as a duplicate of bug 76649 ***