Sisense Community logo
    • Community Feedback
    • Chapters
    • Events
    • Forums
      • Help and How To
      • Product Feedback Forum
      • Strategy & Use Cases
    • Blogs
    • KB Docs
      • KB Docs
      • Add-Ons & Plug-Ins
      • APIs
      • Best Practices
      • Blox
      • CDT
      • Cloud Managed Service
      • Data Models
      • Data Sources
      • Embedding Analytics
      • How-Tos & FAQs
      • Onboarding
      • PySisense
      • Security
      • Sisense Administration
      • Sisense Intelligence & AI
      • Troubleshooting
      • Widget & Dashboard Scripts
    • Support
    • Learning
      • Sisense Academy: Free Courses and Certifications
      • Official Developer Documentation
      • Official Product Documentation
      • Official Sisense Youtube Channel
      • Sisense Compose SDK Playground
      • Official Sisense Discord
    • Use Case Gallery
    Discussions
    •                    
    •                    
    •                    
    •                    
    •                    
    •                    
    •                    
    •                    
    •                    
    •                    
    •                    
    •                    
    •                    
    •                    
    •                    
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   
    Discussions
    • TagsChevronRightIcon
    Releases
      • TroubleshootingChevronRightIcon

      Client-server version difference exceeds supported skew (+/-1)

                                               

      Version d ifference between the client (1.xx) and the server (1.xx) exceeds the supported minor version skew of +/-1 Sometimes during the upgrade process, you can see such a warning: sisense@node1:~/sisense-L2024.3.0.501$ ./sisense.sh single_config.yaml [2025-02-24 10:49:56] Preparing System ... [2025-02-24 10:49:56] Linux user: sisense [2025-02-24 10:49:56] Validating Sudo permissions for user sisense ... [2025-02-24 10:49:56] User sisense has sufficient sudo permissions [2025-02-24 10:49:56] Detecting Host OS ... [2025-02-24 10:49:56] OS: Ubuntu, Version: 22.04 [2025-02-24 10:49:56] Validating OS and its version [2025-02-24 10:49:57] Can proceed with RKE process ... [2025-02-24 10:49:57] Validating that namespace name is all lower case ... [2025-02-24 10:49:57] detected lock on dpkg, releasing it Enter the password for user sisense and press [ENTER]: Using password for Sisense Installation ... [2025-02-24 10:50:02] Verifying Python packages exist ... [2025-02-24 10:50:06] Installing required pip libraries [2025-02-24 10:50:09] Ensuring sisense main directory /opt/sisense exist [2025-02-24 10:50:09] Fixing /opt/sisense ownership to all files WARNING: version difference between client (1.29) and server (1.26) exceeds the supported minor version skew of +/-1 WARNING: version difference between client (1.29) and server (1.26) exceeds the supported minor version skew of +/-1 This means that kubectl version installed on the server differs by more than 1  version from Kubernetes, which is not officially supported. To fix this issue, you’ll need to set the following value in the configuration yaml file: update_k8s_version: true And run the update as usual

      Andriy Soroka
      Andriy SorokaPosted 1 year ago
      0
               
      • Embedding AnalyticsChevronRightIcon

      Sisense Compose SDK

                                                                               

      Sisense Compose SDK The Future is Composable In the fast-paced world of data-driven applications, developers are constantly seeking innovative ways to create customized data products that seamlessly integrate into their projects. Sisense has stepped up to the challenge with its groundbreaking Compose SDK, which has fundamentally changed the game. This powerful toolkit empowers developers to harness the full potential of Sisense components, enabling them to craft data products that are not only highly customized but also perfectly tailored to their applications.  Traditionally, the embedded analytics market constrained developers within the boundaries of their chosen tools. However, Compose SDK breaks free from this limitation. Instead of merely embedding a third-party tool, developers now have the freedom to build bespoke data products by selecting from a rich library of Sisense components and seamlessly integrating them with a wide range of other tools within their Integrated Development Environment (IDE).  A Practical Example  In the world of UI design, consistency is key. Imagine your company has chosen the Material UI framework to style your application. It provides a sleek and uniform look, but now you need to populate Material UI tables with dynamic data from Sisense. Enter Compose SDK. With it, you can seamlessly merge Material UI's aesthetics with Sisense's analytical power. Start with Material UI tables that align perfectly with your design guidelines. Then, using the Compose SDK's ExecuteQuery component, you effortlessly infuse these tables with real-time data from Sisense.         The result? Stunning, data-rich components that not only adhere to your design principles but also deliver invaluable insights. Your users get the best of both worlds - visually appealing design and powerful data. Get Started with Compose SDK  Excited to explore the potential of the Compose SDK? Good news - it's currently in Beta and available to all Sisense partners, ready for you to harness its capabilities today. To embark on your journey, you can begin by cloning the example repository from GitHub listed below. To install the necessary packages for your sample application, follow the user-friendly Compose SDK Quickstart Guide. Keep in mind that, for the time being, these packages are accessible on GitHub, requiring a personal access token for access.  In conclusion, Sisense's Compose SDK represents a revolutionary leap forward in the world of data product development. It empowers developers to break free from the constraints of traditional embedded analytics and build highly customized, seamlessly integrated data products. With the Compose SDK, the possibilities are limitless, and the power to transform your  applications lies at your fingertips. So, why wait? Dive into the world of Compose SDK, unleash your creativity, and revolutionize your data products today. Your applications will thank you for it!  Credit : Sample Application initially developed by Sisense Senior Director of Field Engineering: Tom Linton  Compose SDK -- Material UI Example   Sisense Quick Start Guide   Sisense Github

      Sisense User
      Sisense UserPosted 2 years ago • Last reply 1 year ago
      1
               
      • How-Tos & FAQsChevronRightIcon

      Migrating Assets Across Environments Leveraging GIT

                       

      Migrating Assets Across Environments Leveraging GIT Sisense released its Git Integration for Linux version 2022.10. With the GIT GUI in Sisense, you can do a lot of exciting things like version control or integrate into CI/CD pipelines. I went ahead and put together a quick demo on how a developer can leverage the Sisense Git Integration to migrate assets from their Dev Environment to the Prod Environment and see those changes reflected in the target application that assets are embedded in.  In this video we cover,  1. How to create a Git project in Sisense  2. Add Assets to a project  3. Connect to a remote Git Repo.  4. Push Assets from Dev to a remote Github Repo.  5. Pull Assets from Git Repo into the prod server.  6. Checkout and Commit changes/revert.  7. See Changes reflected in the application Sisense is embedded into.    For any additional questions about Enabling Git in your environment, or other capabilities, please see the  Introduction to Sisense Git Documentation.       Check out this related content:  Academy Documentation

      Sisense User
      Sisense UserPosted 1 year ago
      0
               
      • TroubleshootingChevronRightIcon

      [Custom SMTP Email Server] - Outlook365 Error - 432 4.3.2 Concurrent connections limit exceeded.

                       

      [Custom SMTP Email Server] - Outlook365 Error - 432 4.3.2 Concurrent connections limit exceeded. Note:   As of 2024, if you're using Outlook365 as your SMTP server, you might encounter the following error when sending batch emails: ERROR: Message failed: 432 4.3.2 Concurrent connections limit exceeded. Visit   https://aka.ms/concurrent_sending   for more information This error indicates that too many simultaneous connections have been opened, exceeding the server's limit of three concurrent connections. In early 2024, Microsoft introduced changes to message store and throttling for concurrent connections. Under the new limit, only three concurrent connections are allowed to send email messages simultaneously. If an application attempts to send more than three messages at once using multiple connections, each connection will receive the following error message: 432 4.3.2 STOREDRV.ClientSubmit; sender thread limit exceeded Additional throttling limits for the SMTP Authentication protocol include: 30 messages per minute Recipient rate limit of 10,000 recipients per day Exceeding these limits causes: Per minute limit:   Email delivery delays. Any excess in message submission will be throttled and carried over to the following minutes. Per day limit:   Error message   554 5.2.0 STOREDRV.Submission.Exception   These changes necessitate adjustments to how batch emails are sent to avoid triggering these errors and ensure smooth email delivery. Resources:  https://learn.microsoft.com/en-us/exchange/troubleshoot/send-emails/smtp-submission-improvements Check out this related content:  Sisense Documentation 

      Vladyslav Hontar
      Vladyslav HontarPosted 1 year ago
      0