SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Reporting Services Styles in a Database Table


Reporting Services Styles in a Database Table

Author
Message
Boyan Penev
Boyan Penev
SSC Veteran
SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)SSC Veteran (230 reputation)

Group: General Forum Members
Points: 230 Visits: 125
Comments posted to this topic are about the item Reporting Services Styles in a Database Table

Boyan Penev
markus.krenn
markus.krenn
Grasshopper
Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)

Group: General Forum Members
Points: 14 Visits: 71
Hi Boyan Penev,
why do you need parameters?
Your Resultset of the StoredProcedure has only one row containg the value of the colors. So, my meaning is that you can use an expression like this in the color-Property:
=First(Fields!HeaderColour.Value, "usp_CTL_Get_Report_Colours")

Then also the disadvantage of the parameters is eliminated.

With kind regards,

Markus Krenn
markus.krenn@plus-it.de
peterzeke
peterzeke
SSCarpal Tunnel
SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)

Group: General Forum Members
Points: 4390 Visits: 1767
Interesting article... would it be possible to post the .rdl xml of an example to this discussion thread. I can't quite visualize it based on the article alone.



marty.zigman
marty.zigman
Forum Newbie
Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: General Forum Members
Points: 3 Visits: 2
Why not store the properties in an XML document (database or filesystem) to allow for a larger range of properties and values to be defined without having to modify the database each time we want to centralize a style?
Dan Guzman - Not the MVP
Dan Guzman - Not the MVP
SSCommitted
SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)

Group: General Forum Members
Points: 1906 Visits: 760
Markus - I get a scope parameter error when I try this. sp calls direct might not be allowed

correction ---- I got it to work, the second parameter is the name of the dataset, not the name of the sp. Good idea Markus.


Dan
Paul Hales-839333
Paul Hales-839333
Forum Newbie
Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: General Forum Members
Points: 3 Visits: 13
Nice one Boyan. Always good to store your corporate colours / fonts / formats etc in a centralised location. You suggested a simple .Net management screen to potentially create, update, delete the "stuff" in your tables. An alternative (although not as sexy) which could be useful is to use Report parameters to perform this functionality to avoid the need for a .net app. Thats my 2c anywho. Keep up the good work dude :-).
Martin N
Martin N
SSC-Addicted
SSC-Addicted (444 reputation)SSC-Addicted (444 reputation)SSC-Addicted (444 reputation)SSC-Addicted (444 reputation)SSC-Addicted (444 reputation)SSC-Addicted (444 reputation)SSC-Addicted (444 reputation)SSC-Addicted (444 reputation)

Group: General Forum Members
Points: 444 Visits: 177
in order to get around the problem of one dataset per report item I was thinking you could just create a table valued sql function and join it to your report resultset, just format the function output to be one row with multiple col's.

Then you could just pick the fields and setup the styles

M


Kindest Regards,

Martin
noxidjkram
noxidjkram
SSC Journeyman
SSC Journeyman (92 reputation)SSC Journeyman (92 reputation)SSC Journeyman (92 reputation)SSC Journeyman (92 reputation)SSC Journeyman (92 reputation)SSC Journeyman (92 reputation)SSC Journeyman (92 reputation)SSC Journeyman (92 reputation)

Group: General Forum Members
Points: 92 Visits: 83
markus.krenn (3/26/2009)
Hi Boyan Penev,
why do you need parameters?
Your Resultset of the StoredProcedure has only one row containg the value of the colors. So, my meaning is that you can use an expression like this in the color-Property:
=First(Fields!HeaderColour.Value, "usp_CTL_Get_Report_Colours")

Then also the disadvantage of the parameters is eliminated.

With kind regards,

Markus Krenn
markus.krenn@plus-it.de


This would be fine if it was only to be used in the report body, but you cannot access datasets like this for headers and footers hence for these you would have to store them in parameters (or in hidden textfields in the main report area that were then accessed by name from the header and footer).

BR,

Mark

SQL Novice - Here to learn.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum







































































































































































SQLServerCentral


Search