Service Manager Reporting Issues

[Gareth Cantrell]

I came across a couple of issues today when creating a new report in Service Manager:

1. I am unable to add or change the alias of a table
2. Filtering on timestamps is not working

I have attached the report definition - no matter what I try, it will not filter on the timestamps.

I even tried adding in the "Requests -> Date Logged" column and it will not filter on that either.

de-prioritised-incidents.report.txt

[Ryan]

Hi @Gareth Cantrell,

I can see an issue where after you Upload a report definition file, the tables are not correctly initialised, and it does not allow you to specify a table alias. Is this what you are experiencing? If not, how are you replicating this issue? If so, after you save the new definition, and then navigate away and back into the report, does it now work for you?

As for the timestamp filtering. It appears to be working as expected for me, with all results in 2024 being returned (start of last quarter - currently being the 1st of January). Do you get results with no date filtering - just the priority filtering?

Thanks,

Ryan

[Gareth Cantrell]

@Ryan I created the report in the UI, not via the definition file. I downloaded the definition file solely to attach to this post.

I get the same data irrespective of the timestamp filter - i.e. if I remove it completely, I get exactly the same number of records returned, basically everything since the beginning of time (or July 2023 in our case)

 

 

[Ryan]

Hi @Gareth Cantrell

Looking at the import, I think you may be getting more results because of the filtering.

Your criteria:
(OldPriority=P1 && NewPriority IN (P2, P3, P4, P5))
OR
(OldPriority=P2 && NewPriority IN (P3, P4, P5)) AND log.timestamp from start of last quarter.

So, the timestamp filtering is only being applied to the second priority filter. I think you need another set of brackets around the priority filtering.

((OldPriority=P1 && NewPriority IN (P2, P3, P4, P5)) OR (OldPriority=P2 && NewPriority IN (P3, P4, P5)))
AND
log.timestamp from start of last quarter.

I will keep trying to investigate how the Alias is not able to be set. Can I just check, if you exit the report, and go back in, are you able to set aliases?

Thanks,

Ryan

[Gareth Cantrell]

I'm more used to seeing brackets in an editor than in a UI builder. Adding the extra brackets did the trick, thanks!

I am unable to set the alias even after logging out and clearing all my caches and doing a hard refresh from developer mode.