Issue 55806 - Import of Word-document destroys contained fields
Summary: Import of Word-document destroys contained fields
Status: CONFIRMED
Alias: None
Product: Writer
Classification: Application
Component: open-import (show other issues)
Version: OOO 2.0 Beta2
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
: 97984 98468 (view as issue list)
Depends on:
Blocks:
 
Reported: 2005-10-12 09:09 UTC by wolfgangunger
Modified: 2013-02-07 22:33 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description wolfgangunger 2005-10-12 09:09:57 UTC 
First you should generate an empty Word-document (no matter if Word 2000, 2002 
or 2003). You have to insert a MERGEFIELD, the field code should be something 
like 
MERGEFIELD "ZMSD/Vorname" /ID:"020DATEV.FieldExchange.ZMSDMandant#Vorname#des#Ma
ndanten" /ATTR:N 

Hint: in MS Word you can toggle the visibility of field-codes with ALT+F9

Now that you inserted the field into the document you should save it in Word 
standard-document format (.doc).

After you re-open the file in Writer the additional information of the field-
code (ID and following information) is gone!
Even if you save this document as ODT and inspect the resulting XMLs you won't 
find a trace of the additional information.

Background: our software-solution for MS Office makes excessive use of these 
mailmerge-fields. If we don't find a way to transport the meta-data of the 
fields into the writer-documents we will find a remarkably lesser acceptance 
for the openoffice-based solution.
Comment 1 michael.ruess 2005-10-12 13:38:27 UTC 
Problem is, that the MailMerge / Database field interface between Word and OO
Writer is completely different. Writer needs a Word-like interface for better
compatibility.
Comment 2 wolfgangunger 2005-10-13 07:11:38 UTC 
At the moment you convert the MERGEFIELD into a MailMerge already. Form my 
point of view you will have to generate a new Fieldmaster + according Textfield 
for each word-MERGEFIELD. Otherwise it will be quite difficult to find the 
identical Word-MERGEFIELDS that could be treated as Textfields that belong to 
one Fieldmaster. But that's not the point.

Couldn't you store the whole Word-field-function in a separate Property of the 
fieldmaster?
This would help for compatibility as well - as soon as you have to export the 
document back into Word.doc-format...
Comment 3 wolfgangunger 2006-03-23 13:57:00 UTC 
Since OO 2.0.2 the original fieldcode is provided as a property of the field 
after the import (fieldname = "FieldCode").
After SAVE of the document this information is lost, but that's understandable 
and no problem for me.
Greetz, WU
Comment 4 michael.ruess 2009-01-12 16:01:52 UTC 
*** Issue 97984 has been marked as a duplicate of this issue. ***
Comment 5 mri0202 2009-01-16 07:05:41 UTC 
You wrote 'We are currently working on a solution as tracked in issue 55806'.

Do you have a timeline, when this problem will be solved (issue 55806 is from
2006). Otherwise, I have to find another solution.
Comment 6 michael.ruess 2009-01-26 19:57:03 UTC 
*** Issue 98468 has been marked as a duplicate of this issue. ***