Web client report template errors when using sources with virtual fields
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
High
|
Unassigned | ||
2.12 |
Fix Released
|
High
|
Unassigned | ||
3.0 |
Fix Released
|
High
|
Unassigned |
Bug Description
Evergreen 3.0
Web client (but not XUL client)
Certain types of report templates created with the new web client template editor generate errors when running a report. However, an identical template created with the XUL interface does not cause errors. The problem seems to be related to how virtual fields are used to generate the SQL.
For example, consider this report template:
Source: Bibliographic Record
Fields:
- Bibliographic Record: Record ID
- Bibliographic Record -> Simple Record Extracts: Author (normalized)
- Bibliographic Record -> Simple Record Extracts: Title (normalized)
Create this same template using both the new web client template editor and the XUL template editor. Running a report from the XUL template succeeds. However, running a report from the web client template results in an error displayed in the "outputs" table row:
DBD::Pg::st execute failed: ERROR: column d94d9ed7d30666e
Changed in evergreen: | |
assignee: | nobody → Galen Charlton (gmc) |
Changed in evergreen: | |
assignee: | nobody → Kathy Lussier (klussier) |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
Confirmed on 3.0 web client