Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: Issue with spreadsheet importer
Topic Summary:
Created On: 21-Aug-2003 18:19
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 21-Aug-2003 18:19
User is offline View Users Profile Print this message


Frank Lipski

Posts: 42
Joined: 6-Nov-2002

When importing data from a spreadsheet using the Telelogic supplied import tool, I noticed what I consider a bug. If you are importing data from a column into either a real or integer attribute, and the value is zero, it imports into DOORS as a empty (null) value, and not zero.
I have observed this with V5.2, V6 and V7 of DOORS. Does anyone else consider this a bug, but more importantly, to this forum, has anyone fixed this problem.

TIA
Frank
Report this to a Moderator Report this to a Moderator
 1-Sep-2003 11:09
User is offline View Users Profile Print this message


Tony Goodman

Posts: 1098
Joined: 12-Sep-2002

I think it is a bug.
When a new object is created, its attributes are null by default.
Before updating the value of an attribute, the importer does a comparison between the current attribute value and the value being imported.
The attribute is only updated if the values differ.
Unfortunately, the integer comparison used does not distinguish between null and zero, so all zero values remain null.

You could fix this by amending the commas.dxl script to check for zero or null and explicitly assign zero.

add the following after the "if (new_int != old_int) { ... }" statement (at line 745)

else {
if (new_int == 0) {
o.attr_name = new_int
updated = true
}
}

add the following after the "if (new_real != old_real) { ... }" statement (at line 734)

else {
if (new_real == 0.0) {
o.attr_name = new_real
updated = true
}
}

The downside to this is that the updated objects count may not reflect the number of actual updates.


-------------------------
Tony Goodman
http://www.smartdxl.com
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 0 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 0 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.