Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Issues

Select view

Select search mode

 
7 of 7

Requisition source with extra fields breaks requisition

Cannot Reproduce

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.

Lucidchart Diagrams

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

Activity

Show:

Mark MahacekApril 8, 2021 at 9:00 PM

Closing as I am no longer able to replicate with a clean 1.3.0 or 1.3.1 PRIS install.

Mark MahacekApril 8, 2021 at 5:00 PM

Adding note that this issue can be triggered when trying to add metadata fields.  While the documentation states that is supported with a JDBC source, adding them to the SELECT statement will cause the requisition to break and be rendered without any nodes just like if you include a field name that doesn't match any of the expected field names.