| Summary: | [FILEOPEN] Not perfect import and very slow import | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | sdaniele78 |
| Component: | Calc | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | jmadero.dev, miguelangelrv |
| Priority: | medium | ||
| Version: | 4.0.3.3 release | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Attachments: | File Excel with import problem | ||
|
Description
sdaniele78
2013-05-12 19:02:36 UTC
Created attachment 79207 [details]
File Excel with import problem
(Ubuntu 12.04 64bit - LibreOffice downloaded from website) We use the attached excel file everyday with M$ Excel. I tryied to import it with Calc and: - it is very slow. after convertion is quick - the conversion is not perfect: for example in the "Items" sheet, cell "G2". I must modify and add an extra space at the end of formula to made formula works Extra: - it will be nice if, after inserting formula, formula will be beautified Thank, Daniele Hi sdaniel78, seems to be a some issues there. With Win7x64 Ultimate. Version 4.0.3.3 (Build ID: 0eaa50a932c8f2199a615e1eb30f7ac74279539) In many places like: - Hours. column J seems that it must be an array formula and it is not. - SprintProgress_1. columns D-E-F and other must be also array formulas. Can you confirm, there are array formulas in the original file in those columns. - Hours. column H between others has an 508-Error: in bracketing without any apparent reason. About slow import, please try deleting the conditional formatting in Excel before import in Calc (I have not excel to do it). You are right: columns you said (and other columns too) are "array formula"/"matrix" and showed as:
{=MAX((A$2:A2)*((C$2:C2)=C3))}
(in Excel you can do it with Ctrl+Shift+Enter).
Columns H has no error (in Excel).
About slow import, I reported it because I think there are something that doesn't work in LibreOffice.
Daniele
infos added We need to keep bug reports more precise - one report should be one bug "not perfect import" isn't very helpful for a title. If there are multiple problems with the same sheet, please open more than one bug report for it and relate them in the "See Also" section. I know this can be tedious but it helps tremendously for triaging and fixing bugs. Also tell us EXACTLY what to look for, saying it is imperfect leaves us guessing. Mariosv took some time looking at it but still, is this what you were alluding to with "not perfect import" - formulas are wrong? Or is it conditional formatting? I'm tempted to mark as INVALID and start from scratch but I will mark as NEEDINFO - please give us ONE bug to focus on, edit the title to reflect this, tell us exactly where to look on the document and then mark bug as UNCONFIRMED. Then if there are more issues, open additional bugs that are detailed and specific to a single issue. Thanks for taking the time to help us out, very much appreciated but in order to do accurate and efficient triaging, we need one bug report = to one bug with easy to follow steps/guidance. Thanks! I create this new bug, more specific: https://bugs.freedesktop.org/show_bug.cgi?id=65835 You can invalidate this one (#64504). Also, I check better and there are no problem with conversion, it is only slow. |