# Converting Table(MsSQL) to tree component in ignition perspective **URL:** \ **Category:** Ignition\ **Tags:** python, ignition80, database, scripting, perspective\ **Created:** [July 14, 2020, 6:45am UTC](https://forum.inductiveautomation.com/t/converting-table-mssql-to-tree-component-in-ignition-perspective/36671 "2020-07-14T06:45:21Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\ **Post date:** [June 23, 2023, 1:50pm UTC](https://forum.inductiveautomation.com/t/converting-table-mssql-to-tree-component-in-ignition-perspective/36671/3 "2023-06-23T13:50:07Z")
By coincidence I have asked a very similar question just a few minutes ago. Any answer to mine may be of interest. > [@Text tree to Tree component 'items' property](https://forum.inductiveautomation.com/t/text-tree-to-tree-component-items-property/75453/1): > > I'm experimenting with using the Tree component for navigation rather than the Menu Tree. It offers the user clear visibility of where in the site they are whereas the Menu Tree doesn't. I'm making the tree configurable within the application (subject to user roles) and want to use a simple markup structure to generate the Tree's props.items. Markup would look like this with the syntax anchor text | page URL. The URL can be passed to the tree's onActionPerformed event to cause a navigation to … --- _[View the full topic](https://forum.inductiveautomation.com/t/converting-table-mssql-to-tree-component-in-ignition-perspective/36671)._