Sparx Systems Forum
Enterprise Architect => General Board => Topic started by: Barrett on April 02, 2007, 11:35:14 am
-
Hello,
I created a CSV file in Excel with the following columns:
Column A - Name
Column B - Type
Column C - Notes
Then, I added some basic text, so the saved .csv file looks like this:
Name,Type,Notes
Req1,Really Cool Requirement 1,Some notes about requirement 1
Req2,Really Cool Requirement 2,Some notes about requirement 2
-----------------
Then I went into EA and created a new package, then dragged it to the workspace.
------------------
Then, I created a custom Import rule that said to use the CSV file above and I added the Name, Type, and Notes field to the field specification area.
--------------------
However, if I try to import the csv, I get the following two-line error:
Import Complete
Bad Object Type when creating a new record of Type "
---------------------
What am I doing wrong? This process seems like it should be simple.
Thanks in advance.
B
-
Your type needs to be a valid UML classifier, ie:
node, component, requirement, class etc.... This is so EA knows what type of object to create. It doesn't know what a "Really cool requirement 1" is to create an object of that type.
Cheers,
David.
-
Thanks Dave.
It would be a nice enhancement if EA could give better error messages. Something like your reply to my question would be a great improvement rather than the obscure sounding error I posted.
Thanks again!!!
:)
-
Actually, you make a very good point here. EA has a lot of these (possibly legacy) errors where it just seems to emit the underlying error (from something like COM or ODBC) without any attempt to explain what went wrong or where.
IMHO, in at least some of these cases - yours is an excellent example - an error message aimed at the user rather than the developer (who's likely moved onto other areas of the product long since) would make more sense. The user would have a (possibly good) chance of understanding what needs to be done and rectifying the situation.
David
-
I also got a way that, if you didn't fill anything in on the import screen, you'd get an dialog with an OK button that said: "No error detected."
Huh?
Alan Cooper's "About Face" book on interface design has a lot to say about this type of "information dialogs".
I agree with your amplification of my posting: error messages for the user -- that help the _user_ accomplish his "goals" -- are sorely missing in EA.
Thanks for your reply
B
-
Alan Cooper's "About Face" book on interface design has a lot to say about this type of "information dialogs".
I still have my (original printing) copy. It is well read and thumbed through, and treasured greatly.
Too bad it was never available to people in IT. The reason for this remains a bit vague, although the restriction is often evident.
Sigh...
-
He published a 2nd Edition a year or so back.
:)
-
Yes, so I saw. I think it was a bit farther back. Apparently it is better, but I so love the first one.
-
Rather than an open-text field - where the user can type an infinite number of wrong entries - why not a drop-down?
-
Rather than an open-text field - where the user can type an infinite number of wrong entries - why not a drop-down?
Because this question from nearly 8 years ago is about a CSV import. Which means it is text outside of EA's control.