Skip to content

History Log entries for changes to a Customer's Notes (stored via FIN_NOTE_TEXT_TAB) show the change details correctly, but don't include which specific Customer/Identity the note belongs to, making the log hard to use for reporting — how do you resolve the NOTE_ID key in a history log entry back to the actual Customer it belongs to?

Answer

Enable History Log specifically on FIN_NOTE_TEXT_TAB (rather than trying to log IDENTITY_NOTE_TAB directly, which doesn't work reliably for this). Then, when querying history_log_tab/history_log_attribute_tab for that table, reverse-resolve each entry's logged NOTE_ID (extracted via Client_SYS.Get_Key_Reference_Value) back to a Customer identity using Identity_Note_API.Get_Note_Id, called against each candidate customer's own composite key (company, identity, and party type) until it returns a matching NOTE_ID — effectively working backward from the note ID to find which customer it was generated for. This reliably covers Insert and Update-type history log entries; Delete-type entries need separate handling since the underlying note reference may no longer resolve the same way.

← Browse Security and access questions