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

Community Tip - You can change your system assigned username to something more personal in your community settings. X

Translate the entire conversation x

How to Hide "Location" Attribute

BF_13811900
12-Amethyst

How to Hide "Location" Attribute

I have created a sub-type of a "Change Notice". I would like to hide the "Location" attribute from the "Create New Layout". I have selected the "Location" attribute from under the "Attributes" tab of the sub-type before navigating to the "Visibility" tab and setting the attributes visibility to "Hidden" for the "Create New" operation. However, the "Location" attribute continues to display when I try to create a new instance of my sub-type.

 

I have a requirement to remove the "Complexity" attribute from the same layout. I was able to do this successfully by following the same approach detailed above for "Location". I'm unsure why this would work for one attribute and not another. Can anybody shed any light on this?

ACCEPTED SOLUTION

Accepted Solutions
HelesicPetr
22-Sapphire II
(To:BF_13811900)

Hi @BF_13811900 

I have a tip for you.

Do not use the ootb parent type anymore. Create a general subtype where you add the location and remove it from the second subtype.

 

PetrH

View solution in original post

9 REPLIES 9
Fadel
22-Sapphire III
(To:BF_13811900)

What version are you on ? it seems to work in 13.1. : 

Fede
BF_13811900
12-Amethyst
(To:Fadel)

Hello Fede. Based on your video - I'm not seeing any difference in behavior when the "Location" attribute is set to "Hidden" versus "Value Hidden". What is the difference in behavior that we should expect to see? Regardless of which "Visibility" value is set, your video still displays the "Location" attribute on your sub-type with a value of "(Generated)". 

 

I am trying to totally remove the "Location" attribute and value from the "Create New Layout". When I set "Complexity" to have a visibility value of "Hidden", "Complexity" does not feature on the form at all. This is not the case for "Location", as demonstrated in your video. Do you know if there is away of totally removing "Location" from the form, as I have been able to do with "Complexity"? And, why I am seeing differences in behavior between the two attributes?

 

FYI - I am on 13.0.2.6 

Fadel
22-Sapphire III
(To:BF_13811900)

I see this seems to be an issue , raise a TS case to get R&D involved . we may try some workarounds , if you are not using the OOTB type CN , we can remove location and add it only n subtypes where its needed . 

You may also take a look at https://www.ptc.com/en/support/article/CS172011 

Fede
BF_13811900
12-Amethyst
(To:Fadel)

Hi Fede. Thank you. I will raise a TS. 

HelesicPetr
22-Sapphire II
(To:BF_13811900)

Hi @BF_13811900 

Where is your issue?

I removed the location from the create layout and the location attribute is not shown anymore.

Also the wizard can be finished and CN is created. 

HelesicPetr_0-1758633009267.png

 

PetrH

Fadel
22-Sapphire III
(To:HelesicPetr)

Hi Petr , he is trying to hide the attribute using Type and attributes visibility 

Fede
BF_13811900
12-Amethyst
(To:Fadel)

Hi @HelesicPetr . I have managed to achieve the same result as yourself by removing "Location" from the "Create New Layout" of the the parent "Change Notice" type. However, if I wanted to keep the attribute featured within this layout on the parent type but remove it from the sub-type, I am not available to remove it from the layout for the sub-type. Consequently, I would be hope to remove it from the form by using the "Visibility" tab for the attribute. Using the method I have detailed above, changing the values for "Create New" and "Edit" under the "Visibility" tab does not remove the attribute from the "Create New" wizard.

HelesicPetr
22-Sapphire II
(To:BF_13811900)

Hi @BF_13811900 

I have a tip for you.

Do not use the ootb parent type anymore. Create a general subtype where you add the location and remove it from the second subtype.

 

PetrH

This should work, thank you very much!

Announcements

Top Tags