![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Filtering on Attribute versus Column...Weird Results? Topic Summary: Created On: 27-Dec-2004 19:27 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Found it. I had a few tables in my document. What I failed to realize was that each cell in the table had an associated value for the Make/Model attribute, but the value isn't shown in the Column since it was associated with a table. Hence the filter based on the Attribute (which found the table cells) didn't match the filter based on the displayed Column. | |
![]() |
|
Hi,
I have an object attribute that designates a make and model for one of our products. Since most requirements apply to various makes and models, the attribute is an enumerated type: R-LIB, R-RIB, R-CAB, R-LOB, R-ROB, S-LIB, S-RIB, S-CAB. For example, a single requirement might apply to both R-LIB and R-RIB, or perhaps S-CAB and R-CAB. You get the idea. ![]() Anyway, I wanted to find all the requirements that apply to the "R" make. When I setup my filter to show the requirements that have a Make/Model attribute value including R-LIB, R-RIB, R-CAB, R-LOB, or R-ROB, I get 508 results. For some reason, I thought it might be better to try using the Column tab, so I then revised my filter to show the requirements where the Make/Model column (based on the same attribute) contains "R-". This yeilded 489 results. ....Why are the number of results different? Am I being stupid here and not realizing something? My attribute filter looks like this: ((((Make/Model includes R-CAB) OR (Make/Model includes R-ROB)) OR (Make/Model includes R-LOB)) OR (Make/Model includes R-RIB)) OR (Make/Model includes R-LIB) and the Column filter looks like this: Column 'Make/Model' contains "R-" Thanks for any ideas and/or smacks updise the head. |
|
![]() |
|
![]() |
|
Found it. I had a few tables in my document. What I failed to realize was that each cell in the table had an associated value for the Make/Model attribute, but the value isn't shown in the Column since it was associated with a table. Hence the filter based on the Attribute (which found the table cells) didn't match the filter based on the displayed Column.
|
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.