"Abdul Malik Said" <diplacusis@hotmNOSPAMail.com> wrote in message
news:uS1iYsrhEHA.3916@TK2MSFTNGP11.phx.gbl...
> Does anyone know anything about the client-side Javascript that is
generated
> by the report server, or where it is documented? For instance, if you
"View
> Source" for any report, you will see a page that has several frames for
the
> parameters, toolbar and report. Each of these sections must be generated
by
> the Report Server and sent to the client.
>
> I am trying to modify the behaviour of the parameter toolbar, or at least
> attach some code to it. Has anyone else tried to do this or can someone
> advise me if this is feasible?
>
> Specifically, I am looking at the "tbDMRepFrameUrl" property, and several
> others like it. I see variables like this being set in the javascript
which
> represent the report being currently displayed. I can see in the URL that
is
> in this variable all of the report parameters that are being set. If I
copy
> and paste this URL into a browser, I will get the report with the same
> parameters.
>
> The problem is I found this tbDMRepFrameUrl in the toolbar frame, and it
is
> referenced in code by saying:
> parent.tbDMRepFrameUrl = "..."
>
> Does anyone know about these URL properties and how I might be able to
> access them?
>
> Any information, general or specific, would be appreciated.
>
> Thanks,
> Malik
>
>

"Brian Hartman [MSFT]" <brianhartman@hotmail.com> wrote in message
news:eIoH5NuhEHA.632@TK2MSFTNGP12.phx.gbl...
> These variables are for internal use. We do not document them and do not
> support clients changing them. Their usage may change in a future
release.
>
> We do support modifying the style of the toolbar with the rc:stylesheet
> parameter. But we do support a method for you to extend the toolbar in
> script.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
>
> "Abdul Malik Said" <diplacusis@hotmNOSPAMail.com> wrote in message
> news:uS1iYsrhEHA.3916@TK2MSFTNGP11.phx.gbl...
> > Does anyone know anything about the client-side Javascript that is
> generated
> > by the report server, or where it is documented? For instance, if you
> "View
> > Source" for any report, you will see a page that has several frames for
> the
> > parameters, toolbar and report. Each of these sections must be generated
> by
> > the Report Server and sent to the client.
> >
> > I am trying to modify the behaviour of the parameter toolbar, or at
least
> > attach some code to it. Has anyone else tried to do this or can someone
> > advise me if this is feasible?
> >
> > Specifically, I am looking at the "tbDMRepFrameUrl" property, and
several
> > others like it. I see variables like this being set in the javascript
> which
> > represent the report being currently displayed. I can see in the URL
that
> is
> > in this variable all of the report parameters that are being set. If I
> copy
> > and paste this URL into a browser, I will get the report with the same
> > parameters.
> >
> > The problem is I found this tbDMRepFrameUrl in the toolbar frame, and it
> is
> > referenced in code by saying:
> > parent.tbDMRepFrameUrl = "..."
> >
> > Does anyone know about these URL properties and how I might be able to
> > access them?
> >
> > Any information, general or specific, would be appreciated.
> >
> > Thanks,
> > Malik
> >
> >
>
>

"Abdul Malik Said" <diplacusis@hotmNOSPAMail.com> wrote in message
news:%23R8GG6OiEHA.636@TK2MSFTNGP12.phx.gbl...
> Thanks Brian,
>
> I am confused... your statement below says:
> "But we do support a method for you to extend the toolbar in script"
> I assume you mean that you DO NOT support extending the toolbar in script?
>
> This was my last-ditch effort to find out what the current URL of the
report
> being displayed on a page is. If you know of any other method to get this
> information from SOAP object model or URL integration, please let me know.
>
> The only way I have found is to re-invent parameter inputs, which would
> involve me re-programming the parameter toolbar in order to accept every
> possible combination of parameters!
>
> Malik
>
> "Brian Hartman [MSFT]" <brianhartman@hotmail.com> wrote in message
> news:eIoH5NuhEHA.632@TK2MSFTNGP12.phx.gbl...
> > These variables are for internal use. We do not document them and do
not
> > support clients changing them. Their usage may change in a future
> release.
> >
> > We do support modifying the style of the toolbar with the rc:stylesheet
> > parameter. But we do support a method for you to extend the toolbar in
> > script.
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no
rights
> >
> > "Abdul Malik Said" <diplacusis@hotmNOSPAMail.com> wrote in message
> > news:uS1iYsrhEHA.3916@TK2MSFTNGP11.phx.gbl...
> > > Does anyone know anything about the client-side Javascript that is
> > generated
> > > by the report server, or where it is documented? For instance, if you
> > "View
> > > Source" for any report, you will see a page that has several frames
for
> > the
> > > parameters, toolbar and report. Each of these sections must be
generated
> > by
> > > the Report Server and sent to the client.
> > >
> > > I am trying to modify the behaviour of the parameter toolbar, or at
> least
> > > attach some code to it. Has anyone else tried to do this or can
someone
> > > advise me if this is feasible?
> > >
> > > Specifically, I am looking at the "tbDMRepFrameUrl" property, and
> several
> > > others like it. I see variables like this being set in the javascript
> > which
> > > represent the report being currently displayed. I can see in the URL
> that
> > is
> > > in this variable all of the report parameters that are being set. If I
> > copy
> > > and paste this URL into a browser, I will get the report with the same
> > > parameters.
> > >
> > > The problem is I found this tbDMRepFrameUrl in the toolbar frame, and
it
> > is
> > > referenced in code by saying:
> > > parent.tbDMRepFrameUrl = "..."
> > >
> > > Does anyone know about these URL properties and how I might be able to
> > > access them?
> > >
> > > Any information, general or specific, would be appreciated.
> > >
> > > Thanks,
> > > Malik
> > >
> > >
> >
> >
>
>

