We have a pix firewall and Websense filter on our internet connection. One
of the software products we use is web-based and includes SQL RS for its
reporting.
When I run one of these reports from inside the company, I get the message
that the report is being generated and the spinning green circle thingy
graphic, but the actual report never displays. If I take the exact same
computer and disconnect from the company network and connect with my Verizon
card the report runs fine. I've switched back and forth a few times and it
consistently works from outside and not from inside.
Is there some kind of push going on to get the actual report that is maybe
blocked by the firewall or Websense? I've looked at the firewall
configuration and nothing jumps out at me.
Anybody have any suggestions?Hi Daniel,
Welcome to use MSDN Managed Newsgroup Support.
From your description, my understanding of this issue is: You can see the
report from the Extranet correctly but you can not generate the report when
you are in the intranet. If I misunderstood your concern, please feel free
to point it out.
To narrow down the issue, would your provide the information to me?
1. Are you in the same domain with the Report Server when you using
the company network?
2. If you turn off the firewall, does this issue occur again?
3. You may want to check <reportserverurl> item in the following
configuration file in the Reporting Server to see details.
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\reportmanager\rswebapplicaton.config file
4. If all the above can not resolve the issue, it seems the issue is
related with configuration of your company network. I think you need to
contact your network admin to check the configuration.
Due to the complexity of this issue we might not be able to effectively
assist with this request in the newsgroups. If the issue could not be
solved efficiently in the newsgroup, I would like to suggest that you
contact Microsoft Product Support Services via telephone so that a
dedicated Support Professional can assist with this request. Please be
advised that contacting phone support will be a charged call. However, if
you are simply requesting a hotfix be sent to you and no other support then
charges are usually refunded or waived.
To obtain the phone numbers for specific technology request please take a
look at the web site listed below.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
If you are outside the US please see http://support.microsoft.com
for regional support phone numbers.
Thank you for your patience and understanding.
Sincerely yours,
Wei Lu
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Thanks for your help.
It's not my reporting server - it is from a software vendor. It is
obviously something on our network, but I don't even know where to begin
looking. I'm hoping somebody has had problems with running a RS report on a
server outside a network and could provide some insight like "yes, you have
to open port such-and-such." I've had a previous occasion (with Polycom
videoconferencing) where it turned out the pix is particularly picky about
certain kinds of traffic.
To answer your specific questions.
1. I'm not in the same domain in either case.
2. That would mean bypassing the entire corporate firewall and reconfiguring
the physical connections to the internet. We're not at that point yet.
3. Not relevant. See #1.
"Wei Lu" <t-weilu@.online.microsoft.com> wrote in message
news:Ri38H0QOGHA.768@.TK2MSFTNGXA01.phx.gbl...
> Hi Daniel,
> Welcome to use MSDN Managed Newsgroup Support.
> From your description, my understanding of this issue is: You can see the
> report from the Extranet correctly but you can not generate the report
> when
> you are in the intranet. If I misunderstood your concern, please feel free
> to point it out.
> To narrow down the issue, would your provide the information to me?
> 1. Are you in the same domain with the Report Server when you using
> the company network?
> 2. If you turn off the firewall, does this issue occur again?
> 3. You may want to check <reportserverurl> item in the following
> configuration file in the Reporting Server to see details.
> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\reportmanager\rswebapplicaton.config file
> 4. If all the above can not resolve the issue, it seems the issue is
> related with configuration of your company network. I think you need to
> contact your network admin to check the configuration.
> Due to the complexity of this issue we might not be able to effectively
> assist with this request in the newsgroups. If the issue could not be
> solved efficiently in the newsgroup, I would like to suggest that you
> contact Microsoft Product Support Services via telephone so that a
> dedicated Support Professional can assist with this request. Please be
> advised that contacting phone support will be a charged call. However, if
> you are simply requesting a hotfix be sent to you and no other support
> then
> charges are usually refunded or waived.
>
> To obtain the phone numbers for specific technology request please take a
> look at the web site listed below.
> http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
>
> If you are outside the US please see http://support.microsoft.com
> for regional support phone numbers.
> Thank you for your patience and understanding.
> Sincerely yours,
> Wei Lu
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> =====================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi Daniel,
Thanks for the update.
Apparently it is not server side issue at all. I think you'd better contact
Cisco since the issue is caused by their firewall and they could provide
more information about the configuration of your firewall. You may need
capture packets on firewall side and compare to the packets without
firewall.
Thank you for the understanding.
Sincerely yours,
Wei Lu
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.sql
Showing posts with label filter. Show all posts
Showing posts with label filter. Show all posts
Wednesday, March 21, 2012
Tuesday, March 20, 2012
Problems with Measure by DistinctCount
I have this problem:
Dimensions: Year, Month
Measure: CustomerCount (int)
I set CustomerCount.AggregateFunction=DistinctCount
When I filter Month Dimension I have a problem on agregate total.
For example:
Year Month
gen feb total
2001 100 103 err.
2002 230 234 err.
2003 300 280 err.
total 400 398 err.
This problem happens when I filter but If I remove filter I have correctly
totals.
What can I do?Here, total is not just sum of Jan and Feb.
I understand that current version does not support distinct count against
sube cube.
Ohjoo Kwon
"Dario Concilio" <DarioConcilio@.discussions.microsoft.com> wrote in message
news:39860F22-7B0A-4D7A-B828-DCE427C4A473@.microsoft.com...
> I have this problem:
> Dimensions: Year, Month
> Measure: CustomerCount (int)
> I set CustomerCount.AggregateFunction=DistinctCount
> When I filter Month Dimension I have a problem on agregate total.
> For example:
> Year Month
> gen feb total
> 2001 100 103 err.
> 2002 230 234 err.
> 2003 300 280 err.
> total 400 398 err.
> This problem happens when I filter but If I remove filter I have correctly
> totals.
> What can I do?|||to solve aggregation errors using a DCount measure, you have to use dynamic
distinct count measure.
Like
count(crossjoin(<my dimension>.<my level>.members, measures.<My measure to
count> ), excludeempty)
"Dario Concilio" <DarioConcilio@.discussions.microsoft.com> wrote in message
news:39860F22-7B0A-4D7A-B828-DCE427C4A473@.microsoft.com...
>I have this problem:
> Dimensions: Year, Month
> Measure: CustomerCount (int)
> I set CustomerCount.AggregateFunction=DistinctCount
> When I filter Month Dimension I have a problem on agregate total.
> For example:
> Year Month
> gen feb total
> 2001 100 103 err.
> 2002 230 234 err.
> 2003 300 280 err.
> total 400 398 err.
> This problem happens when I filter but If I remove filter I have correctly
> totals.
> What can I do?
Dimensions: Year, Month
Measure: CustomerCount (int)
I set CustomerCount.AggregateFunction=DistinctCount
When I filter Month Dimension I have a problem on agregate total.
For example:
Year Month
gen feb total
2001 100 103 err.
2002 230 234 err.
2003 300 280 err.
total 400 398 err.
This problem happens when I filter but If I remove filter I have correctly
totals.
What can I do?Here, total is not just sum of Jan and Feb.
I understand that current version does not support distinct count against
sube cube.
Ohjoo Kwon
"Dario Concilio" <DarioConcilio@.discussions.microsoft.com> wrote in message
news:39860F22-7B0A-4D7A-B828-DCE427C4A473@.microsoft.com...
> I have this problem:
> Dimensions: Year, Month
> Measure: CustomerCount (int)
> I set CustomerCount.AggregateFunction=DistinctCount
> When I filter Month Dimension I have a problem on agregate total.
> For example:
> Year Month
> gen feb total
> 2001 100 103 err.
> 2002 230 234 err.
> 2003 300 280 err.
> total 400 398 err.
> This problem happens when I filter but If I remove filter I have correctly
> totals.
> What can I do?|||to solve aggregation errors using a DCount measure, you have to use dynamic
distinct count measure.
Like
count(crossjoin(<my dimension>.<my level>.members, measures.<My measure to
count> ), excludeempty)
"Dario Concilio" <DarioConcilio@.discussions.microsoft.com> wrote in message
news:39860F22-7B0A-4D7A-B828-DCE427C4A473@.microsoft.com...
>I have this problem:
> Dimensions: Year, Month
> Measure: CustomerCount (int)
> I set CustomerCount.AggregateFunction=DistinctCount
> When I filter Month Dimension I have a problem on agregate total.
> For example:
> Year Month
> gen feb total
> 2001 100 103 err.
> 2002 230 234 err.
> 2003 300 280 err.
> total 400 398 err.
> This problem happens when I filter but If I remove filter I have correctly
> totals.
> What can I do?
Wednesday, March 7, 2012
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.
>> >>
>> >>
>> >>
>> >>
>> >
>> >
>>
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.
>> >>
>> >>
>> >>
>> >>
>> >
>> >
>>
Subscribe to:
Posts (Atom)