Table clearing error

william.ivey · September 13, 2022, 6:29pm

When trying to clear the selection on a table in Perspective, I am getting the error below. Does anyone know if this is a bug with the software? (using version 8.1.19 here)

13:24:33.701 [Browser Thread: 57184] ERROR Perspective.Designer.Workspace - level: LEVEL_ERROR
message: “Uncaught TypeError: Cannot read property 'Line_Path' of undefined”
line_number: 32
source: “http://srv14aigd02.netit.itc.com/res/perspective/js/react-dom-16.14.0.js”

dkhayes117 · September 13, 2022, 7:14pm

post your script, here are some hints from your error message

Cannot read property 'Line_Path' of undefined
...
"line number":32,"column":337}}”
...

william.ivey · September 13, 2022, 7:24pm

At the point this is firing, there is no logic pointed at or using those properties.

There are no event scripts associated to this error. This happens by simply clicking on the table or surrounding flex container.

It feels like its inherent to the table object, but could be inherent to its container.

dkhayes117 · September 13, 2022, 7:33pm

Is this in the designer or a perspective session?

william.ivey · September 13, 2022, 7:33pm

Both

lrose · September 13, 2022, 7:38pm

The errors shown in your post all occur in a Java Script file, so those at least are from the component. However, this doesn’t look like the full stack trace.

I would expect a “caused by” statement at some point.

william.ivey · September 13, 2022, 7:45pm

The error information gathered above is from the designer. I cleared everything in my logs before attempting to deselect a row on a table. Everything I posted above is what Ignition applied to the logs.

william.ivey · September 13, 2022, 7:53pm

The error information gathered above is from the designer. I cleared everything in my logs before attempting to deselect a row on a table. Everything I posted above is what Ignition applied to the logs.

Just attempted the same functionality with a new button using its click event and this logic. I am still receiving the same error.

self.parent.parent.getChild(“flxCntTables”).getChild(“flxCntInput”).getChild(“flxCntBody”).getChild(“Table”).props.selection.selectedRow = None

lrose · September 13, 2022, 10:35pm

I wasn’t able to reproduce any error. However, I also wasn’t able to clear the selection from a table using a script.

I would expect setting the selectedRow to -1 to work, however, the selection just stays. I also tried clearing the selection data array, but that also didn’t clear the highlighted row.

I just added a table and a button to a view and added this script to the actionPreformed event of the button.

self.getSibling("Table").props.selection.selectedRow = -1

Perhaps @cmallonee has some insight into how to properly clear selected rows from a table component.

justinedwards.jle · September 14, 2022, 12:56am

I don’t seem to get any errors when I fire the following code form the onClick event from a button, and it seems to deselect everything:

	self.getSibling("Table").props.selection.selectedColumn = None
	self.getSibling("Table").props.selection.selectedRow = None

justinedwards.jle · September 14, 2022, 1:01am

I don’t believe this is a bug, I would look at the Event Configuration for the root container, and see if there is some erroneous code causing the issue.

cmallonee · September 14, 2022, 1:46am

Could you please supply the code you are using to “clear the selection” when this occurs? We’re all just guessing until we see how you’re clearing the selection data in the first place.

lrose · September 14, 2022, 2:30am

Deselecting the column was what I was missing. Not sure why I didn’t think of that, lets chalk it up to lack of sleep.

self.getSibling("Table").props.selection.selectedRow = -1
self.getSibling("Table").props.selection.selectedColumn = -1

justinedwards.jle · September 14, 2022, 8:58am

Something that happens to me every now and then in Perspective is right clicking over an unselected component, and then, as a consequence, I end up writing a script in a different component than I intended to [the component that was actually selected]. To me, this scenario seems feels like the aforementioned situation. It feels like a script has been inadvertently written to the wrong place, and these errors are the unintended consequence.

ynejati · October 31, 2022, 3:26pm

At the moment, if you need to clear selection, just set both the selectedColumn and selectedRow properties to None or null. Currently, the selection data is intended to be read only. It looks like by clearing it, we might be interfering with some internal book keeping of selection data. We will look into it, but for now all you need to do is set selectedColumn and selectedRow to null, and the Table will clear the selected data for you.

william.ivey · November 3, 2022, 11:45am

Thanks for the feedback. I had a colleague mention the same thing as well. Much appreciated.