Requisition source with extra fields breaks requisition

Description

When building my select statement for a JDBC sourced requisition, I had an extra field that did not map to any field PRIS was expecting.  This caused the entire requisition to be generated without any nodes.  I would expect PRIS to just skip that field and still build the rest of the requisition.

This doesn't happen with XLS sources as that is able to ignore extra columns.

Attachments

4

Lucidchart Diagrams

Activity

Show:
Cannot Reproduce

Details

Assignee

Reporter

Components

Priority

PagerDuty

Created June 22, 2018 at 5:27 PM
Updated April 8, 2021 at 9:00 PM
Resolved April 8, 2021 at 9:00 PM
Loading...