# One Graphic screen with Multiple OPC Tag sources

**URL:** <https://forum.inductiveautomation.com/t/one-graphic-screen-with-multiple-opc-tag-sources/2949>\
**Category:** Ignition\
**Created:** [May 17, 2011, 10:58pm UTC](https://forum.inductiveautomation.com/t/one-graphic-screen-with-multiple-opc-tag-sources/2949 "2011-05-17T22:58:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cgele](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cgele/32/3453_2.png) [@cgele](https://forum.inductiveautomation.com/u/cgele)\
**Post date:** [May 17, 2011, 10:58pm UTC](https://forum.inductiveautomation.com/t/one-graphic-screen-with-multiple-opc-tag-sources/2949/1 "2011-05-17T22:58:31Z")

</div>

I’ve created a screen to display electrical parameters for multiple electrical panels, but am having trouble on how to best display the actual values of these parameters.

I’m still new to Ignition, so is it possible to store the OPC tags to a dataset or table that contains one row for each piece of equipment and has multiple columns for the data for each panel and then use an index to the dataset or table to display the values depending on the value of a dropdown list box?

Thanks,  
Chris

---

<div class="post-metadata">

**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\
**Post date:** [May 30, 2011, 4:08am UTC](https://forum.inductiveautomation.com/t/one-graphic-screen-with-multiple-opc-tag-sources/2949/2 "2011-05-30T04:08:52Z")

</div>

Sure, I think you should just make SQLTags out of each of your OPC tags with a good naming convention, and then use indirect tag binding to achieve what you want.

There is an [intro to indirect bindings](http://www.inductiveautomation.com/support/usermanuals/ignition/index.html?indirect_bindings.htm) in the user manual.