chrisnutt Posted December 7, 2017 Share Posted December 7, 2017 Hi, I am experiencing an issue with reporting. I run a report each month of requests logged into IT Services. We have a couple of non-IT services so I exclude these from the monthly report. See right-hand side of the screenshot for the filter. However, I've been scratching my head as the numbers don't quite add up. Looking into the data returned I can see there are four records returned by the report that should be excluded. See left-hand side of the screenshot. I have to present this data each month to our Director, who happens to be the Director of Finance so even the smallest discrepancy will be picked at. Am I doing something wrong or is this the system? I can't see how it's the filter. The dates for the report run in the screenshot is 1 November-30 November - however, I have to split that into two as it seems it only returns a maximum of 1000 records - another bug bear! Link to comment Share on other sites More sharing options...
Ryan Posted December 7, 2017 Share Posted December 7, 2017 Hi, It looks like you are using "Value is not equal" with multiple values. I will raise this internally, but I think you should only be able to set 1 value when using this type of filter. What is happening, is it is using the first value, and creating a filter of Service Name != 'Estate Services' and ignoring the filtering of Security. If you change "Value is not equal" to "Value is not one of these" then it will create a filter Service Name is not in ('Estate Services, 'Security') which will exclude both of these Services. See if that helps, Ryan Link to comment Share on other sites More sharing options...
chrisnutt Posted December 7, 2017 Author Share Posted December 7, 2017 Thanks @Ryan That makes sense. I've updated our filter and it seems to have done the trick on the quick test report I just ran. Any ideas on timescales for when the "Value is not equal" value list will be limited to one? Thanks Chris Link to comment Share on other sites More sharing options...
Victor Posted February 5, 2018 Share Posted February 5, 2018 @chrisnutt probably you are already aware but just in case to tie this thread off, the issue was fixed in admin build 754 deployed early last month Link to comment Share on other sites More sharing options...
chrisnutt Posted February 7, 2018 Author Share Posted February 7, 2018 Thanks @Victor I did notice this the other day. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now