Hello: I'm looking for a way to export every module in DOORS with a custom view. This consists, of course, of two questions, and I'd appreciate help with either or both of them.
My DOORS database has more than 100 modules, so configuring the views one at a time is a suboptimal solution. I'd be willing to do the exports manually (much less time-consuming), but it'd be nice if there were a way around that, too. I'm pretty new to DOORS, so I apologize if this is a stupid question -- but I can't find anything in the documentation or anywhere else online. Thank you! -Stephen spcraft - Mon Jun 24 15:26:32 EDT 2013 |
Re: Global view and global export didn' t try it, right now, but for the first question you might want look at https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014917227. |
Re: Global view and global export That's great, thank you! It seems to work in my test environment, and I'll try it out in production tomorrow. It seems a little absurd that this functionality isn't built into DOORS; seems like it would be a common need (but then again, like I said, I'm new to this world, so I clearly don't know what I'm talking about :) ) Thanks again -- I appreciate the assistance. If anyone has any thoughts about the global export, I would love to hear them. -Stephen |
Re: Global view and global export spcraft - Mon Jun 24 17:19:52 EDT 2013 That's great, thank you! It seems to work in my test environment, and I'll try it out in production tomorrow. It seems a little absurd that this functionality isn't built into DOORS; seems like it would be a common need (but then again, like I said, I'm new to this world, so I clearly don't know what I'm talking about :) ) Thanks again -- I appreciate the assistance. If anyone has any thoughts about the global export, I would love to hear them. -Stephen well, in DOORS (classic, i.e. <= V9) every module has its own data model, so it can easily happen that module m1 has an attribute a1 and a view v1 which contains a1, but module m2 does not have a1 defined -- so, what shall happen when you copy v1 to m2? For reasons like this there are almost no built-in functions which work on many modules. About the export,I'm really unsure - there might be someone out there who hacked into the export function and provides a way to call it with the correct parameters in a batch, but you might have to resort to alternatives like WEXP, DocExpress, RPE or some published custom solution which I'm not aware of currently. Anyone? |
Re: Global view and global export Mike.Scharnow - Mon Jun 24 18:05:10 EDT 2013 well, in DOORS (classic, i.e. <= V9) every module has its own data model, so it can easily happen that module m1 has an attribute a1 and a view v1 which contains a1, but module m2 does not have a1 defined -- so, what shall happen when you copy v1 to m2? For reasons like this there are almost no built-in functions which work on many modules. About the export,I'm really unsure - there might be someone out there who hacked into the export function and provides a way to call it with the correct parameters in a batch, but you might have to resort to alternatives like WEXP, DocExpress, RPE or some published custom solution which I'm not aware of currently. Anyone? Yes, this sort of functionality is possible with DXL - we have been doing it for some time already. The DXL export script is called in batch mode from a Windows cmd or bat file. In the cmd/bat you set parameters you need for the export, such as a root dir/project from which to start exporting all modules (could be the db root as example). a module View Name, etc. The DXL then traverses through the folders/projects under the root and exports from formal modules using the view name you gave it. It exports to csv file(s) only those attributes which are displayed in your View Name parameter. Using a view name as parameter makes it very flexible - use same code for multiple export types, don't need to recode to change data exported (just change view), etc., There are some constraints, eg: you need to have the view in all modules (which means you need to have consistent attribute set in all modules using that view) or it does not export anything etc. The constraints are all things you would normally enforce anyway in any company that has its project execution under control. If your company doesn't then any tool is not going to help you. |
Re: Global view and global export BillTidy - Wed Jun 26 05:20:46 EDT 2013 Yes, this sort of functionality is possible with DXL - we have been doing it for some time already. The DXL export script is called in batch mode from a Windows cmd or bat file. In the cmd/bat you set parameters you need for the export, such as a root dir/project from which to start exporting all modules (could be the db root as example). a module View Name, etc. The DXL then traverses through the folders/projects under the root and exports from formal modules using the view name you gave it. It exports to csv file(s) only those attributes which are displayed in your View Name parameter. Using a view name as parameter makes it very flexible - use same code for multiple export types, don't need to recode to change data exported (just change view), etc., There are some constraints, eg: you need to have the view in all modules (which means you need to have consistent attribute set in all modules using that view) or it does not export anything etc. The constraints are all things you would normally enforce anyway in any company that has its project execution under control. If your company doesn't then any tool is not going to help you. Once, a looong time ago, I modified the standard Word, or was it Excel, export to open all of the formal modules in the current folder and su-folders, open a specific view and export that. As we had something like 300 modules, it took quite some time to execute! But as Bill said, you have to write the DXL for that.. /sekrbo |