# Configurable Object Tree View Workshop Widgets **URL:** \ **Category:** Product Feedback\ **Tags:** workshop, summer-2024-planning\ **Created:** [September 4, 2024, 10:42am UTC](https://community.palantir.com/t/configurable-object-tree-view-workshop-widgets/1216 "2024-09-04T10:42:43Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![7395684bdac13909cac4](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/7395684bdac13909cac4/32/1425_2.png) [@7395684bdac13909cac4](https://community.palantir.com/u/7395684bdac13909cac4)\ **Post date:** [September 4, 2024, 10:42am UTC](https://community.palantir.com/t/configurable-object-tree-view-workshop-widgets/1216/1 "2024-09-04T10:42:43Z")
## Give context on the use case / what you’re trying to achieve For several use cases I have modeled ontology data models with hierarchical links and I would like to give the ability to the user to view and navigate the data structure in simple way in a Workshop. Example mock data structure for a Asana/Jira like use case: Objects: - Project - Epic, linked many to one Project - Feature, linked many to one Epic - User Story, linked many to one Feature Instantiation example ```auto └── Project: TIME-MACHINE ├── Epic: Develop Time Travel Core │ ├── Feature: Quantum Stabilizer │ │ ├── User Story: Research Quantum Mechanics for Stabilization │ │ ├── User Story: Implement Quantum Stabilizer Prototype │ ├── Feature: Temporal Calibration System │ ├── User Story: Design Temporal Calibration Interface │ ├── User Story: Integrate Calibration with Time Travel Core ├── Epic: Safety Protocols for Time Travel ├── Feature: Multi-dimensional Awareness ├── User Story: Develop Awareness Module for Multiverse Detection └── Project: FTL-DRIVE ├── Epic: Build Faster-Than-Light Engine │ ├── Feature: Hyper-Space Entry Mechanism │ │ ├── User Story: Research Hyper-Space Physics │ │ ├── User Story: Build Hyper-Space Entry Mechanism ├── Epic: Navigation System for FTL ├── Feature: Cosmic Navigation AI │ ├── User Story: Design AI Algorithm for Navigating Star Systems ├── Feature: Multi-dimensional Maps ├── User Story: Generate 4D Maps for Hyper-Space Navigation ``` I would like to provide a dynamic vizualisation to users in a Workshop, where they can expand/collapse levels and vizualize different informations at each level, with several options. - One like the “Links” part of an Object View, but configurable on which links to show or not, - One Table structure, combining expand/collapse controls (and indentation) with the columns of tabular data ## Why you can’t do it today / work-arounds Current non satisfactory workarounds: - **Vertex template** to view the data structure. It works to visualise it, but it quickly becomes unreadable and overwhelming for the user when there are a lot of object instances. It is also impossible for the user to expand/collapse links. - **Encapsulated loop components** to view and expand the data structure, by configuring a loop component for each level, and encapsulating sub loops in loop components. It works but it takes times to set up, and the visual result is a bit bulky. ## Why will this make a huge difference for you or your business? The result products would be much more user friendly, driving more adoption and more value ! ---
**Author:** ![arochat](https://avatars.discourse-cdn.com/v4/letter/a/f07891/32.png) [@arochat](https://community.palantir.com/u/arochat)\ **Post date:** [October 4, 2024, 7:53pm UTC](https://community.palantir.com/t/configurable-object-tree-view-workshop-widgets/1216/2 "2024-10-04T19:53:49Z")
Hi there, this is a great idea. As a workaround, slate has a tree widget that seems to do what you are looking for. You can embed your slate app into workshop once it is configured. ---
**Author:** ![system](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/system/32/3_2.png) [@system](https://community.palantir.com/u/system)\ **Post date:** [January 19, 2025, 6:28pm UTC](https://community.palantir.com/t/configurable-object-tree-view-workshop-widgets/1216/3 "2025-01-19T18:28:59Z")
---
**Author:** ![system](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/system/32/3_2.png) [@system](https://community.palantir.com/u/system)\ **Post date:** [May 11, 2025, 7:48am UTC](https://community.palantir.com/t/configurable-object-tree-view-workshop-widgets/1216/4 "2025-05-11T07:48:50Z")
---
**Author:** ![system](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/system/32/3_2.png) [@system](https://community.palantir.com/u/system)\ **Post date:** [September 1, 2025, 10:28pm UTC](https://community.palantir.com/t/configurable-object-tree-view-workshop-widgets/1216/5 "2025-09-01T22:28:50Z")
---
**Author:** ![bkaplan](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@bkaplan](https://community.palantir.com/u/bkaplan)\ **Post date:** [September 2, 2025, 1:01pm UTC](https://community.palantir.com/t/configurable-object-tree-view-workshop-widgets/1216/6 "2025-09-02T13:01:06Z")
Hi - I have been looking for something exactly like this, did you end up figuring out a good solution here? ---
**Author:** ![system](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/system/32/3_2.png) [@system](https://community.palantir.com/u/system)\ **Post date:** [February 27, 2026, 9:04pm UTC](https://community.palantir.com/t/configurable-object-tree-view-workshop-widgets/1216/7 "2026-02-27T21:04:21Z")
---
**Author:** ![system](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/system/32/3_2.png) [@system](https://community.palantir.com/u/system)\ **Post date:** [October 26, 2026, 3:05am UTC](https://community.palantir.com/t/configurable-object-tree-view-workshop-widgets/1216/8 "2026-10-26T03:05:36Z")