Reporting Services Styles in a Database Table

  • Boyan Penev

    SSC-Addicted

    Points: 490

    Comments posted to this topic are about the item Reporting Services Styles in a Database Table

  • markus.krenn

    Grasshopper

    Points: 22

    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

    SSCrazy Eights

    Points: 8932

    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

    SSC Rookie

    Points: 27

    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

    Hall of Fame

    Points: 3571

    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

    Grasshopper

    Points: 19

    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

    Ten Centuries

    Points: 1186

    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

    SSC Veteran

    Points: 200

    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.

Viewing 8 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply