The ar.person_id column was set to
NULL when sales invoices were added to LedgerSMB
programmatically. Turns out stored procedure (function)
person__get_my_entity_id() was selecting against the users table
based on the value of SESSION_USER. But, when connected
Yeah! I finally figured out why a
programmatically generated invoice sometimes display as an AR
Transaction and sometimes as a Sales Invoice. It appears to be
the setting (value) of the invoice column on the ar table (i.e.,
ar.invoice). If set to TRUE, displays
