Can we a use a CSS or equivalent for a reports(RDLC File)

Hi,

I will be using RDLC files to display reports in various pages.

My Question is this.

I need to use the same type of formatting of color,fonts,font sizes and the background colors so that the same can be used across the reports.

This is somewhat like using a CSS file for aspx pages.

Any ideas... , solution........, .......

Hi,

Just wondering!

We have CSS for the aspx and the HTML pages.

Are there no ways to set a golbal standard for the Reports( Ok, be it a Server report or a local report.). Is it not correct what I am asking.

|||I've been looking into this also, and I found some old threads stating that themes and css are not supported but that they may be in the next version.|||

Hello,

Formatting for reports can be expression based. Create your reports using a standard formula for similar items and pass in values through a dataset. Another option would be to take formatting information in as parameters. The RDL file is just an XML file, you could modify it directly if you want. Here is a link to information on programmatically generating RDLs: http://technet.microsoft.com/en-us/library/ms154583.aspx. RDLs and RDLCs are very similar, and the same techniques could be used.

Good luck,

Larry

|||I need a clarification.

How do I assign a class in the css to a text box.

Say I have a class .txtboxTahomaBold in the CSS, how do I assign the class to the textbox. I do not find any property for the controls (textbox, table .... )|||

I am sorry to have misslead you. You do not get to assign CSS to the textboxes, but you can assign the regular SSRS formatting to each text box on a report prior to displaying it. The easiest way would be to create formulas within the report based on data that you provide through a dataset. For example, set the Font formula to =FieldsTextBoxTahomaBold.Value and have the dataset pass in the string "Normal, Tahoma, 11pt, Bold". Of course, you could also modify the XML, but that is more trouble than it is worth.

I will try and get an example written up on my blog. I will post a link here when I do.

Larry

|||

Thanks.

Waiting for your reply.

|||

Formatting your report based on the user or the data is relatively straight forward once you get the trick. To demonstrate, create a report with a valid connection to an instance of Microsoft SQL Server and use the following SQL as your query:

Code Snippet

SELECT
CASE @.param
WHEN 0 THEN 'Blue'
WHEN 1 THEN 'Red'
END AS color,
CASE @.param
WHEN 0 THEN '12pt'
WHEN 1 THEN '24pt'
END AS size

and create five text boxes with the following attributes:
TextBox1
Value: Color
Color: =First(Fields!color.Value)

TextBox2
Value: Size
Font: Normal, Arial, =First(Fields!size.Value), Normal

TextBox3
Value: Both
Color: =First(Fields!color.Value)
Font: Normal, Arial, =First(Fields!size.Value), Normal

TextBox4
Value: =First(Fields!color.Value)

TextBox5
Value: =First(Fields!size.Value)

Sorry for the delay. The article at http://smithmier.com/blog/?p=38 has a picture of the results, but it really isn't required to understand the concept.

|||

Hi Larry,

Thanks for the post.

I will check it out.

Can we a use a CSS or equivalent for a reports(RDLC File)

Hi,

I will be using RDLC files to display reports in various pages.

My Question is this.

I need to use the same type of formatting of color,fonts,font sizes and the background colors so that the same can be used across the reports.

This is somewhat like using a CSS file for aspx pages.

Any ideas... , solution........, .......

Hi,

Just wondering!

We have CSS for the aspx and the HTML pages.

Are there no ways to set a golbal standard for the Reports( Ok, be it a Server report or a local report.). Is it not correct what I am asking.

|||I've been looking into this also, and I found some old threads stating that themes and css are not supported but that they may be in the next version.|||

Hello,

Formatting for reports can be expression based. Create your reports using a standard formula for similar items and pass in values through a dataset. Another option would be to take formatting information in as parameters. The RDL file is just an XML file, you could modify it directly if you want. Here is a link to information on programmatically generating RDLs: http://technet.microsoft.com/en-us/library/ms154583.aspx. RDLs and RDLCs are very similar, and the same techniques could be used.

Good luck,

Larry

|||I need a clarification.

How do I assign a class in the css to a text box.

Say I have a class .txtboxTahomaBold in the CSS, how do I assign the class to the textbox. I do not find any property for the controls (textbox, table .... )|||

I am sorry to have misslead you. You do not get to assign CSS to the textboxes, but you can assign the regular SSRS formatting to each text box on a report prior to displaying it. The easiest way would be to create formulas within the report based on data that you provide through a dataset. For example, set the Font formula to =FieldsTextBoxTahomaBold.Value and have the dataset pass in the string "Normal, Tahoma, 11pt, Bold". Of course, you could also modify the XML, but that is more trouble than it is worth.

