![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Need "Export all Modules to Spreadsheet" .dxl Topic Summary: Created On: 7-Nov-2002 19:53 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Hi, 1) To load a view you must have the module open and visible. Module mRef = read("my Mod",true) current Module = mRef View vn = view ("My View") if (load(vn)) { // It worked } 2) The standard Door->Excel Exporter is in open source code form and can be found at: <DoorsHome Dir> \lib\dxl\standard\export\office\excel.dxl Alternatively if you want to export to a CVS file then the code for this can be found at: <DoorsHome Dir> \lib\dxl\standard\export\comas.dxl Take a COPY of either of these and convert it into a function without the user interactions, etc and you will have a solution. | |
![]() |
|
I am looking for code that will automate the export of formal modules to .csv .
The looping-through-all-modules in a project part I've got. I'm missing the .dxl that shows how to 1. Select a view 2. Do a file-export-spreadsheet Anybody got this? Rob |
|
![]() |
|
![]() |
|
Hi,
1) To load a view you must have the module open and visible. Module mRef = read("my Mod",true) current Module = mRef View vn = view ("My View") if (load(vn)) { // It worked } 2) The standard Door->Excel Exporter is in open source code form and can be found at: <DoorsHome Dir> \lib\dxl\standard\export\office\excel.dxl Alternatively if you want to export to a CVS file then the code for this can be found at: <DoorsHome Dir> \lib\dxl\standard\export\comas.dxl Take a COPY of either of these and convert it into a function without the user interactions, etc and you will have a solution. ------------------------- andrew.myatt@telelogic.com ![]() |
|
![]() |
|
![]() |
|
Text file export is tricky. CRs and TABs in such a file are designed to separate different columns or lines in the export, yet they can also exist in exported Text attributes (such as Object Text) and have their standard meaning; but will mess up your export since they will be interpreted as column and line ending delimitors. I doubt using commas will help.
if you export to MS-Word you'll get the correct information, but they you want to manually replace existing TABs and CRs to some dummy string; perhaps Replace all "^p" with "**CR** ", Replace all "^t" with "**TAB** ". Then export as a text file. This will make the text report look odd but will preserve the integrity of the implied table format within the text file. - Louie |
|
![]() |
|
![]() |
|
Hello,
I'd like to export each and every module in a project to an excel file and save the excel file at a specified location. I'm using the DOORS provided script, excel.dxl to accomplish this and updated it loop through all the modules in the project. I've also tried specifying a view, but the script doesn't performed the desired action. I'd like the script to use the default view in every module; but, I'm not sure how to do it. I've attached the script. Could anyone please let me know what needs to change in the code to get the desired behavior. Thank You. Hi, 1) To load a view you must have the module open and visible. Module mRef = read("my Mod",true) current Module = mRef View vn = view ("My View") if (load(vn)) { // It worked } 2) The standard Door->Excel Exporter is in open source code form and can be found at: <DoorsHome Dir> \lib\dxl\standard\export\office\excel.dxl Alternatively if you want to export to a CVS file then the code for this can be found at: <DoorsHome Dir> \lib\dxl\standard\export\comas.dxl Take a COPY of either of these and convert it into a function without the user interactions, etc and you will have a solution. |
|
![]() |
|
![]() |
|
anant,
Trying chaning line: mod = read(path_name, false) to: mod = read(path_name, true) Also include a close mod after your done with the module. Edited: 12-Sep-2008 at 15:19 by ron lewis |
|
![]() |
|
![]() |
|
Ron,
I made changes you suggested. I see the modules opening in the background, that's all. It's not exporting the modules to an excel spreadsheet. Also, I want the "Default View" to be exported, not the standard view. Thanks. |
|
![]() |
|
![]() |
|
anant, If I read you right, you want to put every module output into a single excel file. This logic of this is not readily apparent to me. Since, in theory every module would have a different heading row.
Can you explain. To put the output of every module in its own excel file would seem more logical to me. Also, you might want to consider galatic exporter which includes ole objects in output. |
|
![]() |
|
![]() |
|
Actually, I do want each module to be a separate csv file (just got the clarification).
|
|
![]() |
|
![]() |
|
If you want csv files -- you need to abandon the excel source code and start with
file named commas.dxl |
|
![]() |
|
![]() |
|
Ron,
The commas.dxl doesn't have any comments in it. Also, does it need to be run on a module or a folder? I tried running it on both, a module and a folder, but nothing happens. |
|
![]() |
|
![]() |
|
I belive there are multiple commas.dxl on your client.
You want the one at ....\lib\dxl\standard\export\commas.dxl And it works from the module -- but you will want to change it to work at a project level. |
|
![]() |
|
![]() |
|
Ron,
Does the script also handle exporting of OLE tables? Thanks. |
|
![]() |
|
![]() |
|
CSV files offer no for Ole objects since a csv files is a text file.
Edited: 16-Sep-2008 at 12:49 by ron lewis |
|
![]() |
|
![]() |
|
Well, since we need the OLE objects as well, I'll have to do an export to Word.
|
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Need "Export all Modules to Spreadsheet" .dxl
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.