# Report parameters unbinding

**URL:** <https://forum.inductiveautomation.com/t/report-parameters-unbinding/69166>\
**Category:** Ignition\
**Created:** [January 30, 2023, 6:46pm UTC](https://forum.inductiveautomation.com/t/report-parameters-unbinding/69166 "2023-01-30T18:46:15Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jbb5310](https://avatars.discourse-cdn.com/v4/letter/j/ecc23a/32.png) [@jbb5310](https://forum.inductiveautomation.com/u/jbb5310)\
**Post date:** [January 30, 2023, 6:46pm UTC](https://forum.inductiveautomation.com/t/report-parameters-unbinding/69166/1 "2023-01-30T18:46:15Z")

</div>

I'm using a dropdown component with names of reports that is linked to the report path on the report viewer. My issue is when changing reports that do not share the same parameters they tend to unbind which becomes an issue for the users.

My current solution is to add all these parameters to all my reports but I'm working with about 50 reports, just wanted to know if there is a work around or a correct way to handle to. Currently on Ignition Version 8.1.21 Reporting Module 6.1.21

---

<div class="post-metadata">

**Author:** ![dkhayes117](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dkhayes117/32/68344_2.png) [@dkhayes117](https://forum.inductiveautomation.com/u/dkhayes117)\
**Post date:** [January 30, 2023, 6:50pm UTC](https://forum.inductiveautomation.com/t/report-parameters-unbinding/69166/2 "2023-01-30T18:50:09Z")

</div>

I ran into this problem a while back in a Vision project. The only way I could make it work was to stack report viewers on top of each other. Each is configured with their own bindings where only one report is visible at any given time. However, I only had around 7 reports, not 50.

---

<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:** [January 30, 2023, 6:57pm UTC](https://forum.inductiveautomation.com/t/report-parameters-unbinding/69166/3 "2023-01-30T18:57:05Z")

</div>

Instead of bindings, you could use scripting to update the report parameters as values change. Somewhat tricky, but probably nicer to client and gateway memory than generating a bunch of extra reports.

---

<div class="post-metadata">

**Author:** ![jbb5310](https://avatars.discourse-cdn.com/v4/letter/j/ecc23a/32.png) [@jbb5310](https://forum.inductiveautomation.com/u/jbb5310)\
**Post date:** [January 30, 2023, 7:11pm UTC](https://forum.inductiveautomation.com/t/report-parameters-unbinding/69166/4 "2023-01-30T19:11:32Z")

</div>

the script would be placed on the component's property change correct? Just want to clarify because I think this will work and save me time in the long haul.

---

<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:** [January 30, 2023, 7:18pm UTC](https://forum.inductiveautomation.com/t/report-parameters-unbinding/69166/5 "2023-01-30T19:18:07Z")

</div>

Yeah, that would be the most direct way to do it. You could also do an 'indirect' approach, where you have X components in charge of setting up parameters, then a button in the middle that copies values over from the data entry components to the report parameters. Less scripting overall, but possibly more complicated scripting; no perfect answer.