I will try and get an example written up on my blog. I will post a link here when I do.

Larry

|||

Thanks.

Waiting for your reply.

|||

Formatting your report based on the user or the data is relatively straight forward once you get the trick. To demonstrate, create a report with a valid connection to an instance of Microsoft SQL Server and use the following SQL as your query:

Code Snippet

SELECT
CASE @.param
WHEN 0 THEN 'Blue'
WHEN 1 THEN 'Red'
END AS color,
CASE @.param
WHEN 0 THEN '12pt'
WHEN 1 THEN '24pt'
END AS size

and create five text boxes with the following attributes:
TextBox1
Value: Color
Color: =First(Fields!color.Value)

TextBox2
Value: Size
Font: Normal, Arial, =First(Fields!size.Value), Normal

TextBox3
Value: Both
Color: =First(Fields!color.Value)
Font: Normal, Arial, =First(Fields!size.Value), Normal

TextBox4
Value: =First(Fields!color.Value)

TextBox5
Value: =First(Fields!size.Value)

Sorry for the delay. The article at http://smithmier.com/blog/?p=38 has a picture of the results, but it really isn't required to understand the concept.

|||

Hi Larry,

Thanks for the post.

I will check it out.

can replication works for a Data Warehouse ?

Hi ,
I am trying to set replication for an exsiting Data Center (let's call it
DC) from the various databases in Server1
my problem :
1) i set up the publication with the snapshot to keep existing data in the
table(there's already data) if same table name is found , however, the
synchronization failed becoz of duplicate index/key
ques : shldn't it just ignore those duplicates ?
and even if there's new data for that table it couldn't replicate over due
to the duplicates
2) i have also tried to use this option "to delete those matching with row
filter" but i realised that those that are the same record it would be
deleted and re-replicated over but those in the destination that not in the
source table have been deleted
3) i finally tried using this option "to delete data and re-create the table
and it works but the issue here is i have many databases to be replicated
over to the data warhouse , i shldn't be forced to purposely removed a table
with data to somewhere else and then after replicate is successful then copy
that data over
could any one kindly advise
tks & rdgs
Yes replication can be used in this scenario. Snapshot replication performs
a period refresh of all of the data. It sounds like transactional
replication might be a better option for you (incremental changes).
HTH
Jerry
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:91170637-D104-4CCD-AEC9-F2458A0C282A@.microsoft.com...
> Hi ,
> I am trying to set replication for an exsiting Data Center (let's call it
> DC) from the various databases in Server1
> my problem :
> 1) i set up the publication with the snapshot to keep existing data in the
> table(there's already data) if same table name is found , however, the
> synchronization failed becoz of duplicate index/key
> ques : shldn't it just ignore those duplicates ?
> and even if there's new data for that table it couldn't replicate over due
> to the duplicates
> 2) i have also tried to use this option "to delete those matching with row
> filter" but i realised that those that are the same record it would be
> deleted and re-replicated over but those in the destination that not in
> the
> source table have been deleted
> 3) i finally tried using this option "to delete data and re-create the
> table
> and it works but the issue here is i have many databases to be replicated
> over to the data warhouse , i shldn't be forced to purposely removed a
> table
> with data to somewhere else and then after replicate is successful then
> copy
> that data over
> could any one kindly advise
> tks & rdgs
|||Hi,
If Replication does work for a Data Warehouse , how shld i set it up as i
have tried the settings below but it somehow did not work for me
appreciate any advise
tks & rdgs
"Jerry Spivey" wrote:

> Yes replication can be used in this scenario. Snapshot replication performs
> a period refresh of all of the data. It sounds like transactional
> replication might be a better option for you (incremental changes).
> HTH
> Jerry
> "maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
> news:91170637-D104-4CCD-AEC9-F2458A0C282A@.microsoft.com...
>
>
|||Replication can be a difficult. If I were you I would step back from the
whole data warehouse thing and implement both snapshot and transactional
replication on a test box and become familiar with the varioius offerings,
options, agents, icons and settings (BOL is pretty good at explaining
replication types). Once you have a better understand of how replication
works and what are the basic and advanced feature sets of repliction, I
think you'll be able to determine which replication type (if any - maybe DTS
would work better or BULK INSERT) would be best for your scenario.
HTH
Jerry
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:A7FEFCA8-8244-45D7-B664-6A5656121451@.microsoft.com...[vbcol=seagreen]
> Hi,
> If Replication does work for a Data Warehouse , how shld i set it up as i
> have tried the settings below but it somehow did not work for me
> appreciate any advise
> tks & rdgs
> "Jerry Spivey" wrote:

can replication works for a Data Warehouse ?

