Created attachment 41074 [details] Error notification upon refresh I cannot refresh datapilot table in LibO. I have made (in OOo) file with several sheets and several datapilot tables. When using file in OOo no problem exists. After saving the file in OOo and opening in LibO, I cannot refresh the datapilot tables anymore. I get an error upon refreshing (see attachment). When reviewing datapilot settings (right mouse button, start), all fields which form the table have disappeared. After reopening the file in OOo shows normal behaviour again. Example file also attached.
Created attachment 41075 [details] Datapilot error example file.
Just did an extra test with Windows and Ubuntu. Same behaviour persists when running LibO and OOo on Ubuntu. OOo doesn't show any problems. LibO just doesn't allow to refresh.
Have done some extra things with the datapilot. Seems quite troublesome how it behaves. Somehow there seems to be a relation with empty cells in the header column. When I copy the source range from a different datapilot table into the "Selection from" field, then suddenly the list with fields is setup. When I try to select the fields and draw them to the desired fields area, then nothing happens. When I press OK, then the table is rebuild with the initial settings I used before. The behavior seems to be very inconsistent.
Did somebody check this issue already? Should I check it in RC3? It has a relation to Bug 30670 (which is now closed due to lack of example document), but that one has a different scope. In this one I provided the examples.
When you say "open in OOo", which version do you mean? 3.2.1 or 3.3 RC?
OOo 3.2.1 on Ubuntu (just checked again) Same version probably under Windows (but that's been a month ago and in the time I've uninstalled OOo since I was running out of space to be able to install LO).
Yeah, in this case, the error message is precise and to the point (which is rare, but hey this is one good news!). I'll look into it to see there is anything we can do about this.
At least I can say that the data pilot implementation has changed a lot in OOo for 3.3, and we also got that change from there. And one of those changes that it disallows fields with no name, which is affecting your document here.
Well knowing that, I can understand the notification :) Changing that indeed solves it, but the performance is not as good as in OOo. Oh well, at least I now have a work around :)
Well, after giving this a lot of thoughts, my conclusion is to not allow empty field names, which means we won't be able to solve this issue. Empty field names cause a lot of grief in my places, so it's better to set that expectation up-front than causing problems in other areas. Sorry about this.
(In reply to comment #10) > Empty field names cause a lot of grief in my places, ^^ I meant to type "many places"