not sure if I got you right (or you are thinking to complicate ).
I created a query to show four tags. afterward I created a webpart page and put the RtTable webpart with this query on it. If i add another RtValues and simply connect the two webparts together (no filter setting, simply provide parameters) and later on select that the RtTable time column populates the Endtime of the value object and this seems to do the job (clicking on the timestamp in the RtTable adjusts the timestamp in the RtValues).
- I add the RtTable
- I set it up to use my dataset
- I create a behaviour for the dataset, making the Time column into a hyperlink, and apply the behaviour to the RtTable
- I add the RtValues
- I connect the RtTable to RtValues using "Provide parameters to..."
- At this point the RtValues does not have any tags, datasets or connections, under Selected Data. Clicking the timestamp-link in RtTable will now result in an error message:
[21.04.2009 10:02:05] \\hau-s010\07.04.2009 16:56:00: PIPoint not found. \\hau-s010\07.04.2009 16:56:00
Here my pi server is 'hau-s010' and as you can see, the timestamp '07.04.2009 16:56:00' is treated as a tag.
What is the next step - do I need to create a dataset, and connect the time-column from RtTable to a placeholder in the relational query for RtValues? (Where I set up the placeholder as a 'date' with 'endtime'?
3 - I did not create a behavior - what did you set up as behavior for the time column?
4 - I had tags already in the RtValues. But i just checked and that is not the problem.
I set the behaviour up with the time column as a hypelink, and selected the "provide row data" (last choice) as link.
But just to follow your example, I removed the behaviour. I also put 2 tags in the RtValues table (sinusoid and sinusoidu), and made sure that the time column is filtered by. (I have selected time, tagname and value to be shown).
Now I should have a setup equal to your setup. But there's no reaction in the RtValues table, when clicking in the RtTable. RtValues just shows snapshot-values - the time doesn't change at all.
Thanks Andreas, I just got it now. The connection icon wasn't green, so the EndTime wasn't set properly.
Anyways - I did get the result I wanted yesterday, but with a slightly different approach. Instead of using an RtValues table as the secondary webpart, I used another RtTable. I set up a relational dataset with a ? placeholder for the time. After doing that, a connection group box appeared in the 'modify shared webpart' config for the RtTable 2 - where I could connect the time column from RtTable1 - which I turned into a hyperlink with a behaviour - to the placeholder in the sql query.
But I wanted to see the solution to the RtTable-RtValues setup as well, so thank you for your help!
It's great seeing and learning the possibilities we actually have with RtWebparts. We've kind of made our own webparts/solutions when we hit the wall previously, but it's a huge timesaver for both us and our customers when we can utilize all of the RtWebparts' built-in functionality.