# Power Table Column Drop Down Query Using configureEditor Extension Function

**URL:** <https://forum.inductiveautomation.com/t/power-table-column-drop-down-query-using-configureeditor-extension-function/19594>\
**Category:** Ignition\
**Created:** [September 8, 2018, 5:50pm UTC](https://forum.inductiveautomation.com/t/power-table-column-drop-down-query-using-configureeditor-extension-function/19594 "2018-09-08T17:50:09Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [September 10, 2018, 3:27pm UTC](https://forum.inductiveautomation.com/t/power-table-column-drop-down-query-using-configureeditor-extension-function/19594/4 "2018-09-10T15:27:06Z")

</div>

You should not run a (by comparison) slow operation like a query directly inside the configureCell function. Run the query somewhere else on the client, then in the script simply limit the results. Check this post for more information on how to do that (note that it's a fairly high-level scripting solution):

> [@Force configure cell update in power table](http://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-column-drop-down-query-using-configureeditor-extension-function/19594)._
