Skip to main content
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
  • Use Case Gallery
Loading…
   
All PostsDiscussionsBlogsIdeasQuestions
Leaderboards
  •                    
  •                    
  •                    
  •                    
  •                    
  •                    
  •                    
  •                    
  •                    
  •                    
  •                    
  •                    
  •                    
  •                    
  •                    
Discussions
  • TagsChevronRightIcon
2022
  • Blog banner
    • News & UpdatesChevronRightIcon

    The New Notebooks from Sisense

                                             

    This blog was created by @vidisha_v , Senior Product Marketing Manager at Sisense, and @Pat Bhatt , Director of Product Management at Sisense   Introduction One of the most exciting advances in the Analytics space is the introduction of Notebooks by Sisense. Notebooks allow analysts to type SQL and generate charts from the outputs for rapid and agile exploration. SQL data may be ingested by Python or R code blocks to process the data for any number of procedural applications – from simple business applications to advanced feature engineering or to Machine Learning (ML) and Artificial Intelligence (AI)! This article will explain the basic features of Notebooks, and contextualize how Notebooks operate in the larger Sisense platform.  Notebooks Notebooks allow you to directly connect to several supported data sources. Popular repositories include Redshift, Snowflake, My SQL, Big Query, among several others. Once a connection is established, the repository may be queried with that repository’s native SQL. Analysts can then open multiple SQL blocks and run multiple queries for any form of data orchestration. This flexibility with processing and combining data using SQL also extends to Python/R. For example, multiple Python (and very soon R) blocks may be opened for processing the outputs from SQL, allowing the analyst to perform complex and advanced ad-hoc analysis and build powerful decision-making applications for business users. Each SQL block references previous SQL blocks for sub-querying, joining, or performing other forms of processing. Likewise, each Python block can reference previous Python blocks and any previous SQL blocks. Notebooks also level up data visualizations. With notebooks, analysts can create multiple/side-by-side charts from any part of a query within a single Notebook for easy comparison, using chart types such as a bar or pie chart. With this flexibility to visualize data, analysts now have the tools to create effective and compelling data stories. Capabilities of Sisense Notebooks designed to empower analysts to solve important business decision problems include: Folders. Notebooks may be organized into separate folders and sub-folders. This allows analysts to keep track of various business problems and implementations in a manner that best suits their preferences and workflows.  Sharing . Notebooks may be shared with or without the ability for the recipient to be able to view the SQL and Python code for easy collaboration. Including SQL and/or Python code enables analysts to share their work with other fellow analysts for a second opinion. On the other hand, sharing Notebooks without the code gives analysts the option to share data with business users. Cloud Integration . Notebooks allow cloud resources to be accessed through Python. For instance, AWS Lambda functions may be called, or documents on S3 directly opened and processed. The ability to use libraries such as boto3 opens the door to significant versatility with Python.  Machine Learning and AI . Python opens the door to implementing, training, and deploying machine learning models. Notebooks support libraries such as scikit-learn, Keras, Theano, among others. Furthermore, additional libraries may be installed on a per-session basis using the pip install commands, providing flexibility to do more advanced analytics beyond the standard packages. Models may be trained and stored in cloud storage such as S3 for use and application with new data at the time of need.  Understanding Sisense Models While Notebooks is a code-first and code-only solution, it does not require the analyst to first prepare dimensional models prior to using Notebooks. In fact, Notebooks allow the analyst to directly connect to data sources and to use those results for further processing. Notebooks operate independently of the dimensional modeling workflows. In a future release, charts generated in Notebooks will have the ability to be published to dashboards. Stay tuned!  However, there are significant advantages to creating dimensional models and utilizing those models for dashboarding. Currently, there are two types of models supported by Sisense; the live model and second, the ElastiCube model. Live models are “hot” materialized views. Essentially, live models are a view to a desired data source and a set of data tables, either in a transactional repository such as a SQL Server, or any cloud data warehouse, such as Redshift. Dashboards and charts may be designed using the live model. However, whenever data is retrieved, it is retrieved straight from the model repository and the data is not stored anywhere within Sisense. The biggest advantage of using live models is that any SQL code that will likely be used repeatedly, may be materialized and charts developed on those views. For small datasets or cloud data warehouses, performance can be high. However, on the flip side, one disadvantage of using live models is performance degradation if the data source is slow, like in a traditional data warehouse, or if the volume of data is very large. The second model, or ElastiCube, overcomes the performance issues of live models. Unlike the live model, the ElastiCube allows arbitrary data sources to be materialized within a proprietary Sisense cache for in-memory query processing. All subsequent dashboards and charts refer to this internal data cache instead of the origin database, increasing performance. The advantage of the ElastiCube is that it also features periodic refreshes of the materialized data. If for example, an analyst starts work every morning at 9:00 am, the data may be refreshed for them by 7:00 am so that the data is as recent as it can be. The analyst also has the option to schedule the ElastiCube to refresh as often as is required by the business. Please note, in cases where the data must be in real-time, Sisense’s Live Model would be the preferable option.  Build to Destination A game-changing capability being launched by Sisense is Build-to-Destination (B2D). With  B2D, users can import data from multiple sources, mesh it together in a single model and materialize these complex data relationships to their cloud data warehouse of choice, such as Redshift, Snowflake, or BigQuery, in addition to the ElastiCube. Why is this important? In cases where data volumes are large, high performance is required, and the analyst does not want to spend resources on the ElastiCube, B2D can operate on the desired cloud data warehouse. Conclusion Notebooks is an exciting new feature that will transform the way that you approach analytics in Sisense! Notebooks introduce code-first analytics working alongside model-based business intelligence, enhancing your ability to scale the delivery of analytics and better collaborate with other analysts and business users. Code-first may reside as a standalone development environment without requiring the analyst to create dimensional models. By furthering your SQL analysis with Python and R, Notebooks also opens the door to advanced analytical applications, including Machine Learning and Artificial Intelligence. 

    vidisha_v
    vidisha_v
    2
             
  • Blog banner
    • News & UpdatesChevronRightIcon

    A New Way to Manage Infusion Views

                             

    As the adoption of Infusion Apps grows within an organization, Views are going to be used to address a wider swath of business problems and questions. As the number of Views increases, administration and management become increasingly important.  Today, the challenges for administering Views stem from a lack of discoverability–   A dashboard can hold multiple Views There is no indication that a widget is published as a View, nor that a dashboard holds one or more Views The widget title may not necessarily match the name of the View Dashboards can have published Views, but not be shared. Or Dashboards and their Views can be shared with different groups There is no way to conclusively say how many Views exist within an instance. Due to dashboard permissions, the visibility of Views are limited to the logged-in user.  View Management solves these challenges by: Displaying all Views in a single place, increasing discoverability, and reducing time  Streamlining the View editing process by taking the user directly to the widget Reducing time and steps to see a View’s data See All Views in One Place With one click, any user with Dashboard Designer access and higher can see all published Views that have been created within a Sisense instance (that they have privileges to see, based on dashboard sharing permissions ).   Easily Understand What’s in a View To understand what’s in a View, you first have to find it, then you have to edit it. Click on a View in View Management and see its contents columns and filters, and their state (visible or hidden).   Quick Access to Views or Models Don’t even think about having to go to another tab - we’ll do it for you! From “View Details”, click the pencil icon to navigate directly to the View, bypassing the need to locate the View through the "Analytics tab. The View will open in edit mode, ready for your changes. Interested in the underlying data? Click the model icon to navigate directly to the data model on the Data tab.   Whether you have 5 Views or 15 Views, we don’t expect you to remember where you put each one. But, you should be able to find it when you need it.  Update to L2022.10 (when available) to start managing your Views in a new way. For more details, check out our documentation . We can’t wait until you see what’s in store for Infusion Apps! Until then, Happy Infusing!

    Sisense User
    Sisense User
    0
             
  • Blog banner
    • News & UpdatesChevronRightIcon

    Add SQL Charts from Notebooks to a Dashboard

                                     

      Add SQL Charts from Notebooks to a Dashboard The work of a data analyst is in constant iteration. Analyze, discover, share. Wash, rinse, and repeat. When it comes to sharing insights with business partners, analysts need a streamlined way to get their insights from Notebooks where analysis is completed to a place where business partners can see it.  Sisense is happy to announce added functionality that allows you to add SQL charts to a Dashboard directly from your Notebooks. This update significantly reduces the steps required to share insights and eliminates task switching between Notebooks, Dashboards, and Models while maintaining data security and data continuity.    Reducing steps through automation While Notebooks only require a data connection to query data and create charts, Dashboards require an underlying data model to be in place. This is because Dashboards are part of a self-service use case , where analysis can be done by non-technical staff or departments rather than dedicated data analysts.  The data set powering a Dashboard widget has to be part of the data model, which can be done today by manually copying and pasting SQL queries into the Model. However, this multi-step process across Notebooks, the Data Tab, and the Analytics Tab isn’t scalable.  Once you have a chart, you will choose the destination Dashboard and select the Model. After completing this step once, the system will automatically populate your last selection, reducing the need to search for the same destinations over and over again.       When you click Add, two things will happen behind the scenes: The chart code will be translated into code to make it a visible and supported widget on the Dashboard  The SQL query will be added to the Model and displayed as a new table  Go directly to the Dashboard to see the chart, begin editing the Dashboard after multiple charts, or go to the Model itself to create relationships between the new table and existing tables.  You can also use this feature to update the Model, which only adds the SQL to the Model but doesn’t create a Dashboard widget.    Eliminate task switching The automation mentioned above makes for a simpler, easier workflow. This, in turn, reduces  task switching . By reducing the number of steps from start to finish, we decrease the opportunity for distraction. Now,  (almost) everything is in a single workflow within the Notebooks tab. To share insights and charts, you no longer need to jump between three areas of the product: Notebooks, Models, and Dashboards.   Before  After Create a live Model Connect the Model to the same database as the Notebook Add a table to the Model that contains the same custom query Publish the live Model Create a Dashboard Create a widget that points to the Model Select the correct data/design options to match the widget to the Notebook chart Select query or chart Select Dashboard Select Model     Please note, you will still need to go to the Dashboard to make visual or design changes. You may also need to go to the Model to create relationships between tables.    Maintain separation between queries, visualizations, and people You shouldn’t have to worry about how changes to your Dashboard might affect your ongoing analysis and vice versa. When a chart is added to a Dashboard, it essentially creates a copy of that SQL. This means that changes to the SQL or chart design in Notebooks won’t affect that widget on the Dashboard. This also means that changes to the widget on the Dashboard have no impact on any of the data or charts in the Notebook.  While the same SQL is powering both the widget and the chart, the visualization and customization are completely independent.    You can be confident that the insights delivered to business users are only seen by those who should see them. Data Security rules are applied to tables within the Model itself. If there are existing data security rules when adding a chart to a dashboard, those rules will be respected. The widget will behave like any other Dashboard widget if security rules are applied to a table, meaning that the viewer will not be able to view that specific data if they do not have the appropriate access.    Get started with adding charts to Dashboards It’s easy to get started! Make sure Notebooks is enabled (talk to your administrator if it’s not). Create a Notebook, connect it directly to your database, and start querying. That’s it! Adding charts to Dashboards from Notebooks is a feature that addresses today’s gap in the analysis cycle - how to get the insights back to those who need them. For more information, check out our documentation and watch the demo below.  Happy Querying!         Mia Isaacson is a Senior Product Manager at Sisense, solving a variety of both customer and business-facing problems. She is based in Portland, Oregon, and enjoys traveling, scuba diving, and drinking wine with her partner, Cory, and her Great Dane, Rambo.

    Sisense User
    Sisense User
    0