# Group items in a single view (Perspective) **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [April 22, 2025, 12:35pm UTC](https://forum.inductiveautomation.com/t/group-items-in-a-single-view-perspective/105383 "2025-04-22T12:35:32Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![TechEnlive](https://avatars.discourse-cdn.com/v4/letter/t/3be4f8/32.png) [@TechEnlive](https://forum.inductiveautomation.com/u/TechEnlive)\ **Post date:** [April 22, 2025, 12:35pm UTC](https://forum.inductiveautomation.com/t/group-items-in-a-single-view-perspective/105383/1 "2025-04-22T12:35:32Z")
Hi, I have a view and here i have added many items. Now, when i need these items, e.g in property binding, I have to search a long list. My question that, is there a way that i can group items? As i can not sort this list. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/a/0a2ffe85c618ef8e23c25486e313f8334fa2ac55.png) ---
**Author:** ![Benjamin\_Furlani](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/benjamin_furlani/32/66084_2.png) [@Benjamin\_Furlani](https://forum.inductiveautomation.com/u/Benjamin_Furlani)\ **Post date:** [April 22, 2025, 12:38pm UTC](https://forum.inductiveautomation.com/t/group-items-in-a-single-view-perspective/105383/2 "2025-04-22T12:38:11Z")
Since you are using a Coordinate Container you can add other containers like flex or other coordinate containers and name them that way. It also helps a ton if you name your components meaningful names. Treat screen development in Ignition like you are following clean code practices. Meaningful names streamline development and supportability. On a similar note. I would suggest you shouldn't be searching through items in the component tree. You should put properties at the view mostly. It allows for naming changes and no breaking of bindings across your screen. ---
**Author:** ![TechEnlive](https://avatars.discourse-cdn.com/v4/letter/t/3be4f8/32.png) [@TechEnlive](https://forum.inductiveautomation.com/u/TechEnlive)\ **Post date:** [April 22, 2025, 1:37pm UTC](https://forum.inductiveautomation.com/t/group-items-in-a-single-view-perspective/105383/3 "2025-04-22T13:37:18Z")
Hi, Good point that all items should be meaningful. I just presented image an example to make my question clear. You may give me a solution for the structure below: **Current looks like this:** ```python Tank_Water_Pump Tank_Chemical Tank_Water Tank_Chemical_Pump Label_Tank_Name_Chemical Label_Tank_Name_Water ``` **Wants to like this:** ```python Tank_Chemical ----->Label_Tank_Name_Chemical ----->Tank_Chemical_Pump Tank_Water: ----->Label_Tank_Name_Water ----->Tank_Water_Pump ``` ---
**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\ **Post date:** [April 22, 2025, 1:40pm UTC](https://forum.inductiveautomation.com/t/group-items-in-a-single-view-perspective/105383/4 "2025-04-22T13:40:46Z")
As Ben has already said, the way you accomplish this is by nesting other containers (Coordinate, Flex, etc...) into the Root. So, in your example, `Tank_Chemical` and `Tank_Water` would both be container types of your choice. There is not "component" grouping in perspective like there is in vision. ---
**Author:** ![Benjamin\_Furlani](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/benjamin_furlani/32/66084_2.png) [@Benjamin\_Furlani](https://forum.inductiveautomation.com/u/Benjamin_Furlani)\ **Post date:** [April 22, 2025, 1:56pm UTC](https://forum.inductiveautomation.com/t/group-items-in-a-single-view-perspective/105383/5 "2025-04-22T13:56:14Z")
_ **This isn't exactly what you need with a coord container** _ Here is an example of flex containers holding other items. This would be the same in your situation. If you want specific positioning within the containers then you will need to the the appropriate container type. Keep in mind wether you are using fixed or percent and how that will affect containers and their contents. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/4/b4881e6dfd0528cd075298a8904a789540cc0ebc.png) ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [April 24, 2025, 10:31am UTC](https://forum.inductiveautomation.com/t/group-items-in-a-single-view-perspective/105383/6 "2025-04-24T10:31:26Z")
If you're nesting flex containers into a coord just be aware that while the flex bounds will scale with the page (if coord set to percent), the contents within it _will not_. This may cause you some issues and headaches... If you're nesting coord containers, then I suggest their aspect ratios be left blank and set to percent, and the main root coord container set to percent and have its aspect ratio set to a binding using the defaultSize prop values Containers in coord containers are not user friendly like in vision, they're ugly and hard to use. Try copying components from one percent coord to another of differing size 😬 total disaster. The only way to maintain your sanity is to design using fixed mode and remembering to change each and every embedded coord back ---
**Author:** ![r123](https://avatars.discourse-cdn.com/v4/letter/r/838e76/32.png) [@r123](https://forum.inductiveautomation.com/u/r123)\ **Post date:** [January 27, 2026, 7:01pm UTC](https://forum.inductiveautomation.com/t/group-items-in-a-single-view-perspective/105383/7 "2026-01-27T19:01:43Z")
What about performance? If you're using one large coordinate container with many different objects in an attempt draw lines or various other details, would it affect performance to group certain objects into many nested coordinate containers? ---
**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\ **Post date:** [January 27, 2026, 7:31pm UTC](https://forum.inductiveautomation.com/t/group-items-in-a-single-view-perspective/105383/8 "2026-01-27T19:31:00Z")
> [@r123](#): > > would it affect performance to group certain objects into many nested coordinate containers? Yes, there is of course some limit to the depth which you can nest components/containers. Although generally speaking this is greater than if you are using nested embedded views, but that is because of loading times. The embedded view issue used to be a much bigger issue, but IA has done a lot of work in that area. Once the page is loaded, then usually there isn't much of a noticiable performance loss because browsers are accustomed to and well optimized for showing many nested layers of HTML. That of course is also limited by what you are doing to the objects. Animations and graphical operations always take their tole. In the end the only way to know for certain is to run the view in the target browser. Specific hardware will also have an effect on this.