# Perspective Tab container - disable tab **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [October 17, 2022, 7:47pm UTC](https://forum.inductiveautomation.com/t/perspective-tab-container-disable-tab/65308 "2022-10-17T19:47:32Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Tim\_Hansson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tim_hansson/32/39365_2.png) [@Tim\_Hansson](https://forum.inductiveautomation.com/u/Tim_Hansson)\ **Post date:** [October 17, 2022, 7:47pm UTC](https://forum.inductiveautomation.com/t/perspective-tab-container-disable-tab/65308/1 "2022-10-17T19:47:32Z")
Hi, I read the changelog that I can disable a tab in the tab container. I'm complete new to ignition and I can't figure out where I do it? ---
**Author:** ![code\_skin](https://avatars.discourse-cdn.com/v4/letter/c/43a26b/32.png) [@code\_skin](https://forum.inductiveautomation.com/u/code_skin)\ **Post date:** [October 17, 2022, 7:51pm UTC](https://forum.inductiveautomation.com/t/perspective-tab-container-disable-tab/65308/2 "2022-10-17T19:51:33Z")
From the manual: A boolean **disabled** property can be added to an element that's set to an object data type. This setting determines if a tab can be selected. If the tab is already active when it becomes disabled, users will not be prevented from leaving the tab, but they will not be able to get back to it. The content of the tab is not affected by the enabled/disabled state of the tab. link to tab container: [Perspective - Tab Container - Ignition User Manual 8.1 - Ignition Documentation](https://docs.inductiveautomation.com/display/DOC81/Perspective+-+Tab+Container) The props.tabs property is defaulted to array, so just change it to an object and add at least 2 keys (text and disabled). example: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/7/b7c6050d7f72725ca90914cc1583f9092f72a03c.png) ---
**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\ **Post date:** [October 17, 2022, 8:45pm UTC](https://forum.inductiveautomation.com/t/perspective-tab-container-disable-tab/65308/3 "2022-10-17T20:45:02Z")
For clarity: you should right-click the 0th entry within `tabs` and select "Change to object". This new object should receive the new keys `text` and `disabled`. ---
**Author:** ![Tim\_Hansson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tim_hansson/32/39365_2.png) [@Tim\_Hansson](https://forum.inductiveautomation.com/u/Tim_Hansson)\ **Post date:** [October 19, 2022, 8:13am UTC](https://forum.inductiveautomation.com/t/perspective-tab-container-disable-tab/65308/4 "2022-10-19T08:13:51Z")
Thanks! I changed to object but didn't get the text and disable. I found out how to add the myself. It's hard because there aren't any "option" when adding in this case "value". So you don't know what you can choose from on a simple way ---
**Author:** ![code\_skin](https://avatars.discourse-cdn.com/v4/letter/c/43a26b/32.png) [@code\_skin](https://forum.inductiveautomation.com/u/code_skin)\ **Post date:** [October 19, 2022, 11:54am UTC](https://forum.inductiveautomation.com/t/perspective-tab-container-disable-tab/65308/5 "2022-10-19T11:54:20Z")
The manual does contain this information. See my link above. ---
**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\ **Post date:** [October 19, 2022, 3:34pm UTC](https://forum.inductiveautomation.com/t/perspective-tab-container-disable-tab/65308/6 "2022-10-19T15:34:29Z")
> [@cmallonee](#): > > should receive roughly translates to "this object needs to have you add the following keys yourself". ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [October 19, 2022, 3:42pm UTC](https://forum.inductiveautomation.com/t/perspective-tab-container-disable-tab/65308/7 "2022-10-19T15:42:43Z")
It would probably make sense for "Change to object" to insert the key that is implied when not an object. (Everywhere applicable.) And if already populated, to move the current value to that key. The component knows--there just needs to be some plumbing for the designer UI to know. ---
**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\ **Post date:** [October 19, 2022, 3:53pm UTC](https://forum.inductiveautomation.com/t/perspective-tab-container-disable-tab/65308/8 "2022-10-19T15:53:55Z")
In this instance, neither `text` nor `disabled` is a required key; perhaps the user intends to make this tab render a View. When objects have required keys, we do add them -- like when adding instances to Flex repeaters. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [October 19, 2022, 6:35pm UTC](https://forum.inductiveautomation.com/t/perspective-tab-container-disable-tab/65308/9 "2022-10-19T18:35:41Z")
I think the implied key when a component accepts a list should be treated specially, even if not actually required. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [October 20, 2022, 1:53pm UTC](https://forum.inductiveautomation.com/t/perspective-tab-container-disable-tab/65308/10 "2022-10-20T13:53:01Z")
I've thought some more on this--reasoning through the "why" behind my gut reaction. The core of the issue, to me, is that "Change to object" shouldn't break a working view/component configuration. Placing the current list item value in the new object's corresponding key seems to me an intuitive transformation. And reversible--the infra to support such throughout the designer would also support a "Change FROM object" operation when that one key is the only one present.