Hey @mdsmith1. In my view, it makes sense from a UI/UX perspective that checkbox selection is limited to multi-row selection. This indicates to users that multiple selections are possible. It also makes multiple selections easier, without having to hold down Ctrl or some other key whilst clicking on rows.
Such a UI element is somewhat redundant in a table with only single-row selection - and also takes up valuable real estate. You can customise the appearance of rows on hover and on selection to make interactions more obvious.
Ryan:
It seems that identification of the selection is easier if the check box is turned on. But I can find a way around it so I will not pursue this any further
Mike
Oh my mistake! You might try using an event handler that references {{ table1.selectedRow.data.Invnumber }}:
Otherwise, if you use a JavaScript query or a script instead of a SQL query, you can call localStorage.setItem('minvnumber', talbe1.selectedRow.data.Invnbr).
Henry:
I got it to work but I had to add some extra code which you can see in the attached screens.
I run your code first which seems to get the pointer in the right place. This code on its own does not seem to run when clicked.
The second piece of code sends 'minvnumber' up to the Local Storage.
So I am out of the woods.
Thanks Henry.
Mike