# Issue passing selected row data to a pop-up

**URL:** <https://forum.inductiveautomation.com/t/issue-passing-selected-row-data-to-a-pop-up/99709>\
**Category:** Ignition\
**Created:** [December 11, 2024, 8:01pm UTC](https://forum.inductiveautomation.com/t/issue-passing-selected-row-data-to-a-pop-up/99709 "2024-12-11T20:01:15Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**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:** [December 12, 2024, 2:56pm UTC](https://forum.inductiveautomation.com/t/issue-passing-selected-row-data-to-a-pop-up/99709/4 "2024-12-12T14:56:47Z")

</div>

Python's `Exception` class doesn't include the panoply of java exceptions that can occur, particularly any SQLException that JDBC can throw. You should include another `except Throwable, t:` clause for those, where you include a

```python
from java.lang import Throwable

```

above your `try:`. (Preferably in a project library script where you delegate your event and action scripts, so it can be imported as a persistent global.)

Also, note that stringifying an exception loses the traceback, which is a real problem for java exceptions, since the traceback has any chained "caused by" inner exceptions. You should **log** your exceptions, using the logger methods that take a `Throwable`.

---

_[View the full topic](https://forum.inductiveautomation.com/t/issue-passing-selected-row-data-to-a-pop-up/99709)._