Hi ,
I am trying to set replication for an exsiting Data Center (let's call it
DC) from the various databases in Server1
my problem :
1) i set up the publication with the snapshot to keep existing data in the
table(there's already data) if same table name is found , however, the
synchronization failed becoz of duplicate index/key
ques : shldn't it just ignore those duplicates ?
and even if there's new data for that table it couldn't replicate over due
to the duplicates
2) i have also tried to use this option "to delete those matching with row
filter" but i realised that those that are the same record it would be
deleted and re-replicated over but those in the destination that not in the
source table have been deleted
3) i finally tried using this option "to delete data and re-create the table
and it works but the issue here is i have many databases to be replicated
over to the data warhouse , i shldn't be forced to purposely removed a table
with data to somewhere else and then after replicate is successful then copy
that data over
could any one kindly advise
tks & rdgsYes replication can be used in this scenario. Snapshot replication performs
a period refresh of all of the data. It sounds like transactional
replication might be a better option for you (incremental changes).
HTH
Jerry
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:91170637-D104-4CCD-AEC9-F2458A0C282A@.microsoft.com...
> Hi ,
> I am trying to set replication for an exsiting Data Center (let's call it
> DC) from the various databases in Server1
> my problem :
> 1) i set up the publication with the snapshot to keep existing data in the
> table(there's already data) if same table name is found , however, the
> synchronization failed becoz of duplicate index/key
> ques : shldn't it just ignore those duplicates ?
> and even if there's new data for that table it couldn't replicate over due
> to the duplicates
> 2) i have also tried to use this option "to delete those matching with row
> filter" but i realised that those that are the same record it would be
> deleted and re-replicated over but those in the destination that not in
> the
> source table have been deleted
> 3) i finally tried using this option "to delete data and re-create the
> table
> and it works but the issue here is i have many databases to be replicated
> over to the data warhouse , i shldn't be forced to purposely removed a
> table
> with data to somewhere else and then after replicate is successful then
> copy
> that data over
> could any one kindly advise
> tks & rdgs|||Hi,
If Replication does work for a Data Warehouse , how shld i set it up as i
have tried the settings below but it somehow did not work for me
appreciate any advise
tks & rdgs
"Jerry Spivey" wrote:
> Yes replication can be used in this scenario. Snapshot replication performs
> a period refresh of all of the data. It sounds like transactional
> replication might be a better option for you (incremental changes).
> HTH
> Jerry
> "maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
> news:91170637-D104-4CCD-AEC9-F2458A0C282A@.microsoft.com...
> > Hi ,
> >
> > I am trying to set replication for an exsiting Data Center (let's call it
> > DC) from the various databases in Server1
> >
> > my problem :
> >
> > 1) i set up the publication with the snapshot to keep existing data in the
> > table(there's already data) if same table name is found , however, the
> > synchronization failed becoz of duplicate index/key
> >
> > ques : shldn't it just ignore those duplicates ?
> >
> > and even if there's new data for that table it couldn't replicate over due
> > to the duplicates
> >
> > 2) i have also tried to use this option "to delete those matching with row
> > filter" but i realised that those that are the same record it would be
> > deleted and re-replicated over but those in the destination that not in
> > the
> > source table have been deleted
> >
> > 3) i finally tried using this option "to delete data and re-create the
> > table
> > and it works but the issue here is i have many databases to be replicated
> > over to the data warhouse , i shldn't be forced to purposely removed a
> > table
> > with data to somewhere else and then after replicate is successful then
> > copy
> > that data over
> >
> > could any one kindly advise
> >
> > tks & rdgs
>
>|||Replication can be a difficult. If I were you I would step back from the
whole data warehouse thing and implement both snapshot and transactional
replication on a test box and become familiar with the varioius offerings,
options, agents, icons and settings (BOL is pretty good at explaining
replication types). Once you have a better understand of how replication
works and what are the basic and advanced feature sets of repliction, I
think you'll be able to determine which replication type (if any - maybe DTS
would work better or BULK INSERT) would be best for your scenario.
HTH
Jerry
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:A7FEFCA8-8244-45D7-B664-6A5656121451@.microsoft.com...
> Hi,
> If Replication does work for a Data Warehouse , how shld i set it up as i
> have tried the settings below but it somehow did not work for me
> appreciate any advise
> tks & rdgs
> "Jerry Spivey" wrote:
>> Yes replication can be used in this scenario. Snapshot replication
>> performs
>> a period refresh of all of the data. It sounds like transactional
>> replication might be a better option for you (incremental changes).
>> HTH
>> Jerry
>> "maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
>> news:91170637-D104-4CCD-AEC9-F2458A0C282A@.microsoft.com...
>> > Hi ,
>> >
>> > I am trying to set replication for an exsiting Data Center (let's call
>> > it
>> > DC) from the various databases in Server1
>> >
>> > my problem :
>> >
>> > 1) i set up the publication with the snapshot to keep existing data in
>> > the
>> > table(there's already data) if same table name is found , however, the
>> > synchronization failed becoz of duplicate index/key
>> >
>> > ques : shldn't it just ignore those duplicates ?
>> >
>> > and even if there's new data for that table it couldn't replicate over
>> > due
>> > to the duplicates
>> >
>> > 2) i have also tried to use this option "to delete those matching with
>> > row
>> > filter" but i realised that those that are the same record it would be
>> > deleted and re-replicated over but those in the destination that not in
>> > the
>> > source table have been deleted
>> >
>> > 3) i finally tried using this option "to delete data and re-create the
>> > table
>> > and it works but the issue here is i have many databases to be
>> > replicated
>> > over to the data warhouse , i shldn't be forced to purposely removed a
>> > table
>> > with data to somewhere else and then after replicate is successful then
>> > copy
>> > that data over
>> >
>> > could any one kindly advise
>> >
>> > tks & rdgs
>>

