cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Did you get called away in the middle of writing a post? Don't worry you can find your unfinished post later in the Drafts section of your profile page. X

Translate the entire conversation x

Attribute Visibility

BF_13811900
12-Amethyst

Attribute Visibility

Am I correct in saying that the only difference between setting an attribute's visibility to "Value Hidden" and "Read Only" from within "Type and Attribute Management" is that the "Value Hidden" setting sets the display of the attribute value to "(Hidden)" and the "Read Only" setting sets it to "(Unassignable)" in the form for the operation the settings were applied to?

ACCEPTED SOLUTION

Accepted Solutions

PTC have been in contact with myself and the behavior I have described is as expected apparently. I was pointed in the direction of https://www.ptc.com/en/support/article/CS131615

View solution in original post

7 REPLIES 7

Here is the explanation from the help center.

shussaini_0-1757677040215.png

Hope this helps.

regards

~Syed

 

Hi Syed! Unfortunately the info in the help center does not shed any light on the issue I'm having. "Read Only" results in the default value that my attribute is set to not displaying in my "Create New" form for the object the attribute is assigned to. Instead, the form displays a value for the attribute of "(Unassignable"). I would expect to see the default value of the attribute when the attribute is set to be "Read Only". Setting the visibility of the attribute to "Value Hidden" results in the value of the attribute in the "Create New" form displaying as "(Hidden)". Each setting does not display the default value that is assigned to the attribute. Apart from the differing values of "(Hidden)" and "(Unassignable"), I'm unsure what the differences are between the two visibility options.

I've seen the "unassignable" before. I don't quite remember, but I think it may depend on what Type the attribute is on. Attributes on CAD objects may have a different behavior than attributes on a WTPart.

Thanks Joe. I'll keep this in mind.

Hi @BF_13811900,

 

I wanted to see if you got the help you needed.

If so, please mark the appropriate reply as the Accepted Solution. It will help other members who may have the same question.
Of course, if you have more to share on your issue, please pursue the conversation. 

 

Thanks,
Anurag 
 

Fadel
22-Sapphire III
(To:joe_morton)

@joe_morton  unassignable is see when adding alias or calculated attribute to create layouts sometime is also seen when attributes have immutable constraints : 

Fadel_0-1758023493263.png

 

Fede

PTC have been in contact with myself and the behavior I have described is as expected apparently. I was pointed in the direction of https://www.ptc.com/en/support/article/CS131615

Announcements

Top Tags