Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
Hi all
I am trying to get the nodeKey of an node (ie. "'webfx-tree-object-35") from the nodeID (ie. "1611")
Is this possible?
Thanks,
Mathias
Hi Mathias,
Can you explain a bit more as to why you'd need the nodeKey of a node? I assume this is the tree "id" of the node, right?
Looking forward to more info.
Regards,
/Dirk
Hi Dirk
Yes, the tree id it is! I have an AfterSave Event handler wich sorts certain subnodes, and to get the sorting to show up in the backend, the Parent node must be refreshed. Therefore i use this code:
((BasePage)doc.HttpContext.CurrentHandler).ClientScript.RegisterClientScriptBlock(GetType(), Guid.NewGuid().ToString(), "<script>parent.tree.webFXTreeHandler.all['webfx-tree-object-35'].reload();</script>");
The javascript needs the nodeKey to work ('webfx-tree-object-35'), and all i have is the nodeID.
I hope this makes sense.
Thanks, Mathias
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.
Continue discussion
Get nodeKey from ID
Hi all
I am trying to get the nodeKey of an node (ie. "'webfx-tree-object-35") from the nodeID (ie. "1611")
Is this possible?
Thanks,
Mathias
Hi Mathias,
Can you explain a bit more as to why you'd need the nodeKey of a node? I assume this is the tree "id" of the node, right?
Looking forward to more info.
Regards,
/Dirk
Hi Dirk
Yes, the tree id it is! I have an AfterSave Event handler wich sorts certain subnodes, and to get the sorting to show up in the backend, the Parent node must be refreshed. Therefore i use this code:
The javascript needs the nodeKey to work ('webfx-tree-object-35'), and all i have is the nodeID.
I hope this makes sense.
Thanks, Mathias
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.