can replication works for a Data Warehouse ?

Hi ,
I am trying to set replication for an exsiting Data Center (let's call it
DC) from the various databases in Server1
my problem :
1) i set up the publication with the snapshot to keep existing data in the
table(there's already data) if same table name is found , however, the
synchronization failed becoz of duplicate index/key
ques : shldn't it just ignore those duplicates ?
and even if there's new data for that table it couldn't replicate over due
to the duplicates
2) i have also tried to use this option "to delete those matching with row
filter" but i realised that those that are the same record it would be
deleted and re-replicated over but those in the destination that not in the
source table have been deleted
3) i finally tried using this option "to delete data and re-create the table
and it works but the issue here is i have many databases to be replicated
over to the data warhouse , i shldn't be forced to purposely removed a table
with data to somewhere else and then after replicate is successful then copy
that data over
could any one kindly advise
tks & rdgsYes replication can be used in this scenario. Snapshot replication performs
a period refresh of all of the data. It sounds like transactional
replication might be a better option for you (incremental changes).
HTH
Jerry
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:91170637-D104-4CCD-AEC9-F2458A0C282A@.microsoft.com...
> Hi ,
> I am trying to set replication for an exsiting Data Center (let's call it
> DC) from the various databases in Server1
> my problem :
> 1) i set up the publication with the snapshot to keep existing data in the
> table(there's already data) if same table name is found , however, the
> synchronization failed becoz of duplicate index/key
> ques : shldn't it just ignore those duplicates ?
> and even if there's new data for that table it couldn't replicate over due
> to the duplicates
> 2) i have also tried to use this option "to delete those matching with row
> filter" but i realised that those that are the same record it would be
> deleted and re-replicated over but those in the destination that not in
> the
> source table have been deleted
> 3) i finally tried using this option "to delete data and re-create the
> table
> and it works but the issue here is i have many databases to be replicated
> over to the data warhouse , i shldn't be forced to purposely removed a
> table
> with data to somewhere else and then after replicate is successful then
> copy
> that data over
> could any one kindly advise
> tks & rdgs|||Hi,
If Replication does work for a Data Warehouse , how shld i set it up as i
have tried the settings below but it somehow did not work for me
appreciate any advise
tks & rdgs
"Jerry Spivey" wrote:

> Yes replication can be used in this scenario. Snapshot replication perfor
ms
> a period refresh of all of the data. It sounds like transactional
> replication might be a better option for you (incremental changes).
> HTH
> Jerry
> "maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
> news:91170637-D104-4CCD-AEC9-F2458A0C282A@.microsoft.com...
>
>|||Replication can be a difficult. If I were you I would step back from the
whole data warehouse thing and implement both snapshot and transactional
replication on a test box and become familiar with the varioius offerings,
options, agents, icons and settings (BOL is pretty good at explaining
replication types). Once you have a better understand of how replication
works and what are the basic and advanced feature sets of repliction, I
think you'll be able to determine which replication type (if any - maybe DTS
would work better or BULK INSERT) would be best for your scenario.
HTH
Jerry
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:A7FEFCA8-8244-45D7-B664-6A5656121451@.microsoft.com...[vbcol=seagreen]
> Hi,
> If Replication does work for a Data Warehouse , how shld i set it up as i
> have tried the settings below but it somehow did not work for me
> appreciate any advise
> tks & rdgs
> "Jerry Spivey" wrote:
>