Local Report Processing mode

Hi,
We have a scenario where we want to test the <a href> url generated
by parsing the <Hyperlink> element present in the rdl file
This check needs to be done without deploying the rdl file on the
report server. So we are planning to use Local processing mode of the
report view control.
I wanted to ask on whether there are any differences between the
conversion of <Hyperlink> element to <a href> when checked in local
processing mode and when checked in remote processing mode (i.e when
the conversion is done by report server by using reporting server web
services).
Thanks in advancewhat do you mean by "test the <a href>?
do you want to validate that the URL works fine before deploying the report?
the local processing mode of the report viewer can't use an RDL file. you
have to convert it to RDLC. but you also have to execute the query in your
code.
the report viewer just render the report and can't execute the query
statements.
but...
you can validate the hyperlink objects in the RDL file
directly, if the hyperlink is hardcoded. (you can simply use the XML
Document object model to do this)
another option is to publish the report in report server, then execute the
report by code and retrieve the URLS generated in the HTML content to
validate them.
hope this will help you.
"Amit" <amits.84@.gmail.com> wrote in message
news:1182624675.249537.176170@.x35g2000prf.googlegroups.com...
> Hi,
> We have a scenario where we want to test the <a href> url generated
> by parsing the <Hyperlink> element present in the rdl file
> This check needs to be done without deploying the rdl file on the
> report server. So we are planning to use Local processing mode of the
> report view control.
> I wanted to ask on whether there are any differences between the
> conversion of <Hyperlink> element to <a href> when checked in local
> processing mode and when checked in remote processing mode (i.e when
> the conversion is done by report server by using reporting server web
> services).
> Thanks in advance
>|||Thanks for the reply.
I want to validate 2 things with the Hyperlink element which would
contain complex expressions and calls to custom assemblies.
1. Whether the rdl file deploys correctly
2. Whether the url generated is right
This needs to be done without any interaction with the report server.
Hence we wanted to try out local report processing mode. Can you
please guide whether I will be able to validate the above mentioned
scenarios using local processing mode ?
For validating the second scenario I would need to generate an event
of clicking the hyperlink. Is that possible in local report processing
mode ?
I will convert the rdl file to rdlc file. As only <Hyperlink>
scenarios needs to be test I would create a rdl file which contains
only <Hyperlink> element. Renaming this rdl file to rdlc would work as
the schema for both are same. right ?
On Jun 24, 2:33 am, "Jeje" <willg...@.hotmail.com> wrote:
> what do you mean by "test the <a href>?
> do you want to validate that the URL works fine before deploying thereport?
> thelocalprocessingmodeof thereportviewer can't use an RDL file. you
> have to convert it to RDLC. but you also have to execute the query in your
> code.
> thereportviewer just render thereportand can't execute the query
> statements.
> but...
> you can validate the hyperlink objects in the RDL file
> directly, if the hyperlink is hardcoded. (you can simply use the XML
> Document object model to do this)
> another option is to publish thereportinreportserver, then execute thereportby code and retrieve the URLS generated in the HTML content to
> validate them.
> hope this will help you.
> "Amit" <amits...@.gmail.com> wrote in message
> news:1182624675.249537.176170@.x35g2000prf.googlegroups.com...
> > Hi,
> > We have a scenario where we want to test the <a href> url generated
> > by parsing the <Hyperlink> element present in the rdl file
> > This check needs to be done without deploying the rdl file on the
> >reportserver. So we are planning to useLocalprocessingmodeof the
> >reportview control.
> > I wanted to ask on whether there are any differences between the
> > conversion of <Hyperlink> element to <a href> when checked inlocal
> >processingmodeand when checked in remoteprocessingmode(i.e when
> > the conversion is done byreportserver by using reporting server web
> > services).
> > Thanks in advance|||All the above testing scenarios should be done programmatically.
On Jun 24, 6:47 pm, Amit <amits...@.gmail.com> wrote:
> Thanks for the reply.
> I want to validate 2 things with the Hyperlink element which would
> contain complex expressions and calls to custom assemblies.
> 1. Whether the rdl file deploys correctly
> 2. Whether the url generated is right
> This needs to be done without any interaction with thereportserver.
> Hence we wanted to try outlocalreportprocessingmode. Can you
> please guide whether I will be able to validate the above mentioned
> scenarios usinglocalprocessingmode?
> For validating the second scenario I would need to generate an event
> of clicking the hyperlink. Is that possible inlocalreportprocessingmode?
> I will convert the rdl file to rdlc file. As only <Hyperlink>
> scenarios needs to be test I would create a rdl file which contains
> only <Hyperlink> element. Renaming this rdl file to rdlc would work as
> the schema for both are same. right ?
> On Jun 24, 2:33 am, "Jeje" <willg...@.hotmail.com> wrote:
> > what do you mean by "test the <a href>?
> > do you want to validate that the URL works fine before deploying thereport?
> > thelocalprocessingmodeof thereportviewer can't use an RDL file. you
> > have to convert it to RDLC. but you also have to execute the query in your
> > code.
> > thereportviewer just render thereportand can't execute the query
> > statements.
> > but...
> > you can validate the hyperlink objects in the RDL file
> > directly, if the hyperlink is hardcoded. (you can simply use the XML
> > Document object model to do this)
> > another option is to publish thereportinreportserver, then execute thereportby code and retrieve the URLS generated in the HTML content to
> > validate them.
> > hope this will help you.
> > "Amit" <amits...@.gmail.com> wrote in message
> >news:1182624675.249537.176170@.x35g2000prf.googlegroups.com...
> > > Hi,
> > > We have a scenario where we want to test the <a href> url generated
> > > by parsing the <Hyperlink> element present in the rdl file
> > > This check needs to be done without deploying the rdl file on the
> > >reportserver. So we are planning to useLocalprocessingmodeof the
> > >reportview control.
> > > I wanted to ask on whether there are any differences between the
> > > conversion of <Hyperlink> element to <a href> when checked inlocal
> > >processingmodeand when checked in remoteprocessingmode(i.e when
> > > the conversion is done byreportserver by using reporting server web
> > > services).
> > > Thanks in advance|||converting an RDL file to RDLC + code based dataset execution could be
possible, but complicated regarding your development constraints.
also, testing a report should be done 1 time only, after this you can't test
all the cases (I mean you can't test all the possible resultsets coming from
the database)
So, I recommend to spread your code in 2:
1. predeploy testing
2. deploy
the step 1 can be done by deploying the report in a test report server or an
hidden folder in RS. when you publish a report the publish process returns
the warnings and other errors found in the report. (so you can stop the
process here if there is warning, and if there is errors the report is not
deployed)
When this step pass the deployment, you can now execute the report a first
time and scan the resulting HTML content by code.
so you can retrieve all the <a href statements and verify by code if these
links works fine (using the webrequest object in .NET)
and finally, remove the tested report from report server.
now the report is approved for deployment and can be added in your
deployment process.
converting an RDL report to RDLC can be complex because you have to extract
the SQL queries and connections from the report, create and populate a
dataset on the fly and execute the report on the fly. what's appends if
there is parameters?
you can't simulate a direct "click" event on an hyperlink in any scenario.
you can just extract and test the generated HTML content.
but can you explain who creates the reports and how?
because Visual Studio can validate the deployment himself and can "compile"
the report to identify warnings and errors.
also, can you explain how the hyperlinks are created in the reports?
does it's hardcoded (fixed) links? or does the links come from a database?
or does the links is a formula result? (a concatenation of something like:
"http://myserver/myfolder/mypage.aspx?id=" & Datasetfield.Value)
Jerome.
"Amit" <amits.84@.gmail.com> wrote in message
news:1182692843.900480.295280@.e16g2000pri.googlegroups.com...
> Thanks for the reply.
> I want to validate 2 things with the Hyperlink element which would
> contain complex expressions and calls to custom assemblies.
> 1. Whether the rdl file deploys correctly
> 2. Whether the url generated is right
> This needs to be done without any interaction with the report server.
> Hence we wanted to try out local report processing mode. Can you
> please guide whether I will be able to validate the above mentioned
> scenarios using local processing mode ?
> For validating the second scenario I would need to generate an event
> of clicking the hyperlink. Is that possible in local report processing
> mode ?
> I will convert the rdl file to rdlc file. As only <Hyperlink>
> scenarios needs to be test I would create a rdl file which contains
> only <Hyperlink> element. Renaming this rdl file to rdlc would work as
> the schema for both are same. right ?
> On Jun 24, 2:33 am, "Jeje" <willg...@.hotmail.com> wrote:
>> what do you mean by "test the <a href>?
>> do you want to validate that the URL works fine before deploying
>> thereport?
>> thelocalprocessingmodeof thereportviewer can't use an RDL file. you
>> have to convert it to RDLC. but you also have to execute the query in
>> your
>> code.
>> thereportviewer just render thereportand can't execute the query
>> statements.
>> but...
>> you can validate the hyperlink objects in the RDL file
>> directly, if the hyperlink is hardcoded. (you can simply use the XML
>> Document object model to do this)
>> another option is to publish thereportinreportserver, then execute
>> thereportby code and retrieve the URLS generated in the HTML content to
>> validate them.
>> hope this will help you.
>> "Amit" <amits...@.gmail.com> wrote in message
>> news:1182624675.249537.176170@.x35g2000prf.googlegroups.com...
>> > Hi,
>> > We have a scenario where we want to test the <a href> url generated
>> > by parsing the <Hyperlink> element present in the rdl file
>> > This check needs to be done without deploying the rdl file on the
>> >reportserver. So we are planning to useLocalprocessingmodeof the
>> >reportview control.
>> > I wanted to ask on whether there are any differences between the
>> > conversion of <Hyperlink> element to <a href> when checked inlocal
>> >processingmodeand when checked in remoteprocessingmode(i.e when
>> > the conversion is done byreportserver by using reporting server web
>> > services).
>> > Thanks in advance
>