![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: CSV/Excel/Spreadsheet import-export preserving RTF formatting Topic Summary: Created On: 3-May-2007 15:36 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi all,
I need to export data from DOORS into a csv or similar and import the modified data again. The problem is, with the standard spreadsheet import I lose all formatting such as bold, italic, strikethrough. In the telelogic kitchen I found the script "Import from CSV file preserving rich text". When called the script first displays a message which includes: "It assumes that the CSV file has been exported using the corresponding CSV/RTF exporter." Only I do not know where to find this corresponding CSV/RTF exporter. Besides the script seems to have a bug (like so many of the kitchen scripts). Does anybody have any hints, suggestions, ideas or maybe even a better solution to my problem? Karl |
|
![]() |
|
![]() |
|
In the kitchen scripts try the file exportdata.dxl
|
|
![]() |
|
![]() |
|
Hi Ron,
thanks for your reply. I tried the exportdata.dxl on one of my modules and without modifying anything imported the data again using importcsvrtf.dxl. On import I got the message that so many objects were created and so many objects were updated, and then DOORS hangs. Obviously and unfortunately this is not what I am looking for. Seems I have to keep on searching and trying. Karl |
|
![]() |
|
![]() |
|
In the hopefully near future, I plan to write an Excel Importer that preserves rich text.
------------------------- David Pechacek AAI Services Textron dpechacek@sc-aaicorp.com David.Pechacek@gmail.com Edited: 4-May-2007 at 13:43 by David Pechacek |
|
![]() |
|
![]() |
|
You have several options as follows:
-- Use importData.dxl from kitchen script -- Debug importcsvrtf.dxl -- the bug is in the progress bar. -- Disable importcsvrtf.dxl progress bar -- easiest solution is to put a progressStop() immediately after the progressStart. (Bug is caused because the function containing progressStart is called twice so two progress bars exist at the same time -- so if you must have a progress bar you could put progressStop before the progressStart to close the first progress bar before opening the second.) I was able to use: -- importData.dxl to import data from exportData.dxl -- importcsvrtf.dxl to import data from exportData.dxl after disabling progress bar(I tend not to use the progress bar, so I never took time to do a complete debug.) Edited: 4-May-2007 at 15:49 by ron lewis |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.