Semantic model data source connection bindings should be source controlled.
A semantic model can contain multiple data source references, each of which can be mapped to a separate Fabric data connection. Currently, the semantic model definition is source controlled, but these data source → connection bindings are not.
After a Git sync or deployment, the connections therefore have to be mapped to the semantic model again, either manually through Semantic model settings → Gateway and cloud connections → Maps to, or programmatically using the connection binding API.
The connection bindings should instead be included in the source-controlled semantic model definition and automatically applied during Git sync and deployment.
Preferably, the connection ID should also support Variable Library variables. Since the connection is identified by a GUID, the binding could accept a String/GUID Variable Library value, allowing the same semantic model definition to be used across environments with different connections.
The Variable Library would then provide the appropriate connection IDs for each environment.
This would eliminate the need for separate manual or programmatic connection-binding steps after Git synchronization or deployment.
