Iām running into an issue with the native Sage Intacct connector in Foundry:
-
Configured Connection Settings with:
- Username / Password
- Sender ID / Sender Password
- CompanyId =
ā¢ā¢ā¢
(from our sage parent account)
-
Added JDBC properties: LocationsId = 999 ā numeric ID of our test sub-company and UseLegacy = false
-
Confirmed in Postman:
- Using same creds +
<locationid>999</locationid>
in<login>
or via<sessionid>
returns full tables (APBILL, ARINVOICE, GLBATCH, etc.)
- Using same creds +
-
Driver logs in Foundry show success but no
<locationid>
in the login response, so the connector falls back to only 11 metadata views (system_tables
).
I feel the CDATA connector only injects LocationsId
after the <login>
call, so Intacct returns a top-level session with no entity scope. That means only information_schema
, sys_query
, etc. show up in Explore Source.
Would love any guidance or help from anyone who might have used the Sage Intacct connector.