Bug 137522

Summary: Ability to save settings for importing data to Calc
Product: LibreOffice Reporter: Frants <220710>
Component: CalcAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: enhancement CC: libreoffice-ux-advise, miguelangelrv, xiscofauli
Priority: medium Keywords: needsUXEval
Version: unspecified   
Hardware: All   
OS: All   
Whiteboard:
Crash report or crash signature: Regression By:

Description Frants 2020-10-16 07:45:56 UTC
Description:
It is necessary to add the ability to save the settings for importing data into Calc. When importing many text files with different data structures, it is inconvenient to configure the import parameters in the "Text Import" window each time. It is more convenient to load the specification with the settings that were previously used into the "Text Import" window.  Such a function would be useful.

Actual Results:
Saving user time.

Expected Results:
Saving user time.


Reproducible: Always


User Profile Reset: No



Additional Info:
Unspecified
Comment 1 m_a_riosv 2020-10-17 19:53:06 UTC
If I'm not wrong the last used remains. And making the link permanent the imported files can be updated through Menu/Edit/Link to external files, and every file keeps their own import configuration.
Comment 2 Frants 2020-10-18 16:43:38 UTC
Yes, you are right, my proposal is not relevant. You mean the import path is Sheet -> Link to External Data? Still, an ordinary user needs to know about this path. Not all users know about this when they use the File → Open (* .txt) path. For example, in the question "How to remove automatic field separators in text import in Calc". In such a case, in the "Text Import" window, a link or option for using the "Sheet -> Link to External Data" mechanism would be useful. Maybe it would improve usability?
https://ask.libreoffice.org/en/question/211141/how-to-remove-automatic-field-separators-in-text-import-in-calc/
Comment 3 Heiko Tietze 2020-11-19 12:44:21 UTC
Issue is solved, similar/same discussion runs on bug 74580

*** This bug has been marked as a duplicate of bug 74580 ***