The /v2/officers/... integration changes the endpoint, but the processing logic for officerData still filters by item.Officer !== "" (see the filtering immediately after the fetch). If the v2 response uses the new contactFullName/title/userID fields you render later, this filter will likely drop all records and the officer section will appear empty. Update the filtering to align with the v2 schema (or remove it if unnecessary).
Originally posted by @Copilot in #291 (comment)
AB#44471
The
/v2/officers/...integration changes the endpoint, but the processing logic forofficerDatastill filters byitem.Officer !== ""(see the filtering immediately after the fetch). If the v2 response uses the newcontactFullName/title/userIDfields you render later, this filter will likely drop all records and the officer section will appear empty. Update the filtering to align with the v2 schema (or remove it if unnecessary).Originally posted by @Copilot in #291 (comment)
AB#44471