Reports fail with timestamp filter transforms other than "date"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen Quick Reports |
Confirmed
|
Low
|
Unassigned |
Bug Description
If you are running a quick report that has a base filter on a timestamp field, like:
Classic Item List -> Copy ID -> Circulations -> Checkout Date/Time
Transform: Year
It will fail to process the report with an error "Invalid Parameters: Missing P1".
Adding in the "year_trunc" transform to http://
So that it reads:
if ($lowerTransform == 'date' | $lowerTransform == 'year_trunc')
instead of:
if ($lowerTransform == 'date')
allows the report to head to the scheduler for processing (although this isn't a fix). There, the report will fail because the date passed over to the SQL is in the format YYYY-MM-DD when it needs to be YYYY.
SQL from the same report run on the two different interfaces:
Failed Quick Report SQL: http://
Completed Evergreen Reports Module SQL: http://
description: | updated |
description: | updated |
Changed in egquickreports: | |
status: | New → Confirmed |
Changed in egquickreports: | |
importance: | Undecided → High |
Changed in egquickreports: | |
importance: | High → Medium |
Changed in egquickreports: | |
importance: | Medium → Low |