I've developed a view using the table component, but due to the way the data is bound, it currently requires multiple clicks to access key information.
The user is looking to enhance the design to reduce the number of interactions and streamline usability.
I am unable paste the screenshot here, will explain how the current design is,
I currently have a table where clicking the row expands a subview. That subview contains flex containers, labels, buttons, and another table. When a row in another table is expanded, the same subview opens again with details for the selected sub‑ID. This drill‑down process continues for three to four levels.
Could you suggest which components in Ignition Perspective would be best suited to improve this design?
As you have multi deep level of data the best is use tree component of the left side of view and user can quicky select what layer he wants and click on and then update the table base on that which take your whole view.
Hi, I tried this tree component, customer accepted this approach.
Now I am trying actual implementation, trying to bind the dataset in tree view but it’s not working.
I think you need to mock up your desired layout to make it clear to your readers how you think this should work. For example, if the user selects something three levels down in the tree then why not just display one associated table?
When a user clicks any node, the corresponding view can be displayed. Now I’m working on binding data to the tree structure.
For example, I have shiftData. I want to bind each shift to the main (root) node. For each child node, I want to display the loads associated with the selected shift. The third‑level nodes should then depend on the load that was selected.
But as I mentioned earlier, I’m not able to paste a screenshot here. It seems my company’s policies are blocking it, which is why I tried to explain the issue using an example instead.