# configureEditor Script Behavior Questions/Concerns **URL:** \ **Category:** Ignition\ **Tags:** ignition80, database, vision, scripting\ **Created:** [November 30, 2023, 2:33pm UTC](https://forum.inductiveautomation.com/t/configureeditor-script-behavior-questions-concerns/82533 "2023-11-30T14:33:27Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![Raymond\_Sipes](https://avatars.discourse-cdn.com/v4/letter/r/4491bb/32.png) [@Raymond\_Sipes](https://forum.inductiveautomation.com/u/Raymond_Sipes)\ **Post date:** [November 30, 2023, 2:33pm UTC](https://forum.inductiveautomation.com/t/configureeditor-script-behavior-questions-concerns/82533/1 "2023-11-30T14:33:27Z")
Hello all! I have a power table that displays a view with our recipes and ingredients tied to the recipe. I have followed some helpful [articles](https://forum.inductiveautomation.com/t/force-configure-cell-update-in-power-table/16318/7) form the forum regarding the configureEditor to allow for a dropdown when selecting into a cell, then updating the power table with the new value. All of this is working as intended, but when I go to update this within the database by running a Named Query, it does not update with the respective value. I added quite a few print statements to try a better understand why this is the case. It seems to be running the script as soon as I enter preview mode. Is there a way to invoke the update named query after the user select the new value within this function? Or would this update named query be better ran in another function? Do let me know if you need any more information, thank you! configureEditor Script: ```auto # Print the raw value of colName for debugging print("Raw Column Name:", repr(colName)) if colName.strip() == "Ingredient": print("Entering the if block.") # Add this line for debugging try: pt = system.db.runNamedQuery("select ingredient") # Construct the list of options using data from each row options = [(pt.getValueAt(row, "Ingredient_ID"), pt.getValueAt(row, "Ingredient")) for row in range(pt.rowCount)] # Print the options for debugging purposes print("Options:", options) # Additional print statements within the try block print("Before update recipe name query.") system.db.runNamedQuery("update recipe name", {"IID": options[0][0], "ID": self.data.getValueAt(0, "ID")}) print("After update recipe name query. Database update successful.") # Return the options return {'options': options} except Exception as e: print("Exception type:", type(e)) print("Error getting ingredients:", e) # Print a message if the if block is not entered print("Did not enter the if block.") ``` isCellEditable: ```auto return True ``` onCellEdited: ```auto self.data = system.dataset.setValue(self.data, rowIndex, colIndex, newValue) ``` ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [November 30, 2023, 2:41pm UTC](https://forum.inductiveautomation.com/t/configureeditor-script-behavior-questions-concerns/82533/2 "2023-11-30T14:41:26Z")
You seem to misunderstand this extension function's purpose. It is called **once** for each _ **column** _ in the table when the table is populated. It is **not** called for each row/column combination that gets edited. This means, if you need certain kinds of dynamic behavior, you need to supply an **editor object** that includes the necessary methods. That custom editor will be called for actual editing activity. (Some [examples here](https://forum.inductiveautomation.com/search?q=TableCellEditor%20order%3Alatest).) Most importantly, that editor is **not** supposed to deliver the result anywhere, except back to the table's internal code. Which then dispatches it to the `onCellEdited` extension function. ---
**Author:** ![Raymond\_Sipes](https://avatars.discourse-cdn.com/v4/letter/r/4491bb/32.png) [@Raymond\_Sipes](https://forum.inductiveautomation.com/u/Raymond_Sipes)\ **Post date:** [November 30, 2023, 2:44pm UTC](https://forum.inductiveautomation.com/t/configureeditor-script-behavior-questions-concerns/82533/3 "2023-11-30T14:44:52Z")
I do believe I am misunderstanding, thank you for the clarification! I will look into some of the articles and see if I can bring some of the functionality over! ---
**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:** [November 30, 2023, 4:06pm UTC](https://forum.inductiveautomation.com/t/configureeditor-script-behavior-questions-concerns/82533/4 "2023-11-30T16:06:58Z")
> [@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):… ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [November 30, 2023, 4:12pm UTC](https://forum.inductiveautomation.com/t/configureeditor-script-behavior-questions-concerns/82533/5 "2023-11-30T16:12:54Z")
Do note that whatever else your editor object does, it must not run database queries or otherwise make gateway calls. You **can** dynamically generate options, but you need to preload the possibilities, as shown in Paul's linked topic. ---
**Author:** ![Raymond\_Sipes](https://avatars.discourse-cdn.com/v4/letter/r/4491bb/32.png) [@Raymond\_Sipes](https://forum.inductiveautomation.com/u/Raymond_Sipes)\ **Post date:** [November 30, 2023, 4:13pm UTC](https://forum.inductiveautomation.com/t/configureeditor-script-behavior-questions-concerns/82533/6 "2023-11-30T16:13:38Z")
Thank you. I already had that linked within my question above though! ---
**Author:** ![Raymond\_Sipes](https://avatars.discourse-cdn.com/v4/letter/r/4491bb/32.png) [@Raymond\_Sipes](https://forum.inductiveautomation.com/u/Raymond_Sipes)\ **Post date:** [November 30, 2023, 4:22pm UTC](https://forum.inductiveautomation.com/t/configureeditor-script-behavior-questions-concerns/82533/7 "2023-11-30T16:22:28Z")
So, would my SELECT statement within the `cofigureEditor` not be advised? I have made some progress with the script(s) by also using the `propertyChange` to update the database once it is ran. Although, i am now running into the issue of the `propertyChange` running on initialization of the screen. I was thinking of adding in `invokeLater` to combat this, although I think this is more of a band aid rather than a fix. configureEditor: ```auto if colName.strip() == "Ingredient": print("Entering the if block.") try: # Assuming "select ingredient" is a valid named query pt = system.db.runNamedQuery("select ingredient") # Construct the list of options using data from each row options = [(pt.getValueAt(row, "Ingredient_ID"), pt.getValueAt(row, "Ingredient")) for row in range(pt.rowCount)] # Set the editor options for the "Ingredient" column return {'options': options} except Exception as e: print("Error configuring editor:", e) ``` propertyChange: ```auto print("prefire") if event.propertyName == "selectedColumn" or event.propertyName == "selectedRow": # Check if the property change event is related to cell selection if event.propertyName == "selectedColumn" and hasattr(event.source, 'selectedColumn') and hasattr(event.source, 'selectedRow'): selectedColumn = event.source.selectedColumn selectedRow = event.source.selectedRow # Check if the selected cell is valid if selectedColumn >= 0 and selectedRow >= 0: print("Selcol") # Check if the selected cell is in the "Ingredient" column if selectedColumn == 4: # Get the selected value from the underlying dataset dataset = event.source.data selectedValue = dataset.getValueAt(selectedRow, selectedColumn) print(selectedValue) print(dataset.getValueAt(selectedRow,0)) try: print("Running??") system.db.runNamedQuery("update recipe name", {"IID": selectedValue, "ID":dataset.getValueAt(selectedRow,0)}) print("Database updated with selected ingredient:", selectedValue) except Exception as e: print("Error updating database:", e) ``` EDIT: I should also point out it will update the DB with the new value, granted it runs as soon as I select the cell to update, rather than when I select the new value. ---
**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:** [November 30, 2023, 4:30pm UTC](https://forum.inductiveautomation.com/t/configureeditor-script-behavior-questions-concerns/82533/8 "2023-11-30T16:30:00Z")
Both of those scripts are running on the main Swing GUI thread, the event dispatch thread or EDT. **Any** blocking call on that thread (such as running a named query, which implies a minimum of two network hops, in both directions) will be immediately visible to end users, as the UI will "freeze" for as long as those scripts take to run. If it's long enough (e.g. in case of a network interruption) the OS will even kick in and warn about an unresponsive process. You _must_ perform your queries off the primary thread _or_ train every single user about this possibility. ---
**Author:** ![Raymond\_Sipes](https://avatars.discourse-cdn.com/v4/letter/r/4491bb/32.png) [@Raymond\_Sipes](https://forum.inductiveautomation.com/u/Raymond_Sipes)\ **Post date:** [November 30, 2023, 4:41pm UTC](https://forum.inductiveautomation.com/t/configureeditor-script-behavior-questions-concerns/82533/9 "2023-11-30T16:41:36Z")
Thank you. I will admit I am not well versed with the thread usage pertaining to scripts. I will read up on this more to get a better understanding moving forward. In the mean time, do you know what would be the best solution to limit this? I am not sure what my next steps should be, possibly IA support? ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [November 30, 2023, 5:07pm UTC](https://forum.inductiveautomation.com/t/configureeditor-script-behavior-questions-concerns/82533/10 "2023-11-30T17:07:56Z")
Do you have to run the query for each row? Whether you do or not, you should be using a Named Query binding on a custom property on the table, using bindings to supply its parameters. Reference that custom dataset property in your custom editor. (Do not run a select query in `configureEditor`, nor in the editor instance's code.) You **cannot** set up different options **per row** using `return {'options': something}` in your configureColumn script. Only a custom editor can do this. ---
**Author:** ![Raymond\_Sipes](https://avatars.discourse-cdn.com/v4/letter/r/4491bb/32.png) [@Raymond\_Sipes](https://forum.inductiveautomation.com/u/Raymond_Sipes)\ **Post date:** [November 30, 2023, 5:12pm UTC](https://forum.inductiveautomation.com/t/configureeditor-script-behavior-questions-concerns/82533/11 "2023-11-30T17:12:31Z")
I would need to run the query for each row they change, yes. I didn't even think about a custom property as a dataset for the query! I will play with this and see what I can come up with. It would have the same options (ingredients) for all rows within the table Thank you @pturmel ! ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [November 30, 2023, 5:19pm UTC](https://forum.inductiveautomation.com/t/configureeditor-script-behavior-questions-concerns/82533/12 "2023-11-30T17:19:47Z")
> [@Raymond\_Sipes](#): > > run the query for each row they change, yes. Contradicts this: > [@Raymond\_Sipes](#): > > same options (ingredients) for all rows Or is the former the update query? If so, that belongs in `onCellEdited`. ---
**Author:** ![Raymond\_Sipes](https://avatars.discourse-cdn.com/v4/letter/r/4491bb/32.png) [@Raymond\_Sipes](https://forum.inductiveautomation.com/u/Raymond_Sipes)\ **Post date:** [November 30, 2023, 5:22pm UTC](https://forum.inductiveautomation.com/t/configureeditor-script-behavior-questions-concerns/82533/13 "2023-11-30T17:22:38Z")
Apologies for the confusion. yes, the SELECT will have the same dataset given whichever row they select. I have now put this into a dataset custom property on the power table. I would want the UPDATE query to run when a cell in any row is changed. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [November 30, 2023, 5:24pm UTC](https://forum.inductiveautomation.com/t/configureeditor-script-behavior-questions-concerns/82533/14 "2023-11-30T17:24:33Z")
Then you **can** use the `{'options': something}` return from `configureColumn`--just generate it from the custom property. No custom dropdown editor required. The update belongs in `onCellEdited`. ---
**Author:** ![Raymond\_Sipes](https://avatars.discourse-cdn.com/v4/letter/r/4491bb/32.png) [@Raymond\_Sipes](https://forum.inductiveautomation.com/u/Raymond_Sipes)\ **Post date:** [November 30, 2023, 5:26pm UTC](https://forum.inductiveautomation.com/t/configureeditor-script-behavior-questions-concerns/82533/15 "2023-11-30T17:26:44Z")
Perfect! I will do this and update the thread if it worked! Thank you again, Phil! EDIT: That solved the issue! Once again Phil saves the day! 😀