Skip to main content
B
BF_1381190014-Alexandrite
14-Alexandrite
September 11, 2025
Solved

Blank Values for Cascading Attributes

  • September 11, 2025
  • 1 reply
  • 531 views

I have created two attributes in Windchill that makes use of enumerated value lists. I have introduced cascading attribute rules against the object type which is associated to the two attributes. My cascading attribute rules stipulate that if a value for attribute 1 is set to X, then the value for attribute 2 should be set to Y. I have configured the "Create New Layout" for this object type to contain these two attributes. When I set the value of attribute 1 to X, attribute 2 does not display a value of Y automatically. Instead, the dropdown list of values associated with attribute 2 decreases to two to select from - a value of Y and an option to set the attribute value to blank. I want attribute 2 to be set to a value of Y without giving the user the ability to select between a value of Y or blank.

 

I am aware that it is possible to specify that attribute 2 should not include any blank options in the dropdown list it is associated with. However, this will not work for me since I do want the value of attribute 2 to be set to blank when attribute 1 is set to blank.

 

Two questions:

 

1. Can anybody suggest a way of getting past this issue?

2. Is it possible to specify that the value of an attribute should be blank if another attribute value equals blank in a cascading attribute rule?

Best answer by Fadel

I have checked the CS353293, it seems that this has been checked with R&D. below is what I conclude from dev response : 

 

The use case is functioning as intended. Filtering values based on cascading attribute rules does not imply that a value will be automatically selected.

Currently the design ensures that users retain control over their selections. They are expected to make a deliberate choice—either to set a value or leave it blank. Defaulting to a blank value is safer and aligns with the behavior when multiple values are available.

While we recognize that auto-selection could enhance productivity for certain attributes and users, implementing it would conflict with the broader expectation of user-driven input and consistency across scenarios.

 

I'm sorry but Out the box there nothing we can change to meet your expectations 

 

1 reply

Fadel
Fadel23-Emerald I
23-Emerald I
September 12, 2025

can you set this on the create layout  : 

Fadel_0-1757685326591.png

 

Buiꓘa
B
BF_1381190014-AlexandriteAuthor
14-Alexandrite
September 12, 2025

Hello @Fadel. I am able to do that. However, as mentioned in my original post, this will not work for me since I do want the value of attribute 2 to be set to blank when attribute 1 is set to blank. Therefore, I believe I would need to include blanks in my dropdown lists.

 

I did contact PTC regarding this issue and their response can be seen below:

 

As outlined in article CS353293, filtering values based on cascading attribute rules does not automatically select a value. This behavior is expected.

 

This does not help with resolving my issue though. I want to be able to select the value of attribute 2 dependent upon what the value for attribute 1 is set to. If attribute 1 is set to X then select a value of Y for attribute 2, for example. Originally, I thought cascading attribute rules was the way to do this but apparently that is not the case.

Fadel
Fadel23-Emerald IAnswer
23-Emerald I
September 12, 2025

I have checked the CS353293, it seems that this has been checked with R&D. below is what I conclude from dev response : 

 

The use case is functioning as intended. Filtering values based on cascading attribute rules does not imply that a value will be automatically selected.

Currently the design ensures that users retain control over their selections. They are expected to make a deliberate choice—either to set a value or leave it blank. Defaulting to a blank value is safer and aligns with the behavior when multiple values are available.

While we recognize that auto-selection could enhance productivity for certain attributes and users, implementing it would conflict with the broader expectation of user-driven input and consistency across scenarios.

 

I'm sorry but Out the box there nothing we can change to meet your expectations 

 

Buiꓘa
Terms & ConditionsCookie settingsAccessibility statement