Problems with Dataset, Table Filters SSRS 2000 SP2

Hello all..
I've put this question out before, but I still haven't figured out a
solution..
When I apply this filter at the dataset or table level to get rid of
commission code 100 it blanks out the report
Expression: =Cstr(Fields!CommissionCode.Value)
Operator: = Value: '100'
I did discover that when I run this under the data tab to look at the raw
data, the filter works! But the report still comes up blank when I preview
it..
Help!!
Thanks.Its pretty apparent to me that due to the lack of response on this issue
that dataset and table filters aren't well supported on this version of
SSRS.. I will take another approach. I hope this post will save someone else
some time in the future.. Thanks
"jereviscious" <here@.there.com> wrote in message
news:eJTkrZ7bHHA.4000@.TK2MSFTNGP02.phx.gbl...
> Hello all..
> I've put this question out before, but I still haven't figured out a
> solution..
> When I apply this filter at the dataset or table level to get rid of
> commission code 100 it blanks out the report
> Expression: =Cstr(Fields!CommissionCode.Value)
> Operator: => Value: '100'
> I did discover that when I run this under the data tab to look at the raw
> data, the filter works! But the report still comes up blank when I preview
> it..
> Help!!
> Thanks.
>
>|||Wrong assumption.
People answer on a volunteer basis. You post might or might not be seen.
Take my case. I don't use filters because I think they are mostly a bad idea
to do. Filters are used after the data is brought over to the report. I use
query parameters. Query parameters do the same thing but it applies the
filter at the database, not at the report.
However, just because I don't use it does not means that filters don't work.
I have not seen any indications that they don't work. If you didn't get a
response you could try posting again. Or try the web forums. The web forums
have a lot more eyeballs.
If you have MSDN you might check out managed newsgroups. Managed newsgroups
are done by registering a fake email address with microsoft. That email
address gets monitored in the newsgroup and you are guaranteed a response
from a MS employee within two business days.
One last thing, have you tried query parameters? That really is the way to
go in most cases.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"jereviscious" <here@.there.com> wrote in message
news:ecjpzh%23bHHA.5044@.TK2MSFTNGP05.phx.gbl...
> Its pretty apparent to me that due to the lack of response on this issue
> that dataset and table filters aren't well supported on this version of
> SSRS.. I will take another approach. I hope this post will save someone
> else some time in the future.. Thanks
> "jereviscious" <here@.there.com> wrote in message
> news:eJTkrZ7bHHA.4000@.TK2MSFTNGP02.phx.gbl...
>> Hello all..
>> I've put this question out before, but I still haven't figured out a
>> solution..
>> When I apply this filter at the dataset or table level to get rid of
>> commission code 100 it blanks out the report
>> Expression: =Cstr(Fields!CommissionCode.Value)
>> Operator: =>> Value: '100'
>> I did discover that when I run this under the data tab to look at the raw
>> data, the filter works! But the report still comes up blank when I
>> preview it..
>> Help!!
>> Thanks.
>>
>>
>|||Bruce, thanks for your thoughtful response .
I'm not making any assumption here. I have anectdotal evidence, and in my
OPINION, which I have a right to, this filtering mechanism is NOT well
supported/implemented.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:eL6kw8%23bHHA.260@.TK2MSFTNGP02.phx.gbl...
> Wrong assumption.
> People answer on a volunteer basis. You post might or might not be seen.
> Take my case. I don't use filters because I think they are mostly a bad
> idea to do. Filters are used after the data is brought over to the report.
> I use query parameters. Query parameters do the same thing but it applies
> the filter at the database, not at the report.
> However, just because I don't use it does not means that filters don't
> work. I have not seen any indications that they don't work. If you didn't
> get a response you could try posting again. Or try the web forums. The web
> forums have a lot more eyeballs.
> If you have MSDN you might check out managed newsgroups. Managed
> newsgroups are done by registering a fake email address with microsoft.
> That email address gets monitored in the newsgroup and you are guaranteed
> a response from a MS employee within two business days.
> One last thing, have you tried query parameters? That really is the way to
> go in most cases.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "jereviscious" <here@.there.com> wrote in message
> news:ecjpzh%23bHHA.5044@.TK2MSFTNGP05.phx.gbl...
>> Its pretty apparent to me that due to the lack of response on this issue
>> that dataset and table filters aren't well supported on this version of
>> SSRS.. I will take another approach. I hope this post will save someone
>> else some time in the future.. Thanks
>> "jereviscious" <here@.there.com> wrote in message
>> news:eJTkrZ7bHHA.4000@.TK2MSFTNGP02.phx.gbl...
>> Hello all..
>> I've put this question out before, but I still haven't figured out a
>> solution..
>> When I apply this filter at the dataset or table level to get rid of
>> commission code 100 it blanks out the report
>> Expression: =Cstr(Fields!CommissionCode.Value)
>> Operator: =>> Value: '100'
>> I did discover that when I run this under the data tab to look at the
>> raw data, the filter works! But the report still comes up blank when I
>> preview it..
>> Help!!
>> Thanks.
>>
>>
>>
>|||Yes you are right to your opinion, I'm not saying you aren't. However, if
you mean supported as in does the product support (work with) filters then I
have never seen anything with any posts where filters did not function. If
you mean supported because of response in this newsgroup, this newsgroup is
dying. Most of the action is in the web forums. Pretty much 0 MS people come
here, except for managed newsgroup postings. MS is putting all its focus on
the web forum. I prefer newsgroups but I am thinking of heading over to the
web forums.
So, if you want to use filters (which I suggest you do only as a last
resort) you should try both searching and posting at the web forums.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"jereviscious" <here@.there.com> wrote in message
news:%23cIgSwHcHHA.4004@.TK2MSFTNGP06.phx.gbl...
> Bruce, thanks for your thoughtful response .
> I'm not making any assumption here. I have anectdotal evidence, and in my
> OPINION, which I have a right to, this filtering mechanism is NOT well
> supported/implemented.
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:eL6kw8%23bHHA.260@.TK2MSFTNGP02.phx.gbl...
>> Wrong assumption.
>> People answer on a volunteer basis. You post might or might not be seen.
>> Take my case. I don't use filters because I think they are mostly a bad
>> idea to do. Filters are used after the data is brought over to the
>> report. I use query parameters. Query parameters do the same thing but it
>> applies the filter at the database, not at the report.
>> However, just because I don't use it does not means that filters don't
>> work. I have not seen any indications that they don't work. If you didn't
>> get a response you could try posting again. Or try the web forums. The
>> web forums have a lot more eyeballs.
>> If you have MSDN you might check out managed newsgroups. Managed
>> newsgroups are done by registering a fake email address with microsoft.
>> That email address gets monitored in the newsgroup and you are guaranteed
>> a response from a MS employee within two business days.
>> One last thing, have you tried query parameters? That really is the way
>> to go in most cases.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "jereviscious" <here@.there.com> wrote in message
>> news:ecjpzh%23bHHA.5044@.TK2MSFTNGP05.phx.gbl...
>> Its pretty apparent to me that due to the lack of response on this issue
>> that dataset and table filters aren't well supported on this version of
>> SSRS.. I will take another approach. I hope this post will save someone
>> else some time in the future.. Thanks
>> "jereviscious" <here@.there.com> wrote in message
>> news:eJTkrZ7bHHA.4000@.TK2MSFTNGP02.phx.gbl...
>> Hello all..
>> I've put this question out before, but I still haven't figured out a
>> solution..
>> When I apply this filter at the dataset or table level to get rid of
>> commission code 100 it blanks out the report
>> Expression: =Cstr(Fields!CommissionCode.Value)
>> Operator: =>> Value: '100'
>> I did discover that when I run this under the data tab to look at the
>> raw data, the filter works! But the report still comes up blank when I
>> preview it..
>> Help!!
>> Thanks.
>>
>>
>>
>>
>|||I'm wasn't criticizing the forum. It took me 6-7 hours to come up with the
correct syntax for this expression
=Cstr(Fields!CommissionCode.Value) = '100'
Simply refuses to work. I tried probably 30 different permutations
attempting to work with the string value. I finally tried this expression,
and it worked
=Cint(Fields!CommissionCode.Value) = =100
Which works fine unless you have a commission code = 032, which fortunately
for this report, doesn't affect anything, but it easily could have.
This should have taken 2 minutes. This was not a last resort problem, but it
WAS a much cleaner solution (far less code) than the alternative.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:ONB%23kzHcHHA.4312@.TK2MSFTNGP05.phx.gbl...
> Yes you are right to your opinion, I'm not saying you aren't. However, if
> you mean supported as in does the product support (work with) filters then
> I have never seen anything with any posts where filters did not function.
> If you mean supported because of response in this newsgroup, this
> newsgroup is dying. Most of the action is in the web forums. Pretty much 0
> MS people come here, except for managed newsgroup postings. MS is putting
> all its focus on the web forum. I prefer newsgroups but I am thinking of
> heading over to the web forums.
> So, if you want to use filters (which I suggest you do only as a last
> resort) you should try both searching and posting at the web forums.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "jereviscious" <here@.there.com> wrote in message
> news:%23cIgSwHcHHA.4004@.TK2MSFTNGP06.phx.gbl...
>> Bruce, thanks for your thoughtful response .
>> I'm not making any assumption here. I have anectdotal evidence, and in my
>> OPINION, which I have a right to, this filtering mechanism is NOT well
>> supported/implemented.
>>
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:eL6kw8%23bHHA.260@.TK2MSFTNGP02.phx.gbl...
>> Wrong assumption.
>> People answer on a volunteer basis. You post might or might not be seen.
>> Take my case. I don't use filters because I think they are mostly a bad
>> idea to do. Filters are used after the data is brought over to the
>> report. I use query parameters. Query parameters do the same thing but
>> it applies the filter at the database, not at the report.
>> However, just because I don't use it does not means that filters don't
>> work. I have not seen any indications that they don't work. If you
>> didn't get a response you could try posting again. Or try the web
>> forums. The web forums have a lot more eyeballs.
>> If you have MSDN you might check out managed newsgroups. Managed
>> newsgroups are done by registering a fake email address with microsoft.
>> That email address gets monitored in the newsgroup and you are
>> guaranteed a response from a MS employee within two business days.
>> One last thing, have you tried query parameters? That really is the way
>> to go in most cases.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "jereviscious" <here@.there.com> wrote in message
>> news:ecjpzh%23bHHA.5044@.TK2MSFTNGP05.phx.gbl...
>> Its pretty apparent to me that due to the lack of response on this
>> issue that dataset and table filters aren't well supported on this
>> version of SSRS.. I will take another approach. I hope this post will
>> save someone else some time in the future.. Thanks
>> "jereviscious" <here@.there.com> wrote in message
>> news:eJTkrZ7bHHA.4000@.TK2MSFTNGP02.phx.gbl...
>> Hello all..
>> I've put this question out before, but I still haven't figured out a
>> solution..
>> When I apply this filter at the dataset or table level to get rid of
>> commission code 100 it blanks out the report
>> Expression: =Cstr(Fields!CommissionCode.Value)
>> Operator: =>> Value: '100'
>> I did discover that when I run this under the data tab to look at the
>> raw data, the filter works! But the report still comes up blank when I
>> preview it..
>> Help!!
>> Thanks.
>>
>>
>>
>>
>>
>|||I have missed your earlier post. As far as your assumptions, I am with Bruce.
Infact its not like they are not supported, people have not come across, like
this, that's why no one replied or like me, have missed the post.
Anyways, so giving in query parameters is good, answering your post.
It s something to do with your data type and your single and double quote.
ie you are converting to string and giving single quote in the expression
window.
How to find out is sometime you need to give the wrong input to find out the
way to give the right input. Try diff. options give integer as input, give it
in double quotes or give a blank input. see what happens.
Let me know whether it works.
Amarnath, MCTS.
"Bruce L-C [MVP]" wrote:
> Wrong assumption.
> People answer on a volunteer basis. You post might or might not be seen.
> Take my case. I don't use filters because I think they are mostly a bad idea
> to do. Filters are used after the data is brought over to the report. I use
> query parameters. Query parameters do the same thing but it applies the
> filter at the database, not at the report.
> However, just because I don't use it does not means that filters don't work.
> I have not seen any indications that they don't work. If you didn't get a
> response you could try posting again. Or try the web forums. The web forums
> have a lot more eyeballs.
> If you have MSDN you might check out managed newsgroups. Managed newsgroups
> are done by registering a fake email address with microsoft. That email
> address gets monitored in the newsgroup and you are guaranteed a response
> from a MS employee within two business days.
> One last thing, have you tried query parameters? That really is the way to
> go in most cases.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "jereviscious" <here@.there.com> wrote in message
> news:ecjpzh%23bHHA.5044@.TK2MSFTNGP05.phx.gbl...
> > Its pretty apparent to me that due to the lack of response on this issue
> > that dataset and table filters aren't well supported on this version of
> > SSRS.. I will take another approach. I hope this post will save someone
> > else some time in the future.. Thanks
> > "jereviscious" <here@.there.com> wrote in message
> > news:eJTkrZ7bHHA.4000@.TK2MSFTNGP02.phx.gbl...
> >> Hello all..
> >>
> >> I've put this question out before, but I still haven't figured out a
> >> solution..
> >>
> >> When I apply this filter at the dataset or table level to get rid of
> >> commission code 100 it blanks out the report
> >>
> >> Expression: =Cstr(Fields!CommissionCode.Value)
> >> Operator: => >> Value: '100'
> >>
> >> I did discover that when I run this under the data tab to look at the raw
> >> data, the filter works! But the report still comes up blank when I
> >> preview it..
> >>
> >> Help!!
> >>
> >> Thanks.
> >>
> >>
> >>
> >>
> >
> >
>
>|||I have answered this question ad infinitum. I have not made any assumptions
thank-you
"Amarnath" <Amarnath@.discussions.microsoft.com> wrote in message
news:7236F647-63FA-47A3-A90E-79D1A77A5C17@.microsoft.com...
>I have missed your earlier post. As far as your assumptions, I am with
>Bruce.
> Infact its not like they are not supported, people have not come across,
> like
> this, that's why no one replied or like me, have missed the post.
> Anyways, so giving in query parameters is good, answering your post.
> It s something to do with your data type and your single and double quote.
> ie you are converting to string and giving single quote in the expression
> window.
> How to find out is sometime you need to give the wrong input to find out
> the
> way to give the right input. Try diff. options give integer as input, give
> it
> in double quotes or give a blank input. see what happens.
> Let me know whether it works.
> Amarnath, MCTS.
>
> "Bruce L-C [MVP]" wrote:
>> Wrong assumption.
>> People answer on a volunteer basis. You post might or might not be seen.
>> Take my case. I don't use filters because I think they are mostly a bad
>> idea
>> to do. Filters are used after the data is brought over to the report. I
>> use
>> query parameters. Query parameters do the same thing but it applies the
>> filter at the database, not at the report.
>> However, just because I don't use it does not means that filters don't
>> work.
>> I have not seen any indications that they don't work. If you didn't get a
>> response you could try posting again. Or try the web forums. The web
>> forums
>> have a lot more eyeballs.
>> If you have MSDN you might check out managed newsgroups. Managed
>> newsgroups
>> are done by registering a fake email address with microsoft. That email
>> address gets monitored in the newsgroup and you are guaranteed a response
>> from a MS employee within two business days.
>> One last thing, have you tried query parameters? That really is the way
>> to
>> go in most cases.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "jereviscious" <here@.there.com> wrote in message
>> news:ecjpzh%23bHHA.5044@.TK2MSFTNGP05.phx.gbl...
>> > Its pretty apparent to me that due to the lack of response on this
>> > issue
>> > that dataset and table filters aren't well supported on this version of
>> > SSRS.. I will take another approach. I hope this post will save someone
>> > else some time in the future.. Thanks
>> > "jereviscious" <here@.there.com> wrote in message
>> > news:eJTkrZ7bHHA.4000@.TK2MSFTNGP02.phx.gbl...
>> >> Hello all..
>> >>
>> >> I've put this question out before, but I still haven't figured out a
>> >> solution..
>> >>
>> >> When I apply this filter at the dataset or table level to get rid of
>> >> commission code 100 it blanks out the report
>> >>
>> >> Expression: =Cstr(Fields!CommissionCode.Value)
>> >> Operator: =>> >> Value: '100'
>> >>
>> >> I did discover that when I run this under the data tab to look at the
>> >> raw
>> >> data, the filter works! But the report still comes up blank when I
>> >> preview it..
>> >>
>> >> Help!!
>> >>
>> >> Thanks.
>> >>
>> >>
>> >>
>> >>
>> >
>> >
>>