A custom field's SQL, checking JT_EXECUTION_INSTANCE_UIV.TASK_LEADER_DB (a flag indicating the task leader/lead engineer) with WHERE TASK_LEADER_DB = TRUE, runs without error but returns the wrong resource — it seems to just return whichever resource was assigned first, not specifically the task leader.

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Put the TRUE value in single quotes — WHERE TASK_LEADER_DB = 'TRUE' rather than the bare, unquoted TRUE — since _DB-suffixed flag columns like this one are typically VARCHAR2 columns storing the literal string 'TRUE'/'FALSE', not a native Oracle BOOLEAN type. Comparing against the unquoted TRUE keyword can silently fail to filter as intended (effectively matching every row rather than specifically the task-leader row), which is why the query was returning the wrong resource despite not throwing an error.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions