# Achieving equivalent of a Repeater in a Report?

**URL:** <https://forum.inductiveautomation.com/t/achieving-equivalent-of-a-repeater-in-a-report/107629>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [June 20, 2025, 4:36pm UTC](https://forum.inductiveautomation.com/t/achieving-equivalent-of-a-repeater-in-a-report/107629 "2025-06-20T16:36:47Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ryan\_Deardorff](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan_deardorff/32/63815_2.png) [@Ryan\_Deardorff](https://forum.inductiveautomation.com/u/Ryan_Deardorff)\
**Post date:** [June 20, 2025, 4:36pm UTC](https://forum.inductiveautomation.com/t/achieving-equivalent-of-a-repeater-in-a-report/107629/1 "2025-06-20T16:36:47Z")

</div>

I want to be able to generate a report that has an arbitrary number of charts based on the number of machines at a given facility, but from what I can see, this isn't possible. If the "visible" property could be bound to some data property, I could just hardwire the maximum number of charts, and toggle as needed (ugly, but still doable). ~~The fact that this property exists but is completely useless confounds me.~~

Am I missing something? Surely I can't be the first to want to achieve this...

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [June 20, 2025, 4:40pm UTC](https://forum.inductiveautomation.com/t/achieving-equivalent-of-a-repeater-in-a-report/107629/2 "2025-06-20T16:40:27Z")

</div>

> [@Ryan\_Deardorff](#):
>
> If the "visible" property could be bound to some data property,

Well, good news on that front:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/b/eb570f220f4b4f8f6c94486c9c844ff545d45517.png)

> **[Data Keys | Ignition User Manual](https://docs.inductiveautomation.com/docs/8.1/ignition-modules/reporting/report-design/data-keys#dynamic-data-keys)**
>
> In the Reporting Module, we use Data Keys to pull values from data sources and show them on the report. In simple terms, Data Keys are placeholders for your data. The simplest reference to data is a simple Data Key. At report generation time, these...

But I would say the better pattern would be to structure your data as a nesting and use a **table** component (with an "unstructured" row containing the chart) - that way you get automatic repetition of N charts for whatever size N is your input. That makes the "hard" part structuring your input data.

---

<div class="post-metadata">

**Author:** ![Ryan\_Deardorff](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan_deardorff/32/63815_2.png) [@Ryan\_Deardorff](https://forum.inductiveautomation.com/u/Ryan_Deardorff)\
**Post date:** [June 20, 2025, 4:49pm UTC](https://forum.inductiveautomation.com/t/achieving-equivalent-of-a-repeater-in-a-report/107629/3 "2025-06-20T16:49:49Z")

</div>

Thanks! I guess I don't yet have a full understanding of the Table component.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [June 20, 2025, 4:53pm UTC](https://forum.inductiveautomation.com/t/achieving-equivalent-of-a-repeater-in-a-report/107629/4 "2025-06-20T16:53:04Z")

</div>

> **[Charts Inside of Tables | Ignition User Manual](https://docs.inductiveautomation.com/docs/8.1/ignition-modules/reporting/report-design/report-table/charts-inside-of-tables#adding-a-chart-inside-a-details-row)**
>
> Adding Charts Inside of Tables

Take a look at this example - it may be enough for what you're doing and you may not need the extra complications of table groupings/nested datasets.