Hi,
I’m working with a dynamic table where each row represents a network interface, and one of the columns is a toggle button (Enable/Disable) configured as a write parameter.
What I want to implement is the following behavior:
When the user enables the toggle (value = 1) on a row, I want to:
Extract all the information related to that interface (from a previously loaded JSON).
Insert that interface into another table (a “selection” table used for monitoring or filtering).
When the user disables the toggle (value = 0), I want to:
Remove the corresponding row from the selection table.
The goal is to allow users to dynamically build a custom list of interfaces by enabling or disabling the toggle per row, and keep the selection synchronized accordingly.
My questions are:
Is this the correct or recommended approach in DataMiner for this type of row-level interaction using toggles?
Is there any native or better way to manage row state and copy information between tables using toggles, especially in terms of performance or best practices?
Is there a clean way to persist the toggle state per row and automatically rebuild the selection table after a protocol restart?
Thank you
Hi Jose,
Based on your explanation, I do not have any concerns with the implementation. One enhancement you might consider is adding a context menu. For example, to include or exclude all interfaces at once. Whit this, users do not have to manually enable or disable each row individually.
To keep the current values between element restarts, you can use the parameter "save" attribute.
Context menu docs: Custom table context menu | DataMiner Docs
Save attribude: save attribute | DataMiner Docs
Hope this helps!