A Lobby link to a hierarchical/structure page (like an estimate's item tree) navigates to a single item's form instead of opening the tree view, even though the equivalent in-app navigation from the tree itself works fine.

Q: A Lobby link to a hierarchical/structure page (like an estimate's item tree) navigates to a single item's form instead of opening the tree view, even though the equivalent in-app navigation from the tree itself works fine.

Use a tree/ prefixed URL (for example, tree/EstimateItem/Tree) instead of the usual page/.../Form pattern when linking to a page that has a treeview — the standard page-form URL pattern lands on the single-record form, while the tree/ prefix specifically targets the treeview presentation of that same page.

Answer

Use a tree/ prefixed URL (for example, tree/EstimateItem/Tree) instead of the usual page/.../Form pattern when linking to a page that has a treeview — the standard page-form URL pattern lands on the single-record form, while the tree/ prefix specifically targets the treeview presentation of that same page.

← Browse Platform, Aurena, and customization questions