OSIsoft: Connecting Excel Web Access (EWA) and PI WebParts. v2.2


Uploaded by OSIsoftLearning on 24.05.2011

Transcript:

We just saw a connection
to the Excel Web Access WebPart from just one of
the standard WebParts, the text filter.
But you can also make connections from some of
our other RtWebParts. And they are very good connections.
For example, within the RtTableTimeSeries or
Values WebParts, you can make a connection such that
when you look at
or click on a row within
any of those WebParts, we will pass that
tag name over to the Excel Web Access.
So for example, as you can see, I'm currently looking
at CDT158. If I click right here
it's going to go ahead and send the
tag name over to that named range.
So that's a connection
that is done from one of these, in this case the RtValues WebPart.
So that's kind of nice to have. You can
simply click and get whatever you want in
terms of the Web Access WebPart.
Now in addition you can take
things from our module database
that are exposed by the RtTreeView WebPart
and send that over to the
Excel Web Access. So for example, we are currently
looking at Unit B. And here is an RtTreeView
WebPart that is showing me Unit A, B
and C from the module database. When I click on Unit A,
as you can see, we pass that Unit over here
and everything as a consequence on this spreadsheet changes.
Because the tag changes, the
data we see over here, it all changes because this is
module relative. And of course in
addition, we can make connections using start time and
end time from the RtTimeRange. So we are currently
looking at 2 hours. As you can see, this is the
2 hour period right down here, 1400 - 1600.
If I were to change this, let's make this
4 hours and go ahead and apply,
again using the connection we can see this is
now gone to 4 hours instead of 2 hours.
We can see the change right there.
Now this increased functionality
is very powerful and of course
when you are talking about
computers, generally when you hear the word powerful,
it often is a kind of warning that is also means
extremely difficult to configure and this is no different.
Actually I'm being facetious, it's not that difficult to configure.
But there are some tricks
that can be stumbling blocks when you are
trying to get this setup for the first time. I'll give you
an example, let's go back to this right here.
This if you recall, I'm saying when you click here,
it's going to go ahead and send that over.
Well it sends over whatever
the provider has been configured to send over.
And by default, what it will send over is something
called the dataset. This dataset here is actually a
combination server name and tag name.
And if I were to simply send that over,
unless I've configured the spreadsheet to receive
it properly and perhaps filter it using
Excel functions, it's simply going to fail. It's
going to dump that kind of a string into here which will not work.
So if you go into the connections section here,
choose send filter
data to that Excel Web Access.
You'll notice when you specify that
this is where you identify
the destination.
That's pretty straightforward. We're going to
send the information from that provider over
to the destination called Tag Name, that's a named range
on the Excel Web Access.
So within the configuration of that connection,
that's where we specify the destination.
What it is that we actually send is
configured elsewhere and that is
configured in the definition for that
Web Part. So if I choose RtValues,
Edit, Modified Shared WebPart,
that's where I actually configure what it is
that I'm going to send.
So if I scroll down here,
you will notice one of the options here
is filter values.
And what this filter value
option does is it gives you a choice
of what it is that you will
effectively send if you are connecting
to another Web Part and using this as a filter.
Now I've specified that I'm going to send the tag
name. But as you can see,
there are many different things that you can send.
Now the default is this right here, Dataset.
Watch what happens if you accept the default.
As I was saying, it's complex because it's one of those deceptively
complex things. You initially do the
connection, you get the connection correct by
setting up any edit connections.
I'll have it go to the Excel Web Access and
you specify the proper destination. It's going to that
particular field. But watch what happens
if you've done it like that. When you make the change,
we send it but we are sending exactly what you told us to send
which is the Dataset. See this, OSISoft CDM-158.
It's not a problem if your spreadsheet
is configured to receive
it correctly. But in this case, it's not.
And typically it won't be.
Typically within the spreadsheet, we are using just a simple
tag name. So that's what I mean
by it can be complex.
So just make sure that when you setup this
connection, in the filters section, you specify
the right thing to send. In this case, that would be the tag name.
So here is before and after.
And now I'm sending the correct thing.
And as a result, now we are sending
just the tag name.
Now in our next videos, we are going to take a look at a couple of
other things that are a little more complex
than you might guess when you first configure them.