How Overwrite display text of Multi Select Dropdownlist

Hi.
I would like to overwrite a text which is displayed on a dropdownlist
when all items are selected. (with multi-selection enabled)
By default when all items are selected they are displayed separated by
coma, Instead of all items listed in a dropdown display I would like
to have for example "All Items"
Is it possible?
Thanks,
MaciejIn your dataset (or your proc, depending on how you set it up), you
need two columns. One of which should contain values to pass as
parameters, the other should contain the labels you want to see. Then
you can set up the available values section of the parameter so that
the value field points to your values and the label field points to
your labels. There are a few ways to add the "All" parameter. Here's
the one from Chris Hays' blog: http://blogs.msdn.com/chrishays/archive/2004/07/27/AllParameterValue.aspx
On Jan 22, 12:08 pm, MacChojna...@.googlemail.com wrote:
> Hi.
> I would like to overwrite a text which is displayed on a dropdownlist
> when all items are selected. (with multi-selection enabled)
> By default when all items are selected they are displayed separated by
> coma, Instead of all items listed in a dropdown display I would like
> to have for example "All Items"
> Is it possible?
> Thanks,
> Maciej|||In your dataset (or your proc, depending on how you set it up), you
need two columns. One of which should contain values to pass as
parameters, the other should contain the labels you want to see. Then
you can set up the available values section of the parameter so that
the value field points to your values and the label field points to
your labels. There are a few ways to add the "All" parameter. Here's
the one from Chris Hays' blog:
http://blogs.msdn.com/chrishays/archive/2004/07/27/AllParameterValue.aspx
Bear in mind, though - if you're using multi-select you're always
going to have the option given to select all from the multi-select as
opposed to your version of 'all' which exists as a single selection on
the list. I'm not sure you can suppress that, either.
Adam
On Jan 22, 12:08 pm, MacChojna...@.googlemail.com wrote:
> Hi.
> I would like to overwrite a text which is displayed on a dropdownlist
> when all items are selected. (with multi-selection enabled)
> By default when all items are selected they are displayed separated by
> coma, Instead of all items listed in a dropdown display I would like
> to have for example "All Items"
> Is it possible?
> Thanks,
> Maciej|||Thanks, Adam but this is not exactly what I'm looking for.
I want to have some text which overwrite text displayed in dropdown.
Lets say that we have 10 Items in dropdown,
Item1 and Item2 are selected dropdown so it displays Item1,Item2
when I select also Item5 dropdown displays Item1,Item2,Item5.
Thing is that I don't want to see this text in dropdown. I want to
have in that place something different:
Instead of "Item1,Item2,Item5" - "Text"
Thanks,
Maciej
On 22 Sty, 19:47, Adam Schmitt <adam.schm...@.gmail.com> wrote:
> In your dataset (or your proc, depending on how you set it up), you
> need two columns. One of which should contain values to pass as
> parameters, the other should contain the labels you want to see. Then
> you can set up the available values section of the parameter so that
> the value field points to your values and the label field points to
> your labels. There are a few ways to add the "All" parameter. Here's
> the one from Chris Hays' blog:http://blogs.msdn.com/chrishays/archive/2004=
/07/27/AllParameterValue...
> Bear in mind, though - if you're using multi-select you're always
> going to have the option given to select all from the multi-select as
> opposed to your version of 'all' which exists as a single selection on
> the list. I'm not sure you can suppress that, either.
> Adam
> On Jan 22, 12:08 pm, MacChojna...@.googlemail.com wrote:
>
> > Hi.
> > I would like tooverwriteatextwhich is displayed on adropdownlist
> > when all items are selected. (with multi-selection enabled)
> > By default when all items are selected they are displayed separated by
> > coma, Instead of all items listed in a dropdown display I would like
> > to have for example "All Items"
> > Is it possible?
> > Thanks,
> > Maciej- Ukryj cytowany tekst -
> - Poka=BF cytowany tekst -|||Regardless of what SSRS is capable of, what you're trying to do can
only be done theoretically if you have a replacement value for every
possible combination of available values. That said, if you didn't
have a terribly large set of available values, you could always create
a single select parameter and populate it with all of those possible
combinations, separated by commas, as values. That way you could
associate the appropriate text with those values in another field on
the database side and use that second field as your text. Other than
that, though, I'm not so sure you could replace that text short of
hiding the parameter and having the user ignore it completely (not
terribly useful if they need to be able to select values from it).
Good luck.
Adam
On Feb 26, 2:48 am, MacChojna...@.googlemail.com wrote:
> Thanks, Adam but this is not exactly what I'm looking for.
> I want to have some text which overwrite text displayed in dropdown.
> Lets say that we have 10 Items in dropdown,
> Item1 and Item2 are selected dropdown so it displays Item1,Item2
> when I select also Item5 dropdown displays Item1,Item2,Item5.
> Thing is that I don't want to see this text in dropdown. I want to
> have in that place something different:
> Instead of "Item1,Item2,Item5" - "Text"
> Thanks,
> Maciej
> On 22 Sty, 19:47, Adam Schmitt <adam.schm...@.gmail.com> wrote:
> > In your dataset (or your proc, depending on how you set it up), you
> > need two columns. One of which should contain values to pass as
> > parameters, the other should contain the labels you want to see. Then
> > you can set up the available values section of the parameter so that
> > the value field points to your values and the label field points to
> > your labels. There are a few ways to add the "All" parameter. Here's
> > the one from Chris Hays' blog:http://blogs.msdn.com/chrishays/archive/20=
04/07/27/AllParameterValue...
> > Bear in mind, though - if you're using multi-select you're always
> > going to have the option given to select all from the multi-select as
> > opposed to your version of 'all' which exists as a single selection on
> > the list. I'm not sure you can suppress that, either.
> > Adam
> > On Jan 22, 12:08 pm, MacChojna...@.googlemail.com wrote:
> > > Hi.
> > > I would like tooverwriteatextwhich is displayed on adropdownlist
> > > when all items are selected. (with multi-selection enabled)
> > > By default when all items are selected they are displayed separated by=
> > > coma, Instead of all items listed in a dropdown display I would like
> > > to have for example "All Items"
> > > Is it possible?
> > > Thanks,
> > > Maciej- Ukryj cytowany tekst -
> > - Poka=BF cytowany tekst -

