Hi all,
I'm having the following issue with a table cell rendering as a view. The view is a simple checkbox: changing the checkbox state will update a database table record and trigger a binding refresh of the perspective table data.
The problem is: just after checkbox clicking, the cell rendering is odd as in the following screenshot (the row just edited is the first one)
Any suggestion?
P.S.: I had to use the view with checkbox instead of the native checkbox rendering because with the native solution, operators have to click twice to change the checkbox state and that gets rather annoying after almost 100 clicks!
1 Like
I assume the first column has render set to "auto", rather than "boolean"?
If you have inadvertently added some whitespace to the value, then it will appear exactly as you have described, as a string.
1 Like
No @simeonw , render mode is set to view, there's a view that's rendering the cell and I explained why I chose that way in my post. Moreover the issue arises whenever the render mode is set to view: I experienced the same weird behavior even with views with a dropdown: there the first rendering after update was a simple textfield with the new value, dropdown was simply gone. I think that's a general issue that Inductive Automation has with that kind of rendering, unfortunately.
Ahh I see. You have an embedded view, but when you click it, the cell is entering edit mode (text field), like any other editable cell would.
Is it not just a matter of disabling the "editable" property on that column? Shouldn't be necessary to have it enabled if you are updating the value in the database.
Otherwise, just switch the cells.allowEditOn back to double-click or long-press, as it currently must be set to single-click?