Page 1 of 1

Excel Data Load with Stereotype: Load Error

PostPosted: Fri May 13, 2016 10:05 am
by chris.lorentz@insitu.com
The log is showing this error - 2016-05-13 08:48:31,683 [pool-MagicDraw-thread-2:Import data from file.] ERROR org.eso.sdd.mbse.safety - Hazard stereotype is null. At one point I have seen the data load properly in columns with mapping completed then this error appeared.

Please advise.

Best regards,

Chris

Re: Excel Data Load with Stereotype: Load Error

PostPosted: Tue May 17, 2016 1:08 am
by chanon_s
Dear Chris

It would be very helpful for deeper investigation if you could send us the project you are having an issue with.

Sincerely

Chanon S.
No Magic Customer Support

Re: Excel Data Load with Stereotype: Load Error

PostPosted: Tue May 17, 2016 9:34 am
by chris.lorentz@insitu.com
Hello,

Attached is the request project file. Was unable to load the test data due to file number limitations.
Thank you for taking a look at this issue!

Chris

Re: Excel Data Load with Stereotype: Load Error

PostPosted: Tue May 17, 2016 9:41 am
by chris.lorentz@insitu.com
Here is the sample data spreadsheet for your convenience.

Thanks again!

Chris

Re: Excel Data Load with Stereotype: Load Error

PostPosted: Wed May 18, 2016 2:40 am
by chanon_s
Dear Chris

We found out that there is an issue regarding your mapping in your project. The issue occurred when it was trying to map a value from an excel column with the property named Verified By, where type is String. This property has its name duplicated with the one, where type is NamedElement, derived from the Requirement stereotype. We will register this issue into our bug tracking system and have it fixed into the future releases.

We are sorry for the inconvenience this issue might have caused. As a workaround, please rename such property to not duplicate with derived properties, as displayed in the image below:

workaround.png


Sincerely

Chanon S.
No Magic Customer Support

Re: Excel Data Load with Stereotype: Load Error

PostPosted: Wed May 18, 2016 9:44 am
by chris.lorentz@insitu.com
The workaround worked well!!! Thank you!!!
Chris