How Large Is Too Large?

Hi,
Just got done with the requirements gathering and discovered
that my users want to measure about 200 items with the warehouse. So
I envision a Fact table with about 200 columns. This seems quite
large to me - but maybe other developers feel differently.
So my question is this: Is a data warehouse that contains a
single Fact table with 200 columns realistic and feasible? Or is a
single table with 200 columns a bad way to go?
JD
I don't think actual number of columns in the table could be used as metric
for good or bad design. Number of columns depends on object/data model you
choose.
If object requires 1000 measurements, all 1000 must be implemented. If all
of them can't fit into single row, then you will use 2 or more tables. But
in any case you will implement all required measurements
HTH
Alex
"Joe" <delphi561@.cox.net> wrote in message
news:1181227222.752767.93740@.o11g2000prd.googlegro ups.com...
> Hi,
> Just got done with the requirements gathering and discovered
> that my users want to measure about 200 items with the warehouse. So
> I envision a Fact table with about 200 columns. This seems quite
> large to me - but maybe other developers feel differently.
> So my question is this: Is a data warehouse that contains a
> single Fact table with 200 columns realistic and feasible? Or is a
> single table with 200 columns a bad way to go?
>
> JD
>
|||200 is not above the limit for columns, but may be > ~8K bytes and thus lead
to row overflows and significantly reduced performance. I think it will be
all about what kind of hardware you put the system on. You may be able to
have multiple facts as well.
TheSQLGuru
President
Indicium Resources, Inc.
"Joe" <delphi561@.cox.net> wrote in message
news:1181227222.752767.93740@.o11g2000prd.googlegro ups.com...
> Hi,
> Just got done with the requirements gathering and discovered
> that my users want to measure about 200 items with the warehouse. So
> I envision a Fact table with about 200 columns. This seems quite
> large to me - but maybe other developers feel differently.
> So my question is this: Is a data warehouse that contains a
> single Fact table with 200 columns realistic and feasible? Or is a
> single table with 200 columns a bad way to go?
>
> JD
>
|||Hello Joe,
In a DW structure I usually see Dimension tables with this number of columns
not fact tables. That said it is not INXS of column counts allowed and if
the number of columns is justifiable then so be it.
Watch out for width though. A fact table should be quite thin not least
because it could be carrying millions upon millions of rows.
Allan Mitchell
http://wiki.sqlis.com | http://www.sqlis.com | http://www.sqldts.com |
http://www.konesans.com

