Creating pretty and functional tables in Dashboard 2.0

[@VladoM]

Another perfect and helpful tutorial, Csongor. Thanks

[@csongorvarga]

Glad you liked it!

[@paulgul1]

Thanks for the informative video, just downloaded your example, should help me understand the basics

[@csongorvarga]

You are welcome!

[@MrBrian9107]

thanks for share!!, can you show how edit any row value and push on payload?

[@paulgul1]

How are the column widths set? I notice in the name column it goes to a second line sometimes so something must be restricting the column width. For reference, when I move the mouse over the headers they disappear so it's not just your settings - I don't know why, when I made a very simple table from a template the headers don't disappear

[@csongorvarga]

I did not look into the column width yet. I noticed for a lot of element that the background colors are incorrect and need to be overwritten with custom styleing. I will mention that in a future video if I have the solution.

[@Joestar-o2s]

I find that if I make any mistakes with the template, my dashboard freezes up and my nodered admin area also locks up. Very hard to debug.

[@csongorvarga]

@user-vp5uo6oq5b That is definitely not normal. Is there anything in the node red log to suggest why it lock up?

[@mircopolo]

Is it possible to create a table that can be used on multiple browsers without affecting each other during sorting, filtering etc ?

[@csongorvarga]

I did not test this, but my understanding that the filters and sorting is happening on the client. Therefore each browser does it independetly.

[@mircopolo]

Let's say the are 2 buttons "select all" and "select filtered" which are used to trigger sql query, then data is sent to a table. If 2 browsers display the same page, I click "select filtered" on browser 1 the same will appear on browser 2 even if last user action there was "select all" button

[@csongorvarga]

@@mircopolo I have a new dialog video coming out soon. In that one I will show and example how to check the client session ID to ensure message is only processed by the current session. The same technique could be used for the table as well. You bind the table items to a local variable and you only copy msg.payload into this variable if the socket.id is the same.