Auditing & Sage300 ORGID (1 reply)
Roger, most connectors support the ability to map a value to a field to specify the Company/Instance/Site of the transaction.
This allows you to target multiple Companies/Instances/Sites without having to resort to using a branch and filter type design. You just have a single process flow and map this to the relevant field which controls this.
Sage300 is no different! The System Connector ID field allows you to specify which connector, ultimately mapping to the Sage300 company.
This field can then be marked as a Log Key, which will then show up in the Audit Report.
When I attempt a transaction using the Sage 300 connector is there a way to retrieve the OrgID so that it can be used in the audit stream. I am working on an integration that does the same set of operations for several companies and I trying to figure out a way to alert the user what company the error occurred in.