Dashboards as Code With Sisense Git Integration

Hi chaobibtc, thanks so much for sharing your experience! 🙌 It’s great to see how Sisense Git Integration is helping streamline your version control and asset promotion workflows. 🔥

I’d like to briefly comment on the following point you raised:

"If Elasticubes are used, ensure data connection names are consistent across environments. Mismatches can cause sync or deployment failures."

Since Git integration is based on the file system, we rely on the OID (object ID) as the unique identifier for assets, not the asset names, which can be duplicated. This means that dashboard, data model, and connection OIDs remain consistent when promoting assets across environments.

You can check out the recommended and supported approach for working with connections in our documentation here- https://docs.sisense.com/main/SisenseLinux/data-source-connection-management.htm#GitIntegrationPromotion

Please feel free to share any additional feedback or submit feature requests directly in the community — we’re always listening!