![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Filtering on empty attribute Topic Summary: Created On: 24-Sep-2003 04:46 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Hi, Louie Landale has identified why this problem occurs - Click here to get the answers and a DXL workaround script - otherwise, just browse the DXL Exchange forum and look for the same message title that I used for this forum "Filtering on empty attribute". | |
![]() |
|
Hi,
I've posted this on both the Defect Tracking and DXL Exchange forums. We applied the following filter to a module: "CommentText is empty" You could imagine our surprise when a number of objects were missing in the filter and we knew that in each case, the contents of attribute "CommentText" was indeed empty. We made specifically sure that there wasn't any stray white spaces hiding away. There's nothing peculiar about this attribute - it's a Text type attribute with "Generate History" enabled and no Default Value set. After scratching our heads for a while, we selected an object that was exhibiting this problem, opened the object properties dialogue box and brought up the edit window for attribute "CommentText". As expected, there was nothing to delete so out of desperation we selected the "Reset to Default" button and tried the filter again. Now it's working ![]() Can anyone on this Forum or any Telelogic people who might be browsing indicate why this might be so - I'm also looking for a work around / DXL script that could find these cells and reset them to default so that they are picked up properly by the filter. ------------------------- Paul Miller Specification Practices Specialist, EuroCyber, Melbourne, Australia. Mobile: +61 (0)418 135 103 Web Site: http://www.eurocyber.biz E-mail: miller@eurocyber.biz">pmiller@eurocyber.biz |
|
![]() |
|
![]() |
|
I can't help, but I have seen the same problem. I have looked for a text attribute being empty, and in a large-ish module (~5000 objects, ~10 baselines), I have found about 15 objects with the problem. I did not think to 'reset to default', so my problem remained. There appeared to be no logic to which objects were affected, either by position in the module or date of last edit. I experienced this with a 5.2 standalone database that had been moved from a Windows 98 machine to a Win2k machine. I had assumed it was just me.
------------------------- Hazel Woodcock |
|
![]() |
|
![]() |
|
See my reply DXL forum.
|
|
![]() |
|
![]() |
|
Hi,
Louie Landale has identified why this problem occurs - Click here to get the answers and a DXL workaround script - otherwise, just browse the DXL Exchange forum and look for the same message title that I used for this forum "Filtering on empty attribute". ------------------------- Paul Miller Specification Practices Specialist, EuroCyber, Melbourne, Australia. Mobile: +61 (0)418 135 103 Web Site: http://www.eurocyber.biz E-mail: miller@eurocyber.biz">pmiller@eurocyber.biz |
|
![]() |
Telelogic DOORS
» Defect/Issue Tracking
»
Filtering on empty attribute
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.