hi,
after changing the order of my report parameters (in this example test)
in the menue via the up and down arrow I get the following error
message:
an error occured during local processing. an error occured during
report processing. the value expression for the query parameter 'date'
contains an error: the expression referenced a non-existing parameter
in the report parameters collection.
anybody knows how to do this?
thanksIt sounds like you have either:
A) deleted a parameter which was there before, or more likely
B) changed the sequence required for cascading parameters, i.e. parameters
where one value depends on another one previously entered. It is probably
something to do with one of your report parameters' 'available values' or
'default values' definitions.
HTH,
Magendo_man
"florian" wrote:
> hi,
> after changing the order of my report parameters (in this example test)
> in the menue via the up and down arrow I get the following error
> message:
> an error occured during local processing. an error occured during
> report processing. the value expression for the query parameter 'date'
> contains an error: the expression referenced a non-existing parameter
> in the report parameters collection.
> anybody knows how to do this?
> thanks
>|||You're right I got this error msg. with cascading parameters. The
hierachie goes like this: A-->B-->C Originally I only included A and C
in my parameters but B was missing. So I added B but I didn't like it
to occure as the last report parameter so I wanted to change the
position and then I got the error msg. I get the same error when I
modifie the rdl file and swith the Report Parameters.
Any ideas instead of writing the whole report once again?
magendo_man schrieb:
> It sounds like you have either:
> A) deleted a parameter which was there before, or more likely
> B) changed the sequence required for cascading parameters, i.e. parameters
> where one value depends on another one previously entered. It is probably
> something to do with one of your report parameters' 'available values' or
> 'default values' definitions.
> HTH,
> Magendo_man
> "florian" wrote:
> > hi,
> >
> > after changing the order of my report parameters (in this example test)
> > in the menue via the up and down arrow I get the following error
> > message:
> >
> > an error occured during local processing. an error occured during
> > report processing. the value expression for the query parameter 'date'
> > contains an error: the expression referenced a non-existing parameter
> > in the report parameters collection.
> >
> > anybody knows how to do this?
> >
> > thanks
> >
> >|||Just add parameter B back in to Report Parameters in 2nd position.
"florian" wrote:
> You're right I got this error msg. with cascading parameters. The
> hierachie goes like this: A-->B-->C Originally I only included A and C
> in my parameters but B was missing. So I added B but I didn't like it
> to occure as the last report parameter so I wanted to change the
> position and then I got the error msg. I get the same error when I
> modifie the rdl file and swith the Report Parameters.
> Any ideas instead of writing the whole report once again?
>
> magendo_man schrieb:
> > It sounds like you have either:
> > A) deleted a parameter which was there before, or more likely
> > B) changed the sequence required for cascading parameters, i.e. parameters
> > where one value depends on another one previously entered. It is probably
> > something to do with one of your report parameters' 'available values' or
> > 'default values' definitions.
> >
> > HTH,
> > Magendo_man
> >
> > "florian" wrote:
> >
> > > hi,
> > >
> > > after changing the order of my report parameters (in this example test)
> > > in the menue via the up and down arrow I get the following error
> > > message:
> > >
> > > an error occured during local processing. an error occured during
> > > report processing. the value expression for the query parameter 'date'
> > > contains an error: the expression referenced a non-existing parameter
> > > in the report parameters collection.
> > >
> > > anybody knows how to do this?
> > >
> > > thanks
> > >
> > >
>|||do mean at the data view or where?
magendo_man schrieb:
> Just add parameter B back in to Report Parameters in 2nd position.
> "florian" wrote:
> > You're right I got this error msg. with cascading parameters. The
> > hierachie goes like this: A-->B-->C Originally I only included A and C
> > in my parameters but B was missing. So I added B but I didn't like it
> > to occure as the last report parameter so I wanted to change the
> > position and then I got the error msg. I get the same error when I
> > modifie the rdl file and swith the Report Parameters.
> >
> > Any ideas instead of writing the whole report once again?
> >
> >
> > magendo_man schrieb:
> >
> > > It sounds like you have either:
> > > A) deleted a parameter which was there before, or more likely
> > > B) changed the sequence required for cascading parameters, i.e. parameters
> > > where one value depends on another one previously entered. It is probably
> > > something to do with one of your report parameters' 'available values' or
> > > 'default values' definitions.
> > >
> > > HTH,
> > > Magendo_man
> > >
> > > "florian" wrote:
> > >
> > > > hi,
> > > >
> > > > after changing the order of my report parameters (in this example test)
> > > > in the menue via the up and down arrow I get the following error
> > > > message:
> > > >
> > > > an error occured during local processing. an error occured during
> > > > report processing. the value expression for the query parameter 'date'
> > > > contains an error: the expression referenced a non-existing parameter
> > > > in the report parameters collection.
> > > >
> > > > anybody knows how to do this?
> > > >
> > > > thanks
> > > >
> > > >
> >
> >|||In Layout view select from the menu Report> Report Parameters..
You should then be able to add back in your deleted parameter and move it in
to the correct position.
~ Magendo_man
"florian" wrote:
> do mean at the data view or where?
>
> magendo_man schrieb:
> > Just add parameter B back in to Report Parameters in 2nd position.
> >
> > "florian" wrote:
> >
> > > You're right I got this error msg. with cascading parameters. The
> > > hierachie goes like this: A-->B-->C Originally I only included A and C
> > > in my parameters but B was missing. So I added B but I didn't like it
> > > to occure as the last report parameter so I wanted to change the
> > > position and then I got the error msg. I get the same error when I
> > > modifie the rdl file and swith the Report Parameters.
> > >
> > > Any ideas instead of writing the whole report once again?
> > >
> > >
> > > magendo_man schrieb:
> > >
> > > > It sounds like you have either:
> > > > A) deleted a parameter which was there before, or more likely
> > > > B) changed the sequence required for cascading parameters, i.e. parameters
> > > > where one value depends on another one previously entered. It is probably
> > > > something to do with one of your report parameters' 'available values' or
> > > > 'default values' definitions.
> > > >
> > > > HTH,
> > > > Magendo_man
> > > >
> > > > "florian" wrote:
> > > >
> > > > > hi,
> > > > >
> > > > > after changing the order of my report parameters (in this example test)
> > > > > in the menue via the up and down arrow I get the following error
> > > > > message:
> > > > >
> > > > > an error occured during local processing. an error occured during
> > > > > report processing. the value expression for the query parameter 'date'
> > > > > contains an error: the expression referenced a non-existing parameter
> > > > > in the report parameters collection.
> > > > >
> > > > > anybody knows how to do this?
> > > > >
> > > > > thanks
> > > > >
> > > > >
> > >
> > >
>sql
Showing posts with label example. Show all posts
Showing posts with label example. Show all posts
Friday, March 30, 2012
Report Parameter in SELECT
I have a report parameter (called Column) that I would like
incorporated in the SELECT Statement. For example, the select is :
SELECT @.Column AS Expr1 FROM Table
The report runs after I select the appropriate value for the parameter,
but I do not get the correct data. If I select Test for the column
parameter, then Test appears for the value in the report--instead of
the correct data.
Does anyone know if building a dynamic column select statement is
possible like this?You have to create an expression for the SQL.
= "Select " & Parameters!Paramname.Value & " as Expr1 from Table"
Be sure you have your field list already because RS will not be able to
detect the fields for you once you use an expression.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Aaron" <aaron.heller@.gmail.com> wrote in message
news:1139495719.116692.50590@.g47g2000cwa.googlegroups.com...
>I have a report parameter (called Column) that I would like
> incorporated in the SELECT Statement. For example, the select is :
> SELECT @.Column AS Expr1 FROM Table
> The report runs after I select the appropriate value for the parameter,
> but I do not get the correct data. If I select Test for the column
> parameter, then Test appears for the value in the report--instead of
> the correct data.
> Does anyone know if building a dynamic column select statement is
> possible like this?
>
incorporated in the SELECT Statement. For example, the select is :
SELECT @.Column AS Expr1 FROM Table
The report runs after I select the appropriate value for the parameter,
but I do not get the correct data. If I select Test for the column
parameter, then Test appears for the value in the report--instead of
the correct data.
Does anyone know if building a dynamic column select statement is
possible like this?You have to create an expression for the SQL.
= "Select " & Parameters!Paramname.Value & " as Expr1 from Table"
Be sure you have your field list already because RS will not be able to
detect the fields for you once you use an expression.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Aaron" <aaron.heller@.gmail.com> wrote in message
news:1139495719.116692.50590@.g47g2000cwa.googlegroups.com...
>I have a report parameter (called Column) that I would like
> incorporated in the SELECT Statement. For example, the select is :
> SELECT @.Column AS Expr1 FROM Table
> The report runs after I select the appropriate value for the parameter,
> but I do not get the correct data. If I select Test for the column
> parameter, then Test appears for the value in the report--instead of
> the correct data.
> Does anyone know if building a dynamic column select statement is
> possible like this?
>
Monday, March 26, 2012
Report of Reports
Are there any example of SSRS reports using an rdl file as the source for the report. I.e. a Report of Reports?
Hi Freddie,
could you please elaborate a bit more?
thanks, 99
|||One way of doing this in RS 2005 is to render a report with the xml data rendering extension as xml document. This is then used as input for the xml data extension. However, getting the query setup correctly and working is a bit tricky. A specific sample and explanation for this approach will be available in an upcoming MSDN article about the RS 2005 Xml data extension later this summer.
-- Robert
|||Thanks Robert,
I did find an article "Integrate XML into Your Reporting Environment" by Bill Wolff at http://www.ftponline.com/special/sqlserver/bwolff/
I will be looking for the upcoming MSDN Article.
To elaborate more on my question...I would like to document my reporting service reports using reporting services. For example which property has custom code (e.g. IIF).
Report of Reports
Are there any example of SSRS reports using an rdl file as the source for the report. I.e. a Report of Reports?
Hi Freddie,
could you please elaborate a bit more?
thanks, 99
|||One way of doing this in RS 2005 is to render a report with the xml data rendering extension as xml document. This is then used as input for the xml data extension. However, getting the query setup correctly and working is a bit tricky. A specific sample and explanation for this approach will be available in an upcoming MSDN article about the RS 2005 Xml data extension later this summer.
-- Robert
|||Thanks Robert,
I did find an article "Integrate XML into Your Reporting Environment" by Bill Wolff at http://www.ftponline.com/special/sqlserver/bwolff/
I will be looking for the upcoming MSDN Article.
To elaborate more on my question...I would like to document my reporting service reports using reporting services. For example which property has custom code (e.g. IIF).
Report not Aggregates
Is there anyway to do a simple line chart that compares 5 fields? For
example, X axis shows fieldA, fieldB, fieldC, etc where Y axis is the value.
I'm having such a hard time with this, the report keeps wanting to take the
Sum or Count (aggregate) of fields. The values don't need summed, they're
already contained in the fields. Please help.
Thanks,
RyanHello Ryan,
I would like to know how you use the SQL Statement to get the dataset.
Also, please give me some sample data.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||2 Tables
table_items
item_id (PK)
item_name
table_values
value_id (PK)
year
actual_amount
item_id (FK)
SQL statement used for the dataset (for years 2002-2004 for example)
(the embedded selects are because some items will not have a row for years,
this puts a 0 value in for those years)
SELECT A.item_id, A.item_name, ISNULL
((SELECT actual_amount
FROM dbo.amounts
WHERE (item_id = A.id) AND (year = 2002)),
0) AS [2002 Actual], ISNULL
((SELECT actual_amount
FROM dbo.amounts AS amounts_5
WHERE (item_id = A.id) AND (year = 2003)),
0) AS [2003 Actual], ISNULL
.....
ETC.
The SQL resultset looks like this:
item_id
item_name
2002 Actual
2003 Actual
2004 Actual
Each item (detail row) is displayed on it's own page. I want each item to
have it's own graph. Just a simple line graph in this example would display
on the X-axis 2002 Actual, 2003 Actual, and 2004 Actual.
Probably too much info for a simple problem but there it is!
Thanks!
Ryan
"Wei Lu [MSFT]" <weilu@.online.microsoft.com> wrote in message
news:HQcIY19CIHA.360@.TK2MSFTNGHUB02.phx.gbl...
> Hello Ryan,
> I would like to know how you use the SQL Statement to get the dataset.
> Also, please give me some sample data.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hello Ryan,
I suggest you just use another dataset for the chart.
Since the chart is based on the dataset's column and you could not put
multiple columns into the X Axis, you need to use another dataset like this:
item_id, item_name, Actual value, Year.
So that when you put the Year into the X axis, you could get the result you
want.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hmmm, this looks good. The problem though is that the last year in the
chart is a different field. For example:
[2006 Actual], [2007 Actual], [2008 Budget].
The last year draws from a Budget field and not the Actual field.
Looks like this may not be doable. We did have the chart in Microsoft
Access. I may have them use that or see if there's any way to accomplish
this in Crystal Reports (I need something I can build into my VS project).
Thanks,
Ryan
"Wei Lu [MSFT]" <weilu@.online.microsoft.com> wrote in message
news:7$yFzgvDIHA.5256@.TK2MSFTNGHUB02.phx.gbl...
> Hello Ryan,
> I suggest you just use another dataset for the chart.
> Since the chart is based on the dataset's column and you could not put
> multiple columns into the X Axis, you need to use another dataset like
> this:
> item_id, item_name, Actual value, Year.
> So that when you put the Year into the X axis, you could get the result
> you
> want.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hello Ryan,
If you are using VS 2005, you could use the ReportViewer Control to
complish this report in the WinForm or Web Form.
Reporting Services and ReportViewer Controls in Visual Studio
http://msdn2.microsoft.com/en-us/library/ms345248.aspx
Hope this helps.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.
example, X axis shows fieldA, fieldB, fieldC, etc where Y axis is the value.
I'm having such a hard time with this, the report keeps wanting to take the
Sum or Count (aggregate) of fields. The values don't need summed, they're
already contained in the fields. Please help.
Thanks,
RyanHello Ryan,
I would like to know how you use the SQL Statement to get the dataset.
Also, please give me some sample data.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||2 Tables
table_items
item_id (PK)
item_name
table_values
value_id (PK)
year
actual_amount
item_id (FK)
SQL statement used for the dataset (for years 2002-2004 for example)
(the embedded selects are because some items will not have a row for years,
this puts a 0 value in for those years)
SELECT A.item_id, A.item_name, ISNULL
((SELECT actual_amount
FROM dbo.amounts
WHERE (item_id = A.id) AND (year = 2002)),
0) AS [2002 Actual], ISNULL
((SELECT actual_amount
FROM dbo.amounts AS amounts_5
WHERE (item_id = A.id) AND (year = 2003)),
0) AS [2003 Actual], ISNULL
.....
ETC.
The SQL resultset looks like this:
item_id
item_name
2002 Actual
2003 Actual
2004 Actual
Each item (detail row) is displayed on it's own page. I want each item to
have it's own graph. Just a simple line graph in this example would display
on the X-axis 2002 Actual, 2003 Actual, and 2004 Actual.
Probably too much info for a simple problem but there it is!
Thanks!
Ryan
"Wei Lu [MSFT]" <weilu@.online.microsoft.com> wrote in message
news:HQcIY19CIHA.360@.TK2MSFTNGHUB02.phx.gbl...
> Hello Ryan,
> I would like to know how you use the SQL Statement to get the dataset.
> Also, please give me some sample data.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hello Ryan,
I suggest you just use another dataset for the chart.
Since the chart is based on the dataset's column and you could not put
multiple columns into the X Axis, you need to use another dataset like this:
item_id, item_name, Actual value, Year.
So that when you put the Year into the X axis, you could get the result you
want.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hmmm, this looks good. The problem though is that the last year in the
chart is a different field. For example:
[2006 Actual], [2007 Actual], [2008 Budget].
The last year draws from a Budget field and not the Actual field.
Looks like this may not be doable. We did have the chart in Microsoft
Access. I may have them use that or see if there's any way to accomplish
this in Crystal Reports (I need something I can build into my VS project).
Thanks,
Ryan
"Wei Lu [MSFT]" <weilu@.online.microsoft.com> wrote in message
news:7$yFzgvDIHA.5256@.TK2MSFTNGHUB02.phx.gbl...
> Hello Ryan,
> I suggest you just use another dataset for the chart.
> Since the chart is based on the dataset's column and you could not put
> multiple columns into the X Axis, you need to use another dataset like
> this:
> item_id, item_name, Actual value, Year.
> So that when you put the Year into the X axis, you could get the result
> you
> want.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hello Ryan,
If you are using VS 2005, you could use the ReportViewer Control to
complish this report in the WinForm or Web Form.
Reporting Services and ReportViewer Controls in Visual Studio
http://msdn2.microsoft.com/en-us/library/ms345248.aspx
Hope this helps.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.
Tuesday, March 20, 2012
Report model
Hi,
In my database I have a table with user rights. For example:
User 1 may see region 1
User 2 may see region 2 and 3
Is it possible to use this in my report model. When user 1 makes a report with the report builder he must not be able to see region 2 and 3.
thanks in advance
You can use the SecurityFilters property on the corresponding model entity to grant permission to specific rows. In addition to the online documentation, look for a post on my blog in the near future for more details on the many options for securing the data exposed by a report model.Monday, March 12, 2012
report manager parameter BUG
here is an example of this bug at work.. (i am using RS SP1)
1) upload this report into report manager
2) - RUN THE Report, and notice that the 2nd parameter called
'defaultparam' gets set to the date, and it works.. (all the report
does is show this parameter)
3) - go to the parameter editing section of hte report in report
manager
4) - change something UNRELELATED to defaultparam - for instance the
PROMPT of the firstparameter - dummyparam, and then APPLY
5) - go back to the report - and "defaultparam" nolonger calculates the
date (the default parameter expression in the report)
conclusion, report manager not only updates the parameters you change,
(as it should to give the administrator ability to), it erroneously
updates all the parameters..
also i notice that query based default (foir single value, rather than
name,value) don't show up in report manager as "query based" (and thus also
sucumb to this bug")
<?xml version="1.0" encoding="utf-8"?>
<Report
xmlns="http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefini..."xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
<RightMargin>1in</RightMargin>
<Body>
<ReportItems>
<Textbox Name="textbox1">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
</Style>
<Top>0.125in</Top>
<rd:DefaultName>textbox1</rd:DefaultName>
<Height>0.25in</Height>
<Width>1in</Width>
<CanGrow>true</CanGrow>
<Value>=Parameters!defaultparam.Value</Value>
<Left>0.25in</Left>
</Textbox>
</ReportItems>
<Style />
<Height>2in</Height>
</Body>
<TopMargin>1in</TopMargin>
<Width>6.5in</Width>
<LeftMargin>1in</LeftMargin>
<rd:SnapToGrid>true</rd:SnapToGrid>
<rd:DrawGrid>true</rd:DrawGrid>
<rd:ReportID>ed8d8d8c-443f-4598-82a1-db50fd8cbc9a</rd:ReportÂID>
<BottomMargin>1in</BottomMargin>
<ReportParameters>
<ReportParameter Name="dummyparam">
<DataType>String</DataType>
<AllowBlank>true</AllowBlank>
<Prompt>dummyparameter</Prompt>
</ReportParameter>
<ReportParameter Name="defaultparam">
<DataType>String</DataType>
<DefaultValue>
<Values>
<Value>=Format(DateTime.Now,"d")</Value>
</Values>
</DefaultValue>
<AllowBlank>true</AllowBlank>
<Prompt>defaultparam</Prompt>
</ReportParameter>
<ReportParameter Name="nextparam">
<DataType>String</DataType>
<AllowBlank>true</AllowBlank>
<Prompt>Report_Parameter_2</Prompt>
</ReportParameter>
</ReportParameters>
<Language>en-US</Language>
</Report>please excuse the double posts, i thought i was putting it on a private
newsgroup at msdn subscribers|||This is a known limitation of the report manager report parameter page.
This issue should be fixed in Yukon.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Karl Prosser" <laborready.com@.kprosser(backwards)> wrote in message
news:2D74DC06-9039-4576-86DB-01055F1A98A6@.microsoft.com...
> please excuse the double posts, i thought i was putting it on a private
> newsgroup at msdn subscribers|||is there a way to make a 'hidden writeable (not read only) parameter' other
than changing in in report manager (which messes up the other default ones?)
because in report designer you can't make it this way, you can omit the
prompt , but then its hidden but gives you READONLY parameter errors if
trying to set it in the URL..
maybe there is a script that uses the webservice or something?
"Daniel Reib [MSFT]" wrote:
> This is a known limitation of the report manager report parameter page.
> This issue should be fixed in Yukon.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Karl Prosser" <laborready.com@.kprosser(backwards)> wrote in message
> news:2D74DC06-9039-4576-86DB-01055F1A98A6@.microsoft.com...
> > please excuse the double posts, i thought i was putting it on a private
> > newsgroup at msdn subscribers
>
>|||There is actually a way to achieve a hidden parameter in SP1 and in the
upcoming SP2 through report designer: specify just at least one blank as
report parameter prompt and publish to the report server.
Note: the parameter will still be prompted in designer preview, but it will
not be prompted in the viewer of report manager.
The next version (RS2005) will have a better solution for managing hidden
parameters (also through the SOAP API and report manager).
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Karl Prosser" <laborready.com@.kprosser(backwards)> wrote in message
news:1BCA549E-DD3D-4754-A1D1-6077EA3D3243@.microsoft.com...
> is there a way to make a 'hidden writeable (not read only) parameter'
> other
> than changing in in report manager (which messes up the other default
> ones?)
> because in report designer you can't make it this way, you can omit the
> prompt , but then its hidden but gives you READONLY parameter errors if
> trying to set it in the URL..
> maybe there is a script that uses the webservice or something?
>
> "Daniel Reib [MSFT]" wrote:
>> This is a known limitation of the report manager report parameter page.
>> This issue should be fixed in Yukon.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Karl Prosser" <laborready.com@.kprosser(backwards)> wrote in message
>> news:2D74DC06-9039-4576-86DB-01055F1A98A6@.microsoft.com...
>> > please excuse the double posts, i thought i was putting it on a private
>> > newsgroup at msdn subscribers
>>|||nice.. just a space instead of a blank.. well at least i can control it
completely from the RDL, its a big releif, i think i need to start a site
with Questions and Answers for these bizarre things in RS
"Robert Bruckner [MSFT]" wrote:
> There is actually a way to achieve a hidden parameter in SP1 and in the
> upcoming SP2 through report designer: specify just at least one blank as
> report parameter prompt and publish to the report server.
> Note: the parameter will still be prompted in designer preview, but it will
> not be prompted in the viewer of report manager.
>|||Daniel,
Would there happen to be a published list of 'known limitations' for RS SP1,
or do we just have to figure these things out as we come upon them?
--
Adrian M.
MCP
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:ul5cMEUFFHA.2176@.TK2MSFTNGP15.phx.gbl...
> This is a known limitation of the report manager report parameter page.
> This issue should be fixed in Yukon.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Karl Prosser" <laborready.com@.kprosser(backwards)> wrote in message
> news:2D74DC06-9039-4576-86DB-01055F1A98A6@.microsoft.com...
>> please excuse the double posts, i thought i was putting it on a private
>> newsgroup at msdn subscribers
>|||Unfortunately, such a site does not exist. We are so busy fixing them (and
adding new ones <g>) that we haven't had time to create something like this.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Adrian M." <absolutelynospam@.nodomain_.com> wrote in message
news:eGTLpKcFFHA.1292@.TK2MSFTNGP10.phx.gbl...
> Daniel,
> Would there happen to be a published list of 'known limitations' for RS
> SP1, or do we just have to figure these things out as we come upon them?
> --
> Adrian M.
> MCP
> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> news:ul5cMEUFFHA.2176@.TK2MSFTNGP15.phx.gbl...
>> This is a known limitation of the report manager report parameter page.
>> This issue should be fixed in Yukon.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Karl Prosser" <laborready.com@.kprosser(backwards)> wrote in message
>> news:2D74DC06-9039-4576-86DB-01055F1A98A6@.microsoft.com...
>> please excuse the double posts, i thought i was putting it on a private
>> newsgroup at msdn subscribers
>>
>
1) upload this report into report manager
2) - RUN THE Report, and notice that the 2nd parameter called
'defaultparam' gets set to the date, and it works.. (all the report
does is show this parameter)
3) - go to the parameter editing section of hte report in report
manager
4) - change something UNRELELATED to defaultparam - for instance the
PROMPT of the firstparameter - dummyparam, and then APPLY
5) - go back to the report - and "defaultparam" nolonger calculates the
date (the default parameter expression in the report)
conclusion, report manager not only updates the parameters you change,
(as it should to give the administrator ability to), it erroneously
updates all the parameters..
also i notice that query based default (foir single value, rather than
name,value) don't show up in report manager as "query based" (and thus also
sucumb to this bug")
<?xml version="1.0" encoding="utf-8"?>
<Report
xmlns="http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefini..."xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
<RightMargin>1in</RightMargin>
<Body>
<ReportItems>
<Textbox Name="textbox1">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
</Style>
<Top>0.125in</Top>
<rd:DefaultName>textbox1</rd:DefaultName>
<Height>0.25in</Height>
<Width>1in</Width>
<CanGrow>true</CanGrow>
<Value>=Parameters!defaultparam.Value</Value>
<Left>0.25in</Left>
</Textbox>
</ReportItems>
<Style />
<Height>2in</Height>
</Body>
<TopMargin>1in</TopMargin>
<Width>6.5in</Width>
<LeftMargin>1in</LeftMargin>
<rd:SnapToGrid>true</rd:SnapToGrid>
<rd:DrawGrid>true</rd:DrawGrid>
<rd:ReportID>ed8d8d8c-443f-4598-82a1-db50fd8cbc9a</rd:ReportÂID>
<BottomMargin>1in</BottomMargin>
<ReportParameters>
<ReportParameter Name="dummyparam">
<DataType>String</DataType>
<AllowBlank>true</AllowBlank>
<Prompt>dummyparameter</Prompt>
</ReportParameter>
<ReportParameter Name="defaultparam">
<DataType>String</DataType>
<DefaultValue>
<Values>
<Value>=Format(DateTime.Now,"d")</Value>
</Values>
</DefaultValue>
<AllowBlank>true</AllowBlank>
<Prompt>defaultparam</Prompt>
</ReportParameter>
<ReportParameter Name="nextparam">
<DataType>String</DataType>
<AllowBlank>true</AllowBlank>
<Prompt>Report_Parameter_2</Prompt>
</ReportParameter>
</ReportParameters>
<Language>en-US</Language>
</Report>please excuse the double posts, i thought i was putting it on a private
newsgroup at msdn subscribers|||This is a known limitation of the report manager report parameter page.
This issue should be fixed in Yukon.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Karl Prosser" <laborready.com@.kprosser(backwards)> wrote in message
news:2D74DC06-9039-4576-86DB-01055F1A98A6@.microsoft.com...
> please excuse the double posts, i thought i was putting it on a private
> newsgroup at msdn subscribers|||is there a way to make a 'hidden writeable (not read only) parameter' other
than changing in in report manager (which messes up the other default ones?)
because in report designer you can't make it this way, you can omit the
prompt , but then its hidden but gives you READONLY parameter errors if
trying to set it in the URL..
maybe there is a script that uses the webservice or something?
"Daniel Reib [MSFT]" wrote:
> This is a known limitation of the report manager report parameter page.
> This issue should be fixed in Yukon.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Karl Prosser" <laborready.com@.kprosser(backwards)> wrote in message
> news:2D74DC06-9039-4576-86DB-01055F1A98A6@.microsoft.com...
> > please excuse the double posts, i thought i was putting it on a private
> > newsgroup at msdn subscribers
>
>|||There is actually a way to achieve a hidden parameter in SP1 and in the
upcoming SP2 through report designer: specify just at least one blank as
report parameter prompt and publish to the report server.
Note: the parameter will still be prompted in designer preview, but it will
not be prompted in the viewer of report manager.
The next version (RS2005) will have a better solution for managing hidden
parameters (also through the SOAP API and report manager).
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Karl Prosser" <laborready.com@.kprosser(backwards)> wrote in message
news:1BCA549E-DD3D-4754-A1D1-6077EA3D3243@.microsoft.com...
> is there a way to make a 'hidden writeable (not read only) parameter'
> other
> than changing in in report manager (which messes up the other default
> ones?)
> because in report designer you can't make it this way, you can omit the
> prompt , but then its hidden but gives you READONLY parameter errors if
> trying to set it in the URL..
> maybe there is a script that uses the webservice or something?
>
> "Daniel Reib [MSFT]" wrote:
>> This is a known limitation of the report manager report parameter page.
>> This issue should be fixed in Yukon.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Karl Prosser" <laborready.com@.kprosser(backwards)> wrote in message
>> news:2D74DC06-9039-4576-86DB-01055F1A98A6@.microsoft.com...
>> > please excuse the double posts, i thought i was putting it on a private
>> > newsgroup at msdn subscribers
>>|||nice.. just a space instead of a blank.. well at least i can control it
completely from the RDL, its a big releif, i think i need to start a site
with Questions and Answers for these bizarre things in RS
"Robert Bruckner [MSFT]" wrote:
> There is actually a way to achieve a hidden parameter in SP1 and in the
> upcoming SP2 through report designer: specify just at least one blank as
> report parameter prompt and publish to the report server.
> Note: the parameter will still be prompted in designer preview, but it will
> not be prompted in the viewer of report manager.
>|||Daniel,
Would there happen to be a published list of 'known limitations' for RS SP1,
or do we just have to figure these things out as we come upon them?
--
Adrian M.
MCP
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:ul5cMEUFFHA.2176@.TK2MSFTNGP15.phx.gbl...
> This is a known limitation of the report manager report parameter page.
> This issue should be fixed in Yukon.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Karl Prosser" <laborready.com@.kprosser(backwards)> wrote in message
> news:2D74DC06-9039-4576-86DB-01055F1A98A6@.microsoft.com...
>> please excuse the double posts, i thought i was putting it on a private
>> newsgroup at msdn subscribers
>|||Unfortunately, such a site does not exist. We are so busy fixing them (and
adding new ones <g>) that we haven't had time to create something like this.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Adrian M." <absolutelynospam@.nodomain_.com> wrote in message
news:eGTLpKcFFHA.1292@.TK2MSFTNGP10.phx.gbl...
> Daniel,
> Would there happen to be a published list of 'known limitations' for RS
> SP1, or do we just have to figure these things out as we come upon them?
> --
> Adrian M.
> MCP
> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> news:ul5cMEUFFHA.2176@.TK2MSFTNGP15.phx.gbl...
>> This is a known limitation of the report manager report parameter page.
>> This issue should be fixed in Yukon.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Karl Prosser" <laborready.com@.kprosser(backwards)> wrote in message
>> news:2D74DC06-9039-4576-86DB-01055F1A98A6@.microsoft.com...
>> please excuse the double posts, i thought i was putting it on a private
>> newsgroup at msdn subscribers
>>
>
Friday, March 9, 2012
Report Manager default open to sub folder
Hello, when I log onto Report Manager web server using Windows Authentication, I need this user to be directed to a default sub folder.
For example: if I have folder A and sub folder 1 and 2. I need to be able to log in and be directed to sub folder 1. I was able to set up view role and access folder A. But then I need to click on folder 1 to view / create my reports.
You can specify the folder path on the URL, so if you want someone to start in Folder1, have them use this URL:
http://localhost/Reports/Pages/Folder.aspx?ItemPath=%2fFolder1
Regards.
report manager - parameter bug
here is an example of this bug at work.. (i am using RS SP1)
1) upload this report into report manager
2) - RUN THE Report, and notice that the 2nd parameter called
'defaultparam' gets set to the date, and it works.. (all the report
does is show this parameter)
3) - go to the parameter editing section of hte report in report
manager
4) - change something UNRELELATED to defaultparam - for instance the
PROMPT of the firstparameter - dummyparam, and then APPLY
5) - go back to the report - and "defaultparam" nolonger calculates the
date (the default parameter expression in the report)
conclusion, report manager not only updates the parameters you change,
(as it should to give the administrator ability to), it erroneously
updates all the parameters..
<?xml version="1.0" encoding="utf-8"?>
<Report
xmlns="http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefinition"
xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
<RightMargin>1in</RightMargin>
<Body>
<ReportItems>
<Textbox Name="textbox1">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
</Style>
<Top>0.125in</Top>
<rd:DefaultName>textbox1</rd:DefaultName>
<Height>0.25in</Height>
<Width>1in</Width>
<CanGrow>true</CanGrow>
<Value>=Parameters!defaultparam.Value</Value>
<Left>0.25in</Left>
</Textbox>
</ReportItems>
<Style />
<Height>2in</Height>
</Body>
<TopMargin>1in</TopMargin>
<Width>6.5in</Width>
<LeftMargin>1in</LeftMargin>
<rd:SnapToGrid>true</rd:SnapToGrid>
<rd:DrawGrid>true</rd:DrawGrid>
<rd:ReportID>ed8d8d8c-443f-4598-82a1-db50fd8cbc9a</rd:ReportID>
<BottomMargin>1in</BottomMargin>
<ReportParameters>
<ReportParameter Name="dummyparam">
<DataType>String</DataType>
<AllowBlank>true</AllowBlank>
<Prompt>dummyparameter</Prompt>
</ReportParameter>
<ReportParameter Name="defaultparam">
<DataType>String</DataType>
<DefaultValue>
<Values>
<Value>=Format(DateTime.Now,"d")</Value>
</Values>
</DefaultValue>
<AllowBlank>true</AllowBlank>
<Prompt>defaultparam</Prompt>
</ReportParameter>
<ReportParameter Name="nextparam">
<DataType>String</DataType>
<AllowBlank>true</AllowBlank>
<Prompt>Report_Parameter_2</Prompt>
</ReportParameter>
</ReportParameters>
<Language>en-US</Language>
</Report>I will post this on the private newsgroup as a bug...
thanks
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<klumsy@.xtra.co.nz> wrote in message
news:1108605533.668474.147440@.c13g2000cwb.googlegroups.com...
> here is an example of this bug at work.. (i am using RS SP1)
> 1) upload this report into report manager
> 2) - RUN THE Report, and notice that the 2nd parameter called
> 'defaultparam' gets set to the date, and it works.. (all the report
> does is show this parameter)
> 3) - go to the parameter editing section of hte report in report
> manager
> 4) - change something UNRELELATED to defaultparam - for instance the
> PROMPT of the firstparameter - dummyparam, and then APPLY
> 5) - go back to the report - and "defaultparam" nolonger calculates the
> date (the default parameter expression in the report)
> conclusion, report manager not only updates the parameters you change,
> (as it should to give the administrator ability to), it erroneously
> updates all the parameters..
>
> <?xml version="1.0" encoding="utf-8"?>
> <Report
> xmlns="http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefinition"
> xmlns:rd="">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
> <RightMargin>1in</RightMargin>
> <Body>
> <ReportItems>
> <Textbox Name="textbox1">
> <Style>
> <PaddingLeft>2pt</PaddingLeft>
> <PaddingBottom>2pt</PaddingBottom>
> <PaddingTop>2pt</PaddingTop>
> <PaddingRight>2pt</PaddingRight>
> </Style>
> <Top>0.125in</Top>
> <rd:DefaultName>textbox1</rd:DefaultName>
> <Height>0.25in</Height>
> <Width>1in</Width>
> <CanGrow>true</CanGrow>
> <Value>=Parameters!defaultparam.Value</Value>
> <Left>0.25in</Left>
> </Textbox>
> </ReportItems>
> <Style />
> <Height>2in</Height>
> </Body>
> <TopMargin>1in</TopMargin>
> <Width>6.5in</Width>
> <LeftMargin>1in</LeftMargin>
> <rd:SnapToGrid>true</rd:SnapToGrid>
> <rd:DrawGrid>true</rd:DrawGrid>
> <rd:ReportID>ed8d8d8c-443f-4598-82a1-db50fd8cbc9a</rd:ReportID>
> <BottomMargin>1in</BottomMargin>
> <ReportParameters>
> <ReportParameter Name="dummyparam">
> <DataType>String</DataType>
> <AllowBlank>true</AllowBlank>
> <Prompt>dummyparameter</Prompt>
> </ReportParameter>
> <ReportParameter Name="defaultparam">
> <DataType>String</DataType>
> <DefaultValue>
> <Values>
> <Value>=Format(DateTime.Now,"d")</Value>
> </Values>
> </DefaultValue>
> <AllowBlank>true</AllowBlank>
> <Prompt>defaultparam</Prompt>
> </ReportParameter>
> <ReportParameter Name="nextparam">
> <DataType>String</DataType>
> <AllowBlank>true</AllowBlank>
> <Prompt>Report_Parameter_2</Prompt>
> </ReportParameter>
> </ReportParameters>
> <Language>en-US</Language>
> </Report>
>|||By the way, the bad behaviour was duplicated on my machine...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<klumsy@.xtra.co.nz> wrote in message
news:1108605533.668474.147440@.c13g2000cwb.googlegroups.com...
> here is an example of this bug at work.. (i am using RS SP1)
> 1) upload this report into report manager
> 2) - RUN THE Report, and notice that the 2nd parameter called
> 'defaultparam' gets set to the date, and it works.. (all the report
> does is show this parameter)
> 3) - go to the parameter editing section of hte report in report
> manager
> 4) - change something UNRELELATED to defaultparam - for instance the
> PROMPT of the firstparameter - dummyparam, and then APPLY
> 5) - go back to the report - and "defaultparam" nolonger calculates the
> date (the default parameter expression in the report)
> conclusion, report manager not only updates the parameters you change,
> (as it should to give the administrator ability to), it erroneously
> updates all the parameters..
>
> <?xml version="1.0" encoding="utf-8"?>
> <Report
> xmlns="http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefinition"
> xmlns:rd="">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
> <RightMargin>1in</RightMargin>
> <Body>
> <ReportItems>
> <Textbox Name="textbox1">
> <Style>
> <PaddingLeft>2pt</PaddingLeft>
> <PaddingBottom>2pt</PaddingBottom>
> <PaddingTop>2pt</PaddingTop>
> <PaddingRight>2pt</PaddingRight>
> </Style>
> <Top>0.125in</Top>
> <rd:DefaultName>textbox1</rd:DefaultName>
> <Height>0.25in</Height>
> <Width>1in</Width>
> <CanGrow>true</CanGrow>
> <Value>=Parameters!defaultparam.Value</Value>
> <Left>0.25in</Left>
> </Textbox>
> </ReportItems>
> <Style />
> <Height>2in</Height>
> </Body>
> <TopMargin>1in</TopMargin>
> <Width>6.5in</Width>
> <LeftMargin>1in</LeftMargin>
> <rd:SnapToGrid>true</rd:SnapToGrid>
> <rd:DrawGrid>true</rd:DrawGrid>
> <rd:ReportID>ed8d8d8c-443f-4598-82a1-db50fd8cbc9a</rd:ReportID>
> <BottomMargin>1in</BottomMargin>
> <ReportParameters>
> <ReportParameter Name="dummyparam">
> <DataType>String</DataType>
> <AllowBlank>true</AllowBlank>
> <Prompt>dummyparameter</Prompt>
> </ReportParameter>
> <ReportParameter Name="defaultparam">
> <DataType>String</DataType>
> <DefaultValue>
> <Values>
> <Value>=Format(DateTime.Now,"d")</Value>
> </Values>
> </DefaultValue>
> <AllowBlank>true</AllowBlank>
> <Prompt>defaultparam</Prompt>
> </ReportParameter>
> <ReportParameter Name="nextparam">
> <DataType>String</DataType>
> <AllowBlank>true</AllowBlank>
> <Prompt>Report_Parameter_2</Prompt>
> </ReportParameter>
> </ReportParameters>
> <Language>en-US</Language>
> </Report>
>|||You may be interested in this related thread:
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=5d83b939-71ab-47fa-9f85-9d15d90dacb9
Also check my recent posting in that same thread for a possible workaround
on RS 2000 (specifying hidden parameters through report designer).
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:OEIuxKPFFHA.3284@.TK2MSFTNGP09.phx.gbl...
> By the way, the bad behaviour was duplicated on my machine...
>
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> <klumsy@.xtra.co.nz> wrote in message
> news:1108605533.668474.147440@.c13g2000cwb.googlegroups.com...
>> here is an example of this bug at work.. (i am using RS SP1)
>> 1) upload this report into report manager
>> 2) - RUN THE Report, and notice that the 2nd parameter called
>> 'defaultparam' gets set to the date, and it works.. (all the report
>> does is show this parameter)
>> 3) - go to the parameter editing section of hte report in report
>> manager
>> 4) - change something UNRELELATED to defaultparam - for instance the
>> PROMPT of the firstparameter - dummyparam, and then APPLY
>> 5) - go back to the report - and "defaultparam" nolonger calculates the
>> date (the default parameter expression in the report)
>> conclusion, report manager not only updates the parameters you change,
>> (as it should to give the administrator ability to), it erroneously
>> updates all the parameters..
>>
>> <?xml version="1.0" encoding="utf-8"?>
>> <Report
>> xmlns="http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefinition"
>> xmlns:rd="">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
>> <RightMargin>1in</RightMargin>
>> <Body>
>> <ReportItems>
>> <Textbox Name="textbox1">
>> <Style>
>> <PaddingLeft>2pt</PaddingLeft>
>> <PaddingBottom>2pt</PaddingBottom>
>> <PaddingTop>2pt</PaddingTop>
>> <PaddingRight>2pt</PaddingRight>
>> </Style>
>> <Top>0.125in</Top>
>> <rd:DefaultName>textbox1</rd:DefaultName>
>> <Height>0.25in</Height>
>> <Width>1in</Width>
>> <CanGrow>true</CanGrow>
>> <Value>=Parameters!defaultparam.Value</Value>
>> <Left>0.25in</Left>
>> </Textbox>
>> </ReportItems>
>> <Style />
>> <Height>2in</Height>
>> </Body>
>> <TopMargin>1in</TopMargin>
>> <Width>6.5in</Width>
>> <LeftMargin>1in</LeftMargin>
>> <rd:SnapToGrid>true</rd:SnapToGrid>
>> <rd:DrawGrid>true</rd:DrawGrid>
>> <rd:ReportID>ed8d8d8c-443f-4598-82a1-db50fd8cbc9a</rd:ReportID>
>> <BottomMargin>1in</BottomMargin>
>> <ReportParameters>
>> <ReportParameter Name="dummyparam">
>> <DataType>String</DataType>
>> <AllowBlank>true</AllowBlank>
>> <Prompt>dummyparameter</Prompt>
>> </ReportParameter>
>> <ReportParameter Name="defaultparam">
>> <DataType>String</DataType>
>> <DefaultValue>
>> <Values>
>> <Value>=Format(DateTime.Now,"d")</Value>
>> </Values>
>> </DefaultValue>
>> <AllowBlank>true</AllowBlank>
>> <Prompt>defaultparam</Prompt>
>> </ReportParameter>
>> <ReportParameter Name="nextparam">
>> <DataType>String</DataType>
>> <AllowBlank>true</AllowBlank>
>> <Prompt>Report_Parameter_2</Prompt>
>> </ReportParameter>
>> </ReportParameters>
>> <Language>en-US</Language>
>> </Report>
>
1) upload this report into report manager
2) - RUN THE Report, and notice that the 2nd parameter called
'defaultparam' gets set to the date, and it works.. (all the report
does is show this parameter)
3) - go to the parameter editing section of hte report in report
manager
4) - change something UNRELELATED to defaultparam - for instance the
PROMPT of the firstparameter - dummyparam, and then APPLY
5) - go back to the report - and "defaultparam" nolonger calculates the
date (the default parameter expression in the report)
conclusion, report manager not only updates the parameters you change,
(as it should to give the administrator ability to), it erroneously
updates all the parameters..
<?xml version="1.0" encoding="utf-8"?>
<Report
xmlns="http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefinition"
xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
<RightMargin>1in</RightMargin>
<Body>
<ReportItems>
<Textbox Name="textbox1">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
</Style>
<Top>0.125in</Top>
<rd:DefaultName>textbox1</rd:DefaultName>
<Height>0.25in</Height>
<Width>1in</Width>
<CanGrow>true</CanGrow>
<Value>=Parameters!defaultparam.Value</Value>
<Left>0.25in</Left>
</Textbox>
</ReportItems>
<Style />
<Height>2in</Height>
</Body>
<TopMargin>1in</TopMargin>
<Width>6.5in</Width>
<LeftMargin>1in</LeftMargin>
<rd:SnapToGrid>true</rd:SnapToGrid>
<rd:DrawGrid>true</rd:DrawGrid>
<rd:ReportID>ed8d8d8c-443f-4598-82a1-db50fd8cbc9a</rd:ReportID>
<BottomMargin>1in</BottomMargin>
<ReportParameters>
<ReportParameter Name="dummyparam">
<DataType>String</DataType>
<AllowBlank>true</AllowBlank>
<Prompt>dummyparameter</Prompt>
</ReportParameter>
<ReportParameter Name="defaultparam">
<DataType>String</DataType>
<DefaultValue>
<Values>
<Value>=Format(DateTime.Now,"d")</Value>
</Values>
</DefaultValue>
<AllowBlank>true</AllowBlank>
<Prompt>defaultparam</Prompt>
</ReportParameter>
<ReportParameter Name="nextparam">
<DataType>String</DataType>
<AllowBlank>true</AllowBlank>
<Prompt>Report_Parameter_2</Prompt>
</ReportParameter>
</ReportParameters>
<Language>en-US</Language>
</Report>I will post this on the private newsgroup as a bug...
thanks
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<klumsy@.xtra.co.nz> wrote in message
news:1108605533.668474.147440@.c13g2000cwb.googlegroups.com...
> here is an example of this bug at work.. (i am using RS SP1)
> 1) upload this report into report manager
> 2) - RUN THE Report, and notice that the 2nd parameter called
> 'defaultparam' gets set to the date, and it works.. (all the report
> does is show this parameter)
> 3) - go to the parameter editing section of hte report in report
> manager
> 4) - change something UNRELELATED to defaultparam - for instance the
> PROMPT of the firstparameter - dummyparam, and then APPLY
> 5) - go back to the report - and "defaultparam" nolonger calculates the
> date (the default parameter expression in the report)
> conclusion, report manager not only updates the parameters you change,
> (as it should to give the administrator ability to), it erroneously
> updates all the parameters..
>
> <?xml version="1.0" encoding="utf-8"?>
> <Report
> xmlns="http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefinition"
> xmlns:rd="">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
> <RightMargin>1in</RightMargin>
> <Body>
> <ReportItems>
> <Textbox Name="textbox1">
> <Style>
> <PaddingLeft>2pt</PaddingLeft>
> <PaddingBottom>2pt</PaddingBottom>
> <PaddingTop>2pt</PaddingTop>
> <PaddingRight>2pt</PaddingRight>
> </Style>
> <Top>0.125in</Top>
> <rd:DefaultName>textbox1</rd:DefaultName>
> <Height>0.25in</Height>
> <Width>1in</Width>
> <CanGrow>true</CanGrow>
> <Value>=Parameters!defaultparam.Value</Value>
> <Left>0.25in</Left>
> </Textbox>
> </ReportItems>
> <Style />
> <Height>2in</Height>
> </Body>
> <TopMargin>1in</TopMargin>
> <Width>6.5in</Width>
> <LeftMargin>1in</LeftMargin>
> <rd:SnapToGrid>true</rd:SnapToGrid>
> <rd:DrawGrid>true</rd:DrawGrid>
> <rd:ReportID>ed8d8d8c-443f-4598-82a1-db50fd8cbc9a</rd:ReportID>
> <BottomMargin>1in</BottomMargin>
> <ReportParameters>
> <ReportParameter Name="dummyparam">
> <DataType>String</DataType>
> <AllowBlank>true</AllowBlank>
> <Prompt>dummyparameter</Prompt>
> </ReportParameter>
> <ReportParameter Name="defaultparam">
> <DataType>String</DataType>
> <DefaultValue>
> <Values>
> <Value>=Format(DateTime.Now,"d")</Value>
> </Values>
> </DefaultValue>
> <AllowBlank>true</AllowBlank>
> <Prompt>defaultparam</Prompt>
> </ReportParameter>
> <ReportParameter Name="nextparam">
> <DataType>String</DataType>
> <AllowBlank>true</AllowBlank>
> <Prompt>Report_Parameter_2</Prompt>
> </ReportParameter>
> </ReportParameters>
> <Language>en-US</Language>
> </Report>
>|||By the way, the bad behaviour was duplicated on my machine...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<klumsy@.xtra.co.nz> wrote in message
news:1108605533.668474.147440@.c13g2000cwb.googlegroups.com...
> here is an example of this bug at work.. (i am using RS SP1)
> 1) upload this report into report manager
> 2) - RUN THE Report, and notice that the 2nd parameter called
> 'defaultparam' gets set to the date, and it works.. (all the report
> does is show this parameter)
> 3) - go to the parameter editing section of hte report in report
> manager
> 4) - change something UNRELELATED to defaultparam - for instance the
> PROMPT of the firstparameter - dummyparam, and then APPLY
> 5) - go back to the report - and "defaultparam" nolonger calculates the
> date (the default parameter expression in the report)
> conclusion, report manager not only updates the parameters you change,
> (as it should to give the administrator ability to), it erroneously
> updates all the parameters..
>
> <?xml version="1.0" encoding="utf-8"?>
> <Report
> xmlns="http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefinition"
> xmlns:rd="">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
> <RightMargin>1in</RightMargin>
> <Body>
> <ReportItems>
> <Textbox Name="textbox1">
> <Style>
> <PaddingLeft>2pt</PaddingLeft>
> <PaddingBottom>2pt</PaddingBottom>
> <PaddingTop>2pt</PaddingTop>
> <PaddingRight>2pt</PaddingRight>
> </Style>
> <Top>0.125in</Top>
> <rd:DefaultName>textbox1</rd:DefaultName>
> <Height>0.25in</Height>
> <Width>1in</Width>
> <CanGrow>true</CanGrow>
> <Value>=Parameters!defaultparam.Value</Value>
> <Left>0.25in</Left>
> </Textbox>
> </ReportItems>
> <Style />
> <Height>2in</Height>
> </Body>
> <TopMargin>1in</TopMargin>
> <Width>6.5in</Width>
> <LeftMargin>1in</LeftMargin>
> <rd:SnapToGrid>true</rd:SnapToGrid>
> <rd:DrawGrid>true</rd:DrawGrid>
> <rd:ReportID>ed8d8d8c-443f-4598-82a1-db50fd8cbc9a</rd:ReportID>
> <BottomMargin>1in</BottomMargin>
> <ReportParameters>
> <ReportParameter Name="dummyparam">
> <DataType>String</DataType>
> <AllowBlank>true</AllowBlank>
> <Prompt>dummyparameter</Prompt>
> </ReportParameter>
> <ReportParameter Name="defaultparam">
> <DataType>String</DataType>
> <DefaultValue>
> <Values>
> <Value>=Format(DateTime.Now,"d")</Value>
> </Values>
> </DefaultValue>
> <AllowBlank>true</AllowBlank>
> <Prompt>defaultparam</Prompt>
> </ReportParameter>
> <ReportParameter Name="nextparam">
> <DataType>String</DataType>
> <AllowBlank>true</AllowBlank>
> <Prompt>Report_Parameter_2</Prompt>
> </ReportParameter>
> </ReportParameters>
> <Language>en-US</Language>
> </Report>
>|||You may be interested in this related thread:
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=5d83b939-71ab-47fa-9f85-9d15d90dacb9
Also check my recent posting in that same thread for a possible workaround
on RS 2000 (specifying hidden parameters through report designer).
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:OEIuxKPFFHA.3284@.TK2MSFTNGP09.phx.gbl...
> By the way, the bad behaviour was duplicated on my machine...
>
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> <klumsy@.xtra.co.nz> wrote in message
> news:1108605533.668474.147440@.c13g2000cwb.googlegroups.com...
>> here is an example of this bug at work.. (i am using RS SP1)
>> 1) upload this report into report manager
>> 2) - RUN THE Report, and notice that the 2nd parameter called
>> 'defaultparam' gets set to the date, and it works.. (all the report
>> does is show this parameter)
>> 3) - go to the parameter editing section of hte report in report
>> manager
>> 4) - change something UNRELELATED to defaultparam - for instance the
>> PROMPT of the firstparameter - dummyparam, and then APPLY
>> 5) - go back to the report - and "defaultparam" nolonger calculates the
>> date (the default parameter expression in the report)
>> conclusion, report manager not only updates the parameters you change,
>> (as it should to give the administrator ability to), it erroneously
>> updates all the parameters..
>>
>> <?xml version="1.0" encoding="utf-8"?>
>> <Report
>> xmlns="http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefinition"
>> xmlns:rd="">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
>> <RightMargin>1in</RightMargin>
>> <Body>
>> <ReportItems>
>> <Textbox Name="textbox1">
>> <Style>
>> <PaddingLeft>2pt</PaddingLeft>
>> <PaddingBottom>2pt</PaddingBottom>
>> <PaddingTop>2pt</PaddingTop>
>> <PaddingRight>2pt</PaddingRight>
>> </Style>
>> <Top>0.125in</Top>
>> <rd:DefaultName>textbox1</rd:DefaultName>
>> <Height>0.25in</Height>
>> <Width>1in</Width>
>> <CanGrow>true</CanGrow>
>> <Value>=Parameters!defaultparam.Value</Value>
>> <Left>0.25in</Left>
>> </Textbox>
>> </ReportItems>
>> <Style />
>> <Height>2in</Height>
>> </Body>
>> <TopMargin>1in</TopMargin>
>> <Width>6.5in</Width>
>> <LeftMargin>1in</LeftMargin>
>> <rd:SnapToGrid>true</rd:SnapToGrid>
>> <rd:DrawGrid>true</rd:DrawGrid>
>> <rd:ReportID>ed8d8d8c-443f-4598-82a1-db50fd8cbc9a</rd:ReportID>
>> <BottomMargin>1in</BottomMargin>
>> <ReportParameters>
>> <ReportParameter Name="dummyparam">
>> <DataType>String</DataType>
>> <AllowBlank>true</AllowBlank>
>> <Prompt>dummyparameter</Prompt>
>> </ReportParameter>
>> <ReportParameter Name="defaultparam">
>> <DataType>String</DataType>
>> <DefaultValue>
>> <Values>
>> <Value>=Format(DateTime.Now,"d")</Value>
>> </Values>
>> </DefaultValue>
>> <AllowBlank>true</AllowBlank>
>> <Prompt>defaultparam</Prompt>
>> </ReportParameter>
>> <ReportParameter Name="nextparam">
>> <DataType>String</DataType>
>> <AllowBlank>true</AllowBlank>
>> <Prompt>Report_Parameter_2</Prompt>
>> </ReportParameter>
>> </ReportParameters>
>> <Language>en-US</Language>
>> </Report>
>
REPORT MANAGER - Hiding Tabs/Links ***
Is there a way to hide Tabs and Links on the REPORT MANAGER interface to
limit user access? If you can provide and example that would be highly
appreciated.Yes, you want to limit access using security. On the properties tab of any
item there should be a security sub-tab which will allow you to set what
users can and can't do with that object. Depending on a users rights only
tabs that a user can use will show up.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mike Collins" <MikeCollins@.discussions.microsoft.com> wrote in message
news:7F502733-69FE-4C4A-A16B-02E6A3192933@.microsoft.com...
> I'm not an expert on this, but you can limit user access through IIS. Make
> sure anonymous access is not checked in your security in IIS. Then through
> the Report Manager, you can add users (or groups) and give them certain
> access rights.
> "doug" wrote:
> > Is there a way to hide Tabs and Links on the REPORT MANAGER interface to
> > limit user access? If you can provide and example that would be highly
> > appreciated.
limit user access? If you can provide and example that would be highly
appreciated.Yes, you want to limit access using security. On the properties tab of any
item there should be a security sub-tab which will allow you to set what
users can and can't do with that object. Depending on a users rights only
tabs that a user can use will show up.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mike Collins" <MikeCollins@.discussions.microsoft.com> wrote in message
news:7F502733-69FE-4C4A-A16B-02E6A3192933@.microsoft.com...
> I'm not an expert on this, but you can limit user access through IIS. Make
> sure anonymous access is not checked in your security in IIS. Then through
> the Report Manager, you can add users (or groups) and give them certain
> access rights.
> "doug" wrote:
> > Is there a way to hide Tabs and Links on the REPORT MANAGER interface to
> > limit user access? If you can provide and example that would be highly
> > appreciated.
Wednesday, March 7, 2012
Report Layout depending on Rendering Format
Can I vary the layout (visibility) depending on the rendering format?
Example: If 'PDF' add a title page, if 'HTML' no title page.
ThanksIs there anybody who could help me on that issue?
"Niklas" wrote:
> Can I vary the layout (visibility) depending on the rendering format?
> Example: If 'PDF' add a title page, if 'HTML' no title page.
> Thanks|||It is not possible to have a title page in one output format, but not in
other output formats.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Niklas" <Niklas@.discussions.microsoft.com> wrote in message
news:BFB7935D-892E-4A66-BBBF-1F39B21C8608@.microsoft.com...
> Is there anybody who could help me on that issue?
> "Niklas" wrote:
> > Can I vary the layout (visibility) depending on the rendering format?
> >
> > Example: If 'PDF' add a title page, if 'HTML' no title page.
> >
> > Thanks
Example: If 'PDF' add a title page, if 'HTML' no title page.
ThanksIs there anybody who could help me on that issue?
"Niklas" wrote:
> Can I vary the layout (visibility) depending on the rendering format?
> Example: If 'PDF' add a title page, if 'HTML' no title page.
> Thanks|||It is not possible to have a title page in one output format, but not in
other output formats.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Niklas" <Niklas@.discussions.microsoft.com> wrote in message
news:BFB7935D-892E-4A66-BBBF-1F39B21C8608@.microsoft.com...
> Is there anybody who could help me on that issue?
> "Niklas" wrote:
> > Can I vary the layout (visibility) depending on the rendering format?
> >
> > Example: If 'PDF' add a title page, if 'HTML' no title page.
> >
> > Thanks
Tuesday, February 21, 2012
Report from prcedure that return multiple recordsets
Hi there,
I am creating a report from a stored procedure that returns
multiples record sets. For an example, my stored procedure is as follows
CREATE PROCEDURE MYPROCEDURE
AS
BEGIN
SELECT * FROM TABLE1
SELECT * FROM TABLE2
SELECT * FROM TABLE3
END
Now lets say I want to create a report that will display the
result of the query no 2 (which is SELECT * FROM TABLE2 in this example). How
can I do this? Is there any way to bind the second record set to the report
dataset with out changing the stored procedure?
I will appreciate any kind of suggestions on this
Thanks
Moim
yes,
you can do this in ur procedure itself. based upon what criteria you decide which query to run, pass that criteria to procedure as a parameter, and then use if condition to run the query
|||Suresh,
Thanks for your reply. But I am sorry I dont have a chance to modify the Stored procesdure. Those are written for a legacy software and they are running good for couple of years.
So can you or any one else find me an alternate to do this?
Anyway, thanks shuresh.
Thanks
Moim|||
Moim,
Unfortunately, SSRS doesn't support multiple recordsets being returned from a stored procedure. It will use the first resultset returned only.
Can you break up your master stored proc into 3 smaller stored procs, each called by separate reports with it's own resultset?
Jarret
|||Hmmm..seems I have to do that Jarret. Anyway thanks for your reply.|||Can you mark this one as answered so others can see that multiple recordsets aren't supported?
Thanks.
Jarret
|||Sure. Thanks|||Thanks Jarret for the answer. I did that earlier , but couldn't get my procedure to work by passing parameters to get the resulting resultset. Insted I have created different procedures and made it to work.
I didn't know that this is a constraint with SSRS.
Report Format with a Group
Is there a way to have the data rows begin on the same row as the group fields. For example if I have a student with multiple tests/scores, I want the tests/score to begin on the same line as the students name.
You could place everything on a detail row...basically no grouping level. This will display the student name as a repeating element, however.
You can then add some conditional logic to the Hidden property to only display the first occurrence of that student name.
|||Do you have an example of the logic to hide all but the first occurance? The programming side of this is a little new to me.|||Check out the HideDuplicates feature of TextBox: http://msdn2.microsoft.com/en-us/library/ms152916.aspx.
In ReportDesigner, right click on your textbox and check "Hide duplicates" in the Textbox Properties dialog.
Report Format with a Group
Is there a way to have the data rows begin on the same row as the group fields. For example if I have a student with multiple tests/scores, I want the tests/score to begin on the same line as the students name.
You could place everything on a detail row...basically no grouping level. This will display the student name as a repeating element, however.
You can then add some conditional logic to the Hidden property to only display the first occurrence of that student name.
|||Do you have an example of the logic to hide all but the first occurance? The programming side of this is a little new to me.|||Check out the HideDuplicates feature of TextBox: http://msdn2.microsoft.com/en-us/library/ms152916.aspx.
In ReportDesigner, right click on your textbox and check "Hide duplicates" in the Textbox Properties dialog.
Subscribe to:
Posts (Atom)