> Hi,
> Just got done with the requirements gathering and discovered
> that my users want to measure about 200 items with the warehouse. So
> I envision a Fact table with about 200 columns. This seems quite
> large to me - but maybe other developers feel differently.
> So my question is this: Is a data warehouse that contains a
> single Fact table with 200 columns realistic and feasible? Or is a
> single table with 200 columns a bad way to go?
> JD
>
|||On Jun 12, 9:30 pm, Allan Mitchell <a...@.no-spam.sqldts.com> wrote:
> Hello Joe,
> In a DW structure I usually see Dimension tables with this number of columns
> not fact tables. That said it is not INXS of column counts allowed and if
> the number of columns is justifiable then so be it.
> Watch out for width though. A fact table should be quite thin not least
> because it could be carrying millions upon millions of rows.
> --
> Allan Mitchellhttp://wiki.sqlis.com|http://www.sqlis.com|http://www.sqldts.com|http://www.konesans.com
>
>
>
> - Show quoted text -
Very interesting topic.
I guess the end-product is important here.
How will the end-user access the datawarehouse, via T-SQL based
Reports or via a cube or cubes ?
Will the facts be inserts only or will their be updates ?
Are all the facts related and can you easily guess which facts will be
reported on together ?

How Large Is Too Large?

Hi,
Just got done with the requirements gathering and discovered
that my users want to measure about 200 items with the warehouse. So
I envision a Fact table with about 200 columns. This seems quite
large to me - but maybe other developers feel differently.
So my question is this: Is a data warehouse that contains a
single Fact table with 200 columns realistic and feasible? Or is a
single table with 200 columns a bad way to go?
JDI don't think actual number of columns in the table could be used as metric
for good or bad design. Number of columns depends on object/data model you
choose.
If object requires 1000 measurements, all 1000 must be implemented. If all
of them can't fit into single row, then you will use 2 or more tables. But
in any case you will implement all required measurements
HTH
Alex
"Joe" <delphi561@.cox.net> wrote in message
news:1181227222.752767.93740@.o11g2000prd.googlegroups.com...
> Hi,
> Just got done with the requirements gathering and discovered
> that my users want to measure about 200 items with the warehouse. So
> I envision a Fact table with about 200 columns. This seems quite
> large to me - but maybe other developers feel differently.
> So my question is this: Is a data warehouse that contains a
> single Fact table with 200 columns realistic and feasible? Or is a
> single table with 200 columns a bad way to go?
>
> JD
>|||200 is not above the limit for columns, but may be > ~8K bytes and thus lead
to row overflows and significantly reduced performance. I think it will be
all about what kind of hardware you put the system on. You may be able to
have multiple facts as well.
TheSQLGuru
President
Indicium Resources, Inc.
"Joe" <delphi561@.cox.net> wrote in message
news:1181227222.752767.93740@.o11g2000prd.googlegroups.com...
> Hi,
> Just got done with the requirements gathering and discovered
> that my users want to measure about 200 items with the warehouse. So
> I envision a Fact table with about 200 columns. This seems quite
> large to me - but maybe other developers feel differently.
> So my question is this: Is a data warehouse that contains a
> single Fact table with 200 columns realistic and feasible? Or is a
> single table with 200 columns a bad way to go?
>
> JD
>|||Hello Joe,
In a DW structure I usually see Dimension tables with this number of columns
not fact tables. That said it is not INXS of column counts allowed and if
the number of columns is justifiable then so be it.
Watch out for width though. A fact table should be quite thin not least
because it could be carrying millions upon millions of rows.
Allan Mitchell
http://wiki.sqlis.com | http://www.sqlis.com | http://www.sqldts.com |
http://www.konesans.com

> Hi,
> Just got done with the requirements gathering and discovered
> that my users want to measure about 200 items with the warehouse. So
> I envision a Fact table with about 200 columns. This seems quite
> large to me - but maybe other developers feel differently.
> So my question is this: Is a data warehouse that contains a
> single Fact table with 200 columns realistic and feasible? Or is a
> single table with 200 columns a bad way to go?
> JD
>|||On Jun 12, 9:30 pm, Allan Mitchell <a...@.no-spam.sqldts.com> wrote:
> Hello Joe,
> In a DW structure I usually see Dimension tables with this number of colum
ns
> not fact tables. That said it is not INXS of column counts allowed and if
> the number of columns is justifiable then so be it.
> Watch out for width though. A fact table should be quite thin not least
> because it could be carrying millions upon millions of rows.
> --
> Allan Mitchellhttp://wiki.sqlis.com|http://www.sqlis.com|http://www.sqldts.com|ttp://www.konesans.com" target="_blank">h
ttp://www.konesans.com
>
>
>
>
>
> - Show quoted text -
Very interesting topic.
I guess the end-product is important here.
How will the end-user access the datawarehouse, via T-SQL based
Reports or via a cube or cubes ?
Will the facts be inserts only or will their be updates ?
Are all the facts related and can you easily guess which facts will be
reported on together ?