"Abdul Malik Said" <diplacusis@hotmNOSPAMail.com> wrote in message
news:eZ6wy$diEHA.1356@TK2MSFTNGP09.phx.gbl...
> Thanks Brian,
>
> Am I correct that for your solution I would have to program my own
parameter
> inputs? I want to avoid doing this because then I would have to program a
> general-purpose parameters toolbar that correctly gets any combination of
> parameters for any report from the user
>
> What I would really like to do is take a variable that the tool bar sets.
I
> can see it, and it is called:
>
> tbDMRepFrameUrl
>
> This is set in the parent frame of the toolbar, and I can see it at
runtime.
> I am surprised that there is no way to simply access this property using
> SOAP or URL methods. All I really want to do is take that URL, which is
the
> current URL being displayed as chosen by the user from the toolbar, and
save
> it to generate the next report.
>
> Is there any easier way without re-developing the parameter input code
that
> microsoft has already written?
>
> Malik
>
> "Brian Hartman [MSFT]" <brianhartman@hotmail.com> wrote in message
> news:#jXBJ0UiEHA.3944@tk2msftngp13.phx.gbl...
> > You are correct, that was a typo. I should have said "do not".
> >
> > You can use the SOAP API to get the list of parameters for a report and
to
> > update the list based on the current selection (for heirarchical
> > parameters). Once you have a set of parameters from the user, you can
> > specify them on the URL to the reportserver in a simple
> > ParameterName=ParameterValue format. If you also add
rc:parameters=false,
> > the built in parameters area will not be displayed, but you will still
get
> > the other functionality such as the page navigation, export, and
document
> > map. Basically, you can add your own information to the page and submit
> it
> > to the server, but there is no way for you to add things to the built in
> > areas.
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no
rights
> >
> > "Abdul Malik Said" <diplacusis@hotmNOSPAMail.com> wrote in message
> > news:%23R8GG6OiEHA.636@TK2MSFTNGP12.phx.gbl...
> > > Thanks Brian,
> > >
> > > I am confused... your statement below says:
> > > "But we do support a method for you to extend the toolbar in script"
> > > I assume you mean that you DO NOT support extending the toolbar in
> script?
> > >
> > > This was my last-ditch effort to find out what the current URL of the
> > report
> > > being displayed on a page is. If you know of any other method to get
> this
> > > information from SOAP object model or URL integration, please let me
> know.
> > >
> > > The only way I have found is to re-invent parameter inputs, which
would
> > > involve me re-programming the parameter toolbar in order to accept
every
> > > possible combination of parameters!
> > >
> > > Malik
> > >
> > > "Brian Hartman [MSFT]" <brianhartman@hotmail.com> wrote in message
> > > news:eIoH5NuhEHA.632@TK2MSFTNGP12.phx.gbl...
> > > > These variables are for internal use. We do not document them and
do
> > not
> > > > support clients changing them. Their usage may change in a future
> > > release.
> > > >
> > > > We do support modifying the style of the toolbar with the
> rc:stylesheet
> > > > parameter. But we do support a method for you to extend the toolbar
> in
> > > > script.
> > > >
> > > > --
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights
> > > >
> > > > "Abdul Malik Said" <diplacusis@hotmNOSPAMail.com> wrote in message
> > > > news:uS1iYsrhEHA.3916@TK2MSFTNGP11.phx.gbl...
> > > > > Does anyone know anything about the client-side Javascript that is
> > > > generated
> > > > > by the report server, or where it is documented? For instance, if
> you
> > > > "View
> > > > > Source" for any report, you will see a page that has several
frames
> > for
> > > > the
> > > > > parameters, toolbar and report. Each of these sections must be
> > generated
> > > > by
> > > > > the Report Server and sent to the client.
> > > > >
> > > > > I am trying to modify the behaviour of the parameter toolbar, or
at
> > > least
> > > > > attach some code to it. Has anyone else tried to do this or can
> > someone
> > > > > advise me if this is feasible?
> > > > >
> > > > > Specifically, I am looking at the "tbDMRepFrameUrl" property, and
> > > several
> > > > > others like it. I see variables like this being set in the
> javascript
> > > > which
> > > > > represent the report being currently displayed. I can see in the
URL
> > > that
> > > > is
> > > > > in this variable all of the report parameters that are being set.
If
> I
> > > > copy
> > > > > and paste this URL into a browser, I will get the report with the
> same
> > > > > parameters.
> > > > >
> > > > > The problem is I found this tbDMRepFrameUrl in the toolbar frame,
> and
> > it
> > > > is
> > > > > referenced in code by saying:
> > > > > parent.tbDMRepFrameUrl = "..."
> > > > >
> > > > > Does anyone know about these URL properties and how I might be
able
> to
> > > > > access them?
> > > > >
> > > > > Any information, general or specific, would be appreciated.
> > > > >
> > > > > Thanks,
> > > > > Malik
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

