# Creating a different header for a table with embedded view

**URL:** <https://forum.inductiveautomation.com/t/creating-a-different-header-for-a-table-with-embedded-view/94703>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [August 15, 2024, 3:03pm UTC](https://forum.inductiveautomation.com/t/creating-a-different-header-for-a-table-with-embedded-view/94703 "2024-08-15T15:03:03Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aisha\_Shiddat](https://avatars.discourse-cdn.com/v4/letter/a/45deac/32.png) [@Aisha\_Shiddat](https://forum.inductiveautomation.com/u/Aisha_Shiddat)\
**Post date:** [August 15, 2024, 3:03pm UTC](https://forum.inductiveautomation.com/t/creating-a-different-header-for-a-table-with-embedded-view/94703/1 "2024-08-15T15:03:03Z")

</div>

I'm trying to create a unique header for each tab area within a tabbed container. Is this something I can do with an embedded view component?

---

<div class="post-metadata">

**Author:** ![pascal.fragnoud](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pascal.fragnoud/32/24728_2.png) [@pascal.fragnoud](https://forum.inductiveautomation.com/u/pascal.fragnoud)\
**Post date:** [August 15, 2024, 3:18pm UTC](https://forum.inductiveautomation.com/t/creating-a-different-header-for-a-table-with-embedded-view/94703/2 "2024-08-15T15:18:07Z")

</div>

Is it a table, or a tab container ?

---

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [August 15, 2024, 3:19pm UTC](https://forum.inductiveautomation.com/t/creating-a-different-header-for-a-table-with-embedded-view/94703/3 "2024-08-15T15:19:35Z")

</div>

What do you mean by "header" and "tab area"?  
Post a neatly cropped image.

---

<div class="post-metadata">

**Author:** ![Aisha\_Shiddat](https://avatars.discourse-cdn.com/v4/letter/a/45deac/32.png) [@Aisha\_Shiddat](https://forum.inductiveautomation.com/u/Aisha_Shiddat)\
**Post date:** [August 15, 2024, 3:30pm UTC](https://forum.inductiveautomation.com/t/creating-a-different-header-for-a-table-with-embedded-view/94703/4 "2024-08-15T15:30:34Z")

</div>

Its for different tables inside of each tab area of the tab container.

 ![Tabbed Container](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/1/b1a87e8567a37b84829aab7f659c112f5f1bc96e.png)

---

<div class="post-metadata">

**Author:** ![pascal.fragnoud](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pascal.fragnoud/32/24728_2.png) [@pascal.fragnoud](https://forum.inductiveautomation.com/u/pascal.fragnoud)\
**Post date:** [August 15, 2024, 3:36pm UTC](https://forum.inductiveautomation.com/t/creating-a-different-header-for-a-table-with-embedded-view/94703/5 "2024-08-15T15:36:07Z")

</div>

You want the part circled in yellow to be dynamic and change depending on the tab ?

You could put it inside the tab area, so that it changes when you select another tab.  
Or use an embedded view and bind the path to the selected tab.  
Or a multitude of other solutions. It's perfectly doable, the best way depends on what exactly you want to do, but you haven't been very descriptive of what you're trying to achieve.

Frankly, I'd just put it inside the tab container. This is to me the simplest way.

---

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [August 15, 2024, 4:28pm UTC](https://forum.inductiveautomation.com/t/creating-a-different-header-for-a-table-with-embedded-view/94703/6 "2024-08-15T16:28:31Z")

</div>

If the date range selector is common to all tabs then add it outside the tab container as you have done.

If the date range selector is different for each tab or if it is not required on some tabs then create a view and embed that view on each tab's view as required.

---

<div class="post-metadata">

**Author:** ![pascal.fragnoud](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pascal.fragnoud/32/24728_2.png) [@pascal.fragnoud](https://forum.inductiveautomation.com/u/pascal.fragnoud)\
**Post date:** [August 15, 2024, 4:59pm UTC](https://forum.inductiveautomation.com/t/creating-a-different-header-for-a-table-with-embedded-view/94703/7 "2024-08-15T16:59:45Z")

</div>

I think I wouldn't even make a view, I'd just copy the few things it's composed of in each container.

---

<div class="post-metadata">

**Author:** ![Aisha\_Shiddat](https://avatars.discourse-cdn.com/v4/letter/a/45deac/32.png) [@Aisha\_Shiddat](https://forum.inductiveautomation.com/u/Aisha_Shiddat)\
**Post date:** [August 16, 2024, 6:56pm UTC](https://forum.inductiveautomation.com/t/creating-a-different-header-for-a-table-with-embedded-view/94703/8 "2024-08-16T18:56:23Z")

</div>

I'm probably just going to use some scripting to achieve what I am trying to do, in simple terms - what I was asking is there a way to embed components inside of a embedded view?

---

<div class="post-metadata">

**Author:** ![pascal.fragnoud](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pascal.fragnoud/32/24728_2.png) [@pascal.fragnoud](https://forum.inductiveautomation.com/u/pascal.fragnoud)\
**Post date:** [August 16, 2024, 8:49pm UTC](https://forum.inductiveautomation.com/t/creating-a-different-header-for-a-table-with-embedded-view/94703/9 "2024-08-16T20:49:28Z")

</div>

Nothing's stopping you. There's nothing special about embedded views.

But I try to avoid it as much as possible, I find it makes things more complicated than it needs to be. I make templates when absolutely necessary, or for something that I'll be reusing AND is complex enough that I wouldn't want to just duplicate it.

We could try and help you find the best way for your use case, but... we still don't know your use case.
