Requisition source with extra fields breaks requisition
Description
Attachments
2
Lucidchart Diagrams
Activity
Show:
Cannot Reproduce
Details
Assignee
UnassignedUnassignedReporter
Mark MahacekMark MahacekComponents
Priority
Minor
Details
Details
Assignee
Unassigned
UnassignedReporter

Components
Priority
PagerDuty
PagerDuty Incident
PagerDuty
PagerDuty Incident
PagerDuty

PagerDuty Incident
Created June 22, 2018 at 5:27 PM
Updated April 8, 2021 at 9:00 PM
Resolved April 8, 2021 at 9:00 PM
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.