# Power Table dropdown lists data from query not appearing Ignition 7.9

**URL:** <https://forum.inductiveautomation.com/t/power-table-dropdown-lists-data-from-query-not-appearing-ignition-7-9/100487>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [January 6, 2025, 4:36pm UTC](https://forum.inductiveautomation.com/t/power-table-dropdown-lists-data-from-query-not-appearing-ignition-7-9/100487 "2025-01-06T16:36:40Z")\
**Posts on this page:** 1\
**Showing post:** 6

<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 7, 2025, 6:59pm UTC](https://forum.inductiveautomation.com/t/power-table-dropdown-lists-data-from-query-not-appearing-ignition-7-9/100487/6 "2025-01-07T18:59:27Z")

</div>

I'm not quite sure what you're asking with the first question, but:

> [@Juan\_Gerardo\_Rivera](#):
>
> the .text will still be working

If you have two components on the _same_ window they can absolutely refer to each other's properties (though at scale this can be an antipattern; it often makes sense to make additional custom properties on the root container and bind bidirectionally to that central property from both components as needed).

If you have two components on _different_ windows, then you need to obtain a reference to the actual window object (e.g. [`system.gui.getWindow`](https://www.docs.inductiveautomation.com/docs/8.1/appendix/scripting-functions/system-gui/system-gui-getWindow)), _or_ use a different strategy to share the data (e.g. [client tags](https://www.docs.inductiveautomation.com/docs/8.1/ignition-modules/vision/vision-client-tags)) or one of a few other possible options, but the exact best approach will vary a bit.

* * *

For your second question, if I'm understanding correctly, take a look at this post/project; I think it covers what you're asking for:

> [@Force configure cell update in power table](https://forum.inductiveautomation.com/t/force-configure-cell-update-in-power-table/16318/7):
>
> The much more efficient solution is to embed a custom editor, which will lookup the datasets dynamically whenever it’s appropriate. I’ve got a very simple example of this below; the project has an editable ‘Options’ dataset, and the available options in column B in the editable table will be dynamic based on the value in column A. The relevant code is here: root = self from javax.swing import JComboBox, DefaultCellEditor, DefaultComboBoxModel class CustomCellEditor(DefaultCellEditor):…

---

_[View the full topic](https://forum.inductiveautomation.com/t/power-table-dropdown-lists-data-from-query-not-appearing-ignition-7-9/100487)._