Author Topic: Import model issues (Read 6409 times)

malmoth · « **on:** January 11, 2005, 07:35:05 am »

Is it possible to import model issues from a .csv file?

Beside, I saw it was possible to export model issues in a .rtf file. Is it possible to do it in a .csv file?

That could be very useful to get rid of my stand-alone Excel table which I manage model issues with.

thomaskilian · « **Reply #1 on:** January 11, 2005, 11:18:23 am »

AFAIK you need a XML file. But it's very easy to produce one using Excel.

sargasso · « **Reply #2 on:** January 11, 2005, 01:33:37 pm »

Quote

it's very easy to produce one using Excel.

OK Thomas, you got me on this one... How?

bruce

Bruno.Cossi · « **Reply #3 on:** January 11, 2005, 02:19:18 pm »

MS Office 2003 (not sure about the previous versions, I suspect not) has a decent support of XML. MS Excel certainly can open XML files (in the Open dialog, change the file type to XML) and save to an XML file as well (Save As, change the file type).
I have not tried it with the EA XML files, but with a bit of tweaking at the worst, I see no reason why it wouldn't work.

Bruno

sargasso · « **Reply #4 on:** January 11, 2005, 03:47:45 pm »

Rats - guess I'll just have to wait for the millenium to occur in this org.

Bruce

Bruno.Cossi · « **Reply #5 on:** January 11, 2005, 08:57:09 pm »

:-) I know, many of our clients run on Office 4 versions behind the current one. I would think there is an Add-In for older versions of Excelt that helps with the XML import/export though...

Bruno

Quote

Rats - guess I'll just have to wait for the millenium to occur in this org.

Bruce

thomaskilian · « **Reply #6 on:** January 12, 2005, 04:15:42 am »

No 2003

Follow these steps:
- import CSV in one Excel sheet "table1"
- create/use a second sheet
- define the cells in the first line to be ="<token>" & table1!A1 & "</token>" (whatever token is needed)
- multiply this cell as needed
- copy the resulting XMLish text into paste buffer
- use notepad to open an existing XML file
- delete everything except the header/footer
- paste the Excel-text

Have fun

Bruno.Cossi · « **Reply #7 on:** January 12, 2005, 07:54:05 am »

I can't help but feel that my way is somewhat simpler ;-)

Quote

No 2003
Follow these steps:
- import CSV in one Excel sheet "table1"
- create/use a second sheet
- define the cells in the first line to be ="<token>" & table1!A1 & "</token>" (whatever token is needed)
- multiply this cell as needed
- copy the resulting XMLish text into paste buffer
- use notepad to open an existing XML file
- delete everything except the header/footer
- paste the Excel-text

Have fun

thomaskilian · « **Reply #8 on:** January 12, 2005, 09:31:12 am »

So give me the link to the add-in

I got used to creating it manually (15 minutes work each time).

Bruno.Cossi · « **Reply #9 on:** January 12, 2005, 10:48:25 am »

Ok, ok :-) What version of Excel do you use? Apparently the "Save as XML" option existed in version 2002 already.

Bruno

Quote

So give me the link to the add-in I got used to creating it manually (15 minutes work each time).

malmoth · « **Reply #10 on:** January 12, 2005, 10:59:07 am »

Excuse me. There is newbie written over here

. I can save my excel file as an xml file.
But anyway I try to import it, it will create a package in my model structure.
What I want to do, is to import my model issues, in the system tab.

Bruno.Cossi · « **Reply #11 on:** January 12, 2005, 11:47:26 am »

OK then, let xml be xml, there is a nice workaround - look into the table called t_issues (if you are using an .EAP file, just open using MS Access). You cna simply import your Excel file into the table directly.

Hope this helps!

Bruno

Quote

Excuse me. There is newbie written over here . I can save my excel file as an xml file.
But anyway I try to import it, it will create a package in my model structure.
What I want to do, is to import my model issues, in the system tab.

malmoth · « **Reply #12 on:** January 13, 2005, 04:24:49 am »

Thanks. That works pretty well.

But I still have a question.

In the t_issues table (opened with MS Access) I have found two fields 'Category' and 'Type' that appear neigther in the Model Issues dialog box nor in the Model Issues Tab.

I could use this 'category' field to discriminate whether an issue is internal or if it comes from my client, for exemple.

thomaskilian · « **Reply #13 on:** January 13, 2005, 07:11:22 am »

You can but you won't be shure whether your repository will run in the future

Playing with tables directly should be used only in emergency cases.

malmoth · « **Reply #14 on:** January 13, 2005, 07:49:14 am »

OK. Let's say I've imported my model issues excel table in my EA file. Now, I only want to use EA features.

All the fields in the Model issues dialog box in EA are very useful. But there is no way to sort out those issues. A typical example is the 'Internal/external' classification.

I am surprise that there is no 'Type' or 'Category' field in the Issues dialog box, whereas the fields exist in the t_issues table.

Sparx Systems Forum

News: