# Reporting Module: Roadmap

**URL:** <https://forum.inductiveautomation.com/t/reporting-module-roadmap/69468>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [February 6, 2023, 7:11am UTC](https://forum.inductiveautomation.com/t/reporting-module-roadmap/69468 "2023-02-06T07:11:49Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![Adriaan.leRoux](https://avatars.discourse-cdn.com/v4/letter/a/bbce88/32.png) [@Adriaan.leRoux](https://forum.inductiveautomation.com/u/Adriaan.leRoux)\
**Post date:** [February 6, 2023, 7:11am UTC](https://forum.inductiveautomation.com/t/reporting-module-roadmap/69468/1 "2023-02-06T07:11:49Z")

</div>

Can I get any sort of clarity on where IA is going with the Reporting module, or if there are any upgrades in the pipeline? I get the feeling that this module's development has stagnated as it feels considerably behind the other modules provided.

---

<div class="post-metadata">

**Author:** ![jcoffman](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jcoffman/32/6429_2.png) [@jcoffman](https://forum.inductiveautomation.com/u/jcoffman)\
**Post date:** [February 6, 2023, 4:25pm UTC](https://forum.inductiveautomation.com/t/reporting-module-roadmap/69468/2 "2023-02-06T16:25:12Z")

</div>

Hi @Adriaan.leRoux,

We do have some plans to make some improvements within the Reporting module. There isn't a roadmap or anything formalized yet, but Its definitely something we are aware of and this exact task is on someones To-Do list.

Ill pass this thread along to the dev so when they have some time maybe they can update this thread.

Hope that helps,  
Jonathan C

---

<div class="post-metadata">

**Author:** ![Adriaan.leRoux](https://avatars.discourse-cdn.com/v4/letter/a/bbce88/32.png) [@Adriaan.leRoux](https://forum.inductiveautomation.com/u/Adriaan.leRoux)\
**Post date:** [February 6, 2023, 6:47pm UTC](https://forum.inductiveautomation.com/t/reporting-module-roadmap/69468/3 "2023-02-06T18:47:54Z")

</div>

I appreciate the feedback, thank you very much

---

<div class="post-metadata">

**Author:** ![Vi\_Quang](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/vi_quang/32/82707_2.png) [@Vi\_Quang](https://forum.inductiveautomation.com/u/Vi_Quang)\
**Post date:** [February 10, 2023, 1:09am UTC](https://forum.inductiveautomation.com/t/reporting-module-roadmap/69468/4 "2023-02-10T01:09:53Z")

</div>

Hi Adriaan,

I can say that there are plans for the Reporting Module, a feature is currently in development even, but so far we haven't yet set a formal roadmap. This might change in about 2 months, and I'll try to update you with the status then. It can be a frustrating to not have anything definitive, especially if there's something you think is lacking with the software or improvements you'd like to see. Also, input on how we can improve your workflow or experience using the software is always appreciated.

---

<div class="post-metadata">

**Author:** ![amy.sudibyo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/amy.sudibyo/32/38659_2.png) [@amy.sudibyo](https://forum.inductiveautomation.com/u/amy.sudibyo)\
**Post date:** [February 10, 2023, 2:15am UTC](https://forum.inductiveautomation.com/t/reporting-module-roadmap/69468/5 "2023-02-10T02:15:39Z")

</div>

I think a little more detail in the user manual would go a long way. Currently the reporting module seems to be documented largely in the IU training video, which makes it annoying as a reference if it's been a while between reporting module uses.

---

<div class="post-metadata">

**Author:** ![Vi\_Quang](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/vi_quang/32/82707_2.png) [@Vi\_Quang](https://forum.inductiveautomation.com/u/Vi_Quang)\
**Post date:** [February 10, 2023, 9:20pm UTC](https://forum.inductiveautomation.com/t/reporting-module-roadmap/69468/6 "2023-02-10T21:20:37Z")

</div>

Thanks Amy,

I'll take a look at what's in the videos and compare it with what we have in the Manual and see if we can improve on this.

---

<div class="post-metadata">

**Author:** ![Adriaan.leRoux](https://avatars.discourse-cdn.com/v4/letter/a/bbce88/32.png) [@Adriaan.leRoux](https://forum.inductiveautomation.com/u/Adriaan.leRoux)\
**Post date:** [February 15, 2023, 7:12pm UTC](https://forum.inductiveautomation.com/t/reporting-module-roadmap/69468/7 "2023-02-15T19:12:41Z")

</div>

Hi there, I am off sick at the moment, but I'll do a thorough write up when I am back at work next week

---

<div class="post-metadata">

**Author:** ![Adriaan.leRoux](https://avatars.discourse-cdn.com/v4/letter/a/bbce88/32.png) [@Adriaan.leRoux](https://forum.inductiveautomation.com/u/Adriaan.leRoux)\
**Post date:** [February 20, 2023, 1:39am UTC](https://forum.inductiveautomation.com/t/reporting-module-roadmap/69468/8 "2023-02-20T01:39:19Z")

</div>

- Move Report pages up and down, reorder

- Headers & Footers

- Snap grid for easy layout

- Preferred ranges on charts / Desired areas. Currently this has to be drawn in with a box

- Timeseries pen order, move up and down easily

- Reorder Schedules

- Easy to use table of content, like an insertable component like MS Word

- Large Reports:

- When working on a report, I would like to be able to 'disable' or hide a page. For example, if I have a daily report, and the changes I make take longer than a day to do, I do not want to see the page I am currently working on being put in the report in its half finished state

- Print/page margins

- Preview report data, especially when scripting is involved

- a dashed line when the data quality is bad. I recall this feature, but I don't see it working

- A better GUI, or easier way to create the emails that are being sent. nothing fancy, but some sort of interface for formatting

- Hyperlinks that take you to different pages (Or a clickable ToC)

That's my 5 cents for now

---

<div class="post-metadata">

**Author:** ![brandon1](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@brandon1](https://forum.inductiveautomation.com/u/brandon1)\
**Post date:** [February 20, 2023, 2:04pm UTC](https://forum.inductiveautomation.com/t/reporting-module-roadmap/69468/9 "2023-02-20T14:04:25Z")

</div>

I would like the ability to use the expression language and scripting languages on the report components cells.

The simple table objects should have the ability to adjust the cell size via properties like the regular table component.

The ability to add as many summary rows on the bottom of the table component as needed.

The ability to do conditional formatting on columns of the report objects like excel can do.

Fix issues where the simple report component renders at different sizes in design verses runtime mode.

Just an overall round of random bug fixes. I have had times where the report module completely locks up and I end up losing work. It is very frustrating.

---

<div class="post-metadata">

**Author:** ![Steve\_Griffin](https://avatars.discourse-cdn.com/v4/letter/s/5e9695/32.png) [@Steve\_Griffin](https://forum.inductiveautomation.com/u/Steve_Griffin)\
**Post date:** [February 20, 2023, 2:38pm UTC](https://forum.inductiveautomation.com/t/reporting-module-roadmap/69468/10 "2023-02-20T14:38:08Z")

</div>

If would also be very useful to retrieve an objects value usually a TextShape object. we may have these  
in many places on a free form report. And we need to do some math on these. it gets difficult.  
to get the average of two values we have @(tag\_history.cellasidelvl\_in\_r + tag\_history.cellbsidelvl\_in\_r)/2@  
it would be better if it worked like Excel TextShape1 + TestShape2 /2. Of course the TextShape would  
have a unique name. As is is now they are all named TextShape.  
Now be able to use this TextShapes value in a different TextShape, like Excel. I do this often  
in chemical reports, and it gets very difficult. In Excel I woud have ((B2 + C2 / 2) \* D3) + E3.  
Now replace each reference with something like @tag\_history.cellasidelvl\_in\_r@.  
very hard to follow in the current reporting module

---

<div class="post-metadata">

**Author:** ![gdube](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/gdube/32/41701_2.png) [@gdube](https://forum.inductiveautomation.com/u/gdube)\
**Post date:** [February 20, 2023, 2:51pm UTC](https://forum.inductiveautomation.com/t/reporting-module-roadmap/69468/11 "2023-02-20T14:51:59Z")

</div>

The docs from the developer of the "library" used by the Reporting module is pretty helpful.  
[https://www.reportmill.com/support/DesDocs.html](https://www.reportmill.com/support/DesDocs.html)

---

<div class="post-metadata">

**Author:** ![Vi\_Quang](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/vi_quang/32/82707_2.png) [@Vi\_Quang](https://forum.inductiveautomation.com/u/Vi_Quang)\
**Post date:** [February 20, 2023, 5:22pm UTC](https://forum.inductiveautomation.com/t/reporting-module-roadmap/69468/12 "2023-02-20T17:22:40Z")

</div>

Thanks guys for your input,

I've had similar thoughts on some of these and it's great to know that it will be of use if implemented. Some are completely new to me, so that's great too, and I'll look at those and try to evaluate them.

> Just an overall round of random bug fixes. I have had times where the report module completely locks up and I end up losing work. It is very frustrating.

If you haven't posted a bug report when this happens, please do. Losing work is a sure way to have people hate software, just having to redo what you've already done is very frustrating and defeating. We'll try to reduce some of the bug tickets in the queue and hopefully that will help.

Update: regarding a Roadmap. Internally we'll have a trajectory set in March, but unfortunate that will not be public facing.

---

<div class="post-metadata">

**Author:** ![Adriaan.leRoux](https://avatars.discourse-cdn.com/v4/letter/a/bbce88/32.png) [@Adriaan.leRoux](https://forum.inductiveautomation.com/u/Adriaan.leRoux)\
**Post date:** [June 19, 2024, 7:30am UTC](https://forum.inductiveautomation.com/t/reporting-module-roadmap/69468/13 "2024-06-19T07:30:36Z")

</div>

Any update on this? Is there something in the pipeline for us?

---

<div class="post-metadata">

**Author:** ![Vi\_Quang](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/vi_quang/32/82707_2.png) [@Vi\_Quang](https://forum.inductiveautomation.com/u/Vi_Quang)\
**Post date:** [June 20, 2024, 3:40pm UTC](https://forum.inductiveautomation.com/t/reporting-module-roadmap/69468/14 "2024-06-20T15:40:06Z")

</div>

It's still on our radar, and worked on (not to imply exactly the items listed in this thread), unfortunately I can't be more specific in my response.

---

<div class="post-metadata">

**Author:** ![Adriaan.leRoux](https://avatars.discourse-cdn.com/v4/letter/a/bbce88/32.png) [@Adriaan.leRoux](https://forum.inductiveautomation.com/u/Adriaan.leRoux)\
**Post date:** [June 20, 2024, 5:24pm UTC](https://forum.inductiveautomation.com/t/reporting-module-roadmap/69468/15 "2024-06-20T17:24:41Z")

</div>

Thanks for replying though
