There is no Business Entity-level configuration band. Configuration variables — for example SHAREPOINT_SITE_ID or SHAREPOINT_LIST_ID — are declared once, on the Connected System, and every Business Entity on that system shares the same resolved values. The external-datasource schema has no configuration key at the datasource root.
Where it lives
| Layer | Location |
|---|---|
| Variable definitions | <systemKey>-system.json → configuration[] (name, value, location, required, optional portalInput) |
| Business Entity files | No configuration key — entities read the system's resolved values |
| UI | Connected System Configuration tab (?tab=configuration) |
See Configure system configuration for how to declare and set these variables.
Current limitation
Some integrations host multiple Business Entities that share connection and auth but point at different vendor resources — for example one SharePoint Connected System with separate document libraries for deals, contracts, and general documents. Today there is no per-entity override for a system-level variable such as SHAREPOINT_LIST_ID: every entity on the system resolves the same value.
If entities need different vendor resource identifiers, model the difference in the entity's own fields (for example a fixed value in fieldMappings, or a separate Connected System per resource) rather than expecting a datasource-level configuration override — that mechanism does not exist in the current schema.