I think you can create an attribute called URL, put the link to the other sharepoint page in there - and try!
Don't shoot me if this doesn't work, but unless my memory is playing games with me I think I have done this before.
Here is another example using the URL extended property. The goal was to have an element drive to a new SharePoint page, and also assign the appropriate SVG file to a PI Graphic WebPart.
Three elements in AF:
I then created a SharePoint screen with a PI TreeView and a PI Graphic and called it URL_2.aspx
The PI Graphic webpart has been configured with the query string parameter ‘svg’ for the Selected File in the tool panel.
I have three svg files in the Shared Documents folder:
For each tk element, I added the URL extended property, and pointed to this SharePoint page, and added the following query string parameter:
The first part of the extend property, drives to the SharePoint page:
The next part sets the Selected File of the PI Graphic to the svg file located in the Shared Documents.
The results are that you can click on any of the three elements, the same SharePoint page is called back up, and the PI Graphic file is selected from the query string.
Office: 510.295.0032 | Cell: 602-803-4864 | Fax: 602.896.3996 Mail: email@example.com
This is a good example. I have another question.
How can you link the treeview to open other trend pages on the same page? Is 't possible to have 2 pages side by side (one for the treeview and the other one for the pages to open)?
I have one main treeview for navigation and from there I want to open different pages on the same page. What is the best solution for that?
Microsoft's Page Viewer web part lets you host one page within another, but there are no web part connections supported between the PI TreeView on the containing page and anything included on the contained page. Perhaps you could have a single web part page with PI TreeView and PI Graphic on it, and then let the selections in PI TreeView load different SVG files into PI Graphic?