"Brian Hartman [MSFT]" <brianhartman@hotmail.com> wrote in message
news:#jXBJ0UiEHA.3944@tk2msftngp13.phx.gbl...
> You are correct, that was a typo. I should have said "do not".
>
> You can use the SOAP API to get the list of parameters for a report and to
> update the list based on the current selection (for heirarchical
> parameters). Once you have a set of parameters from the user, you can
> specify them on the URL to the reportserver in a simple
> ParameterName=ParameterValue format. If you also add rc:parameters=false,
> the built in parameters area will not be displayed, but you will still get
> the other functionality such as the page navigation, export, and document
> map. Basically, you can add your own information to the page and submit
it
> to the server, but there is no way for you to add things to the built in
> areas.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
>
> "Abdul Malik Said" <diplacusis@hotmNOSPAMail.com> wrote in message
> news:%23R8GG6OiEHA.636@TK2MSFTNGP12.phx.gbl...
> > Thanks Brian,
> >
> > I am confused... your statement below says:
> > "But we do support a method for you to extend the toolbar in script"
> > I assume you mean that you DO NOT support extending the toolbar in
script?
> >
> > This was my last-ditch effort to find out what the current URL of the
> report
> > being displayed on a page is. If you know of any other method to get
this
> > information from SOAP object model or URL integration, please let me
know.
> >
> > The only way I have found is to re-invent parameter inputs, which would
> > involve me re-programming the parameter toolbar in order to accept every
> > possible combination of parameters!
> >
> > Malik
> >
> > "Brian Hartman [MSFT]" <brianhartman@hotmail.com> wrote in message
> > news:eIoH5NuhEHA.632@TK2MSFTNGP12.phx.gbl...
> > > These variables are for internal use. We do not document them and do
> not
> > > support clients changing them. Their usage may change in a future
> > release.
> > >
> > > We do support modifying the style of the toolbar with the
rc:stylesheet
> > > parameter. But we do support a method for you to extend the toolbar
in
> > > script.
> > >
> > > --
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights
> > >
> > > "Abdul Malik Said" <diplacusis@hotmNOSPAMail.com> wrote in message
> > > news:uS1iYsrhEHA.3916@TK2MSFTNGP11.phx.gbl...
> > > > Does anyone know anything about the client-side Javascript that is
> > > generated
> > > > by the report server, or where it is documented? For instance, if
you
> > > "View
> > > > Source" for any report, you will see a page that has several frames
> for
> > > the
> > > > parameters, toolbar and report. Each of these sections must be
> generated
> > > by
> > > > the Report Server and sent to the client.
> > > >
> > > > I am trying to modify the behaviour of the parameter toolbar, or at
> > least
> > > > attach some code to it. Has anyone else tried to do this or can
> someone
> > > > advise me if this is feasible?
> > > >
> > > > Specifically, I am looking at the "tbDMRepFrameUrl" property, and
> > several
> > > > others like it. I see variables like this being set in the
javascript
> > > which
> > > > represent the report being currently displayed. I can see in the URL
> > that
> > > is
> > > > in this variable all of the report parameters that are being set. If
I
> > > copy
> > > > and paste this URL into a browser, I will get the report with the
same
> > > > parameters.
> > > >
> > > > The problem is I found this tbDMRepFrameUrl in the toolbar frame,
and
> it
> > > is
> > > > referenced in code by saying:
> > > > parent.tbDMRepFrameUrl = "..."
> > > >
> > > > Does anyone know about these URL properties and how I might be able
to
> > > > access them?
> > > >
> > > > Any information, general or specific, would be appreciated.
> > > >
> > > > Thanks,
> > > > Malik
> > > >
> > > >
> > >
> > >
> >
> >
>
>