Oleksandr_K
Sisense Employee
Joined 4 years ago
User Profile
User Widgets
Contributions
Re: 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!Re: Sisense Fusion git limits
Thank you for reaching out! In Sisense Fusion, there is no explicit 500MB size limit on Git repositories at the file system level. However, extremely large repositories can introduce performance challenges in terms of how the application interacts and synchronizes with Git. Additionally, Fusion’s Git integration currently supports only dashboards and data model metadata—other asset types aren’t tracked or processed, even if they’re manually added to the repository. I’d be happy to learn more about your specific use case to understand why your repository needs to be this large and discuss any potential workarounds or best practices to optimize performance.Re: Folder and Dashboard Ownership for Multiple Users
Thanks for raising this - your feedback is important to us. Current folder implementation is indeed based on a single user ownership that prevents other users from adding or removing dashboards from it. We will evaluate this feature request in order to prioritize it in the roadmap.
