Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Reporting Services Styles in a Database Table Expand / Collapse
Author
Message
Posted Thursday, March 26, 2009 12:26 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, May 30, 2012 7:15 PM
Points: 22, Visits: 121
Comments posted to this topic are about the item Reporting Services Styles in a Database Table

Boyan Penev
Post #683860
Posted Thursday, March 26, 2009 3:19 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, April 09, 2014 6:37 AM
Points: 12, Visits: 66
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
Post #683921
Posted Thursday, March 26, 2009 6:15 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: 2 days ago @ 10:49 AM
Points: 314, Visits: 1,448
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.


Post #684028
Posted Thursday, March 26, 2009 6:32 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, October 08, 2009 6:29 AM
Points: 1, 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?
Post #684038
Posted Thursday, March 26, 2009 12:31 PM
Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Monday, September 30, 2013 9:43 AM
Points: 710, Visits: 664
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
Post #684480
Posted Thursday, March 26, 2009 4:45 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, July 23, 2009 11:32 PM
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 .
Post #684683
Posted Sunday, March 29, 2009 7:33 PM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Tuesday, April 01, 2014 3:59 AM
Points: 79, Visits: 165
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
Post #685841
Posted Tuesday, March 31, 2009 3:49 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, January 22, 2014 3:28 AM
Points: 13, Visits: 74
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.
Post #686817
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse