Introduction:  Sisense supports row-level security (RLS) rules on data models, allowing administrators to control data access at a granular level per user and user group. However, in some environments, RLS rules may be applied inconsistently — data that should be restricted is sometimes exposed, particularly when toggling field visibility in a widget. This behavior is not caused by rule conflicts, but by insufficient system resources — specifically, an undersized DataContextRulesCacheSize and limited memory allocation — which cause the security rule engine to behave unpredictably. This article explains how to resolve this issue by adjusting the relevant settings in the Configuration Manager. Step-by-Step Guide:   Check the number of existing data security rules. Self-hosted environment Run the following command: kubectl -n sisense exec -it `kubectl -n sisense get pods | grep sisense-mongodb | head -1 | awk '{print $1}' ` -- mongosh prismWebDB --eval 'db.dataContext.find().count()' Sisense Cloud environment Connect to Repository from ElastiCube data model using MongoDB connector and execute query. Use the following connection settings in the MongoDB connector. Location:  Single-Node: sisense-mongodb.sisense Multi-Node: sisense-mongodb-headless.sisense Port: 27017 Default Database: prismWebDB Authentication Mechanism: No Authentication Define the following table query: SELECT  Count(*) AS NumberOfDataSecurityRegistrations FROM   "prismWebDB"."dataContext" Preview data of the query and check the returned value Check the DataContextRulesCacheSize parameter value Log in to Sisense as a user with Admin privileges. Open Configuration Manager : Admin > Server & Hardware > System Management > Configuration Click the Logo in top left five times to open the left pane, and select Query in the left pane Check the DataContextRulesCacheSize.value parameter, the default value is 1000 Update the DataContextRulesCacheSize parameter value greater than the value obtained in Step 1 Update MemoryLimit parameter value (default: 1024m) to 2G or greater value  If you want to increase the MemoryLimit parameter more than 2G, you have to update the memory limit of the query deployment, which should be greater than Memory Limit + 1G. Save the changes and restart the relevant services. Verify that data security rules are now applied consistently across all widgets. Conclusion:  Once these configuration changes are applied, the RLS rules should be enforced reliably. Increasing the DataContextRulesCacheSize ensures the system can cache a sufficient number of data context rules without dropping or misapplying them under load. Add a disclaimer for custom solutions . Disclaimer: This post outlines a potential custom workaround for a specific use case or provides instructions regarding a specific task. The solution may not work in all scenarios or Sisense versions, so we strongly recommend testing it in your environment before deployment. If you need further assistance with this, please let us know.

Hi all, We have a lot of vertical orientated tables. An example is our questionnaire table. This contains all our questionnaire-types with their questions and user-answers. We ourselves, but also our users, would like to combines these in a pivot style way, but that was not possible with the current Sisense Pivot Table. And datamodelling became to cumbersome to do this for every questionnaire (we have around 300 types). The built-in Pivot only allows aggregations at a row × column intersection. That works for numbers, but not when the value you want to show is text. Our questionnaire data stored in a "text" format is the classic case: I wanted one row per form, one column per question and the actual answer in each cell. The workarounds I found meant either mapping answers to numeric codes with javascript or reshaping the data model every time a question was added. So I built a widget plugin instead with the new ComposeSDK. Setting it up The data panel has three slots: Rows: up to 3 fields, for example form ID and location Columns: 1 field, for example question Value: a text field, used as is with no aggregation When a cell has more than one value, you choose whether to join them (with your own separator), keep the first, or keep the last. Rows and columns have a default sort order (A→Z, Z→A, or order of appearance). You can also click any header to sort by that column, including by the answers in a question column and empty cells always end up at the bottom. Wide tables were the main usability problem, so the header row and the row-field columns stay frozen when you scroll sideways. Text wrapping and the width of the row columns are both settings. The row limit counts table rows (forms in this example), not the records underneath. Limiting raw records would cut forms off halfway, so the widget fetches complete forms only and shows a notice when there are more than the limit. The native PDF export only captures the part of a widget you can see, so I added export buttons for the whole table: CSV, Excel (.xlsx with a frozen header) and PDF (A4 landscape, with the header repeated on every page and extra pages sideways for very wide tables). Dashboard filters apply to it like any other widget. How it's built It's a Compose SDK widget plugin, created with the Plugin DevX toolchain ( npx @sisense/sdk-cli create-plugin , React and TypeScript) and uploaded to Sisense as a plugin. I tested it on Sisense 2026.3.2, Linux. The data comes from useExecuteQuery with ungroup: true , and the pivoting happens in the browser. For the row limit, the widget first counts the distinct column values, then fetches just enough rows, sorted by the row fields, to fill the requested number of complete table rows. Four things I ran into while building it If you build plugins yourself, these may save you some time. At runtime the plugin doesn't use the SDK version in your package.json . It runs on the host's copy ( window["@sisense/sdk-ui"] ), so check that every API you call exists in the version your instance ships. Sisense's own CSS also styles MUI class names. In my case it turned the design-panel labels white on a light background. Explicit colors on a wrapper with more specific selectors fixed it, plus !important for the labels. Dropdown menus render outside the widget, so they need their own styling via slotProps . Adding PDF export with jsPDF made the bundle balloon. The Sisense build is a single IIFE file, so jsPDF's optional dependencies (html2canvas, canvg) got inlined even though the plugin never uses them. A scoped npm overrides entry that points them at tiny local stubs brought the bundle back to about 860 KB. If your widget measures its container, for a canvas or a chart, attach the ResizeObserver through a callback ref. The widget renders its loading state first, so a useEffect(..., []) on a regular ref never sees the element and the size stays at zero. Getting it Download it here Limitations The pivoting runs in the browser, so it's meant for tens of thousands of underlying rows, not millions. With bigger sets, use filters or the row limit. There's one column field for now, with no nested column headers, and clicking a cell doesn't cross-filter other widgets yet. How do you handle text values in pivots today: a data-model change, a script on the native pivot, or something else? I'd also like to know whether there's a cleaner approach I missed and which feature you'd want added first. :) Hamza

Introduction A common request is to overlay an secondary line (e.g. average reference series) on a line chart and style it differently from the main series — for example, make it dashed , thinner , and without value labels so it reads as a subtle reference rather than a primary trend. The challenge: the widget Design panel applies line styling (line width, value labels, line type) to all series at once . There is no built-in way to format a single series independently from the panel. This article shows a short widget script that targets one series by name and formats only that series, leaving the main line untouched. Prerequisites A line chart (or line/column) widget with two or more series — e.g. your main measure plus an average measure such as avg([Weeks in CreatedDate], [# of unique UniqueNumbers]) . Edit rights on the dashboard/widget. Before Script: After Script: Steps Open the widget, then select the widget menu (three dots) → Edit Script . Paste the script below. // Format one series independently on a line chart: // dashed line, no value labels, and a slimmer line weight. // Set the string below to the EXACT title of the series to restyle. var averageSeriesName = "avg [# of unique UniqueNumbers]"; widget.on("beforeviewloaded", function (widget, args) { args.options.series.forEach(function (s) { if (s.name === averageSeriesName) { s.dashStyle = "Dash"; // dashed line s.dataLabels = { enabled: false }; // hide value labels on this series only s.lineWidth = 1; // slimmer line (higher number = thicker) } }); }); Set the averageSeriesName variable to the exact title of the series you want to restyle — copy it character-for-character from the legend or from the tooltip that appears when you hover the line (including any prefix such as avg ). This is the single most important step: if the name does not match exactly, nothing changes. Click Apply , then Save the dashboard and refresh the widget. Customization To restyle by position instead of by name, replace the if (s.name === …) test with an index check, e.g. args.options.series.forEach(function (s, i) { if (i === 1) { … } }) where 1 is the second series. To emphasize the main line instead of thinning the average, target the main series name and give it a higher lineWidth . Notes The Design panel's Line Width control (Thin / Bold / Thick) can override the script's lineWidth when the widget re-renders. If the width does not hold, set the panel width for the main line and let the script handle only the secondary series. Widget scripts are an unsupported, "as-is" customization. Test on a copy of the widget first, and re-validate after Sisense version upgrades. Result The main series keeps its normal styling, while the average/reference series appears as a slim, dashed line with no value labels — a clean visual reference across the chart.

Exporting a dashboard as a PDF or PNG works fine when the audience is internal, and the need is simple. But as soon as a report needs to go out to different groups, with different branding, formatted for a specific audience, that's a different use case than a general export was ever built to solve. On September 17 , we're running a live demo of Report Studio, a report design and delivery layer built inside Sisense for exactly this gap: getting data out of Sisense in a format that's actually ready for a client, an exec, or anyone who isn't going to open a dashboard. This isn't a slide deck. It's a live build, start to finish. Here's what you'll see: Building a report from scratch: widgets, text boxes, a logo, and shapes added to the canvas, then exported manually A side-by-side of a native Sisense PDF export vs. the same data in Report Studio Applying a template to the report we just built, and how much manual layout work it removes Toggling between brands live on a single report, with the recipient's brand assigned automatically based on their user or group Token substitution across text boxes, file name, email subject, and email body Export by dimension, both on demand and as part of a scheduled delivery The actual email a recipient outside your organization receives, report attached Admin-side monitoring: job history and delivery oversight at scale Register here: https://www.qbeeq.io/webinars-register Drop questions here, and we'll answer them live during the webinar!

Every widget in Sisense supports descriptions, but what about dashboards themselves? Sometimes you need to explain a dashboard's purpose or guide users on how to interact with it effectively. We solved this by adding an info icon to the top toolbar that triggers a modal with the dashboard description. Add this script at the dashboard level and update the CONFIG object at the top with your custom text. We also included a feedback email in the configuration, making it easy for users to reach out with questions or suggestions. If you'd prefer, you could split this into a separate feedback button instead of including it in the description modal. Another nice touch: you can swap the ℹ️ emoji for a different icon to match the style of Sisense's built-in widget info icons. Let me know if this is helpful or if it this feature already exists and I have missed it.  // Configuration - update these values for your dashboard const CONFIG = { feedbackEmail: 'feedback@feedback.com', description: 'You can put your additional context here.' }; $(document).ready(function() { setTimeout(function() { // Clean up any existing instances $('#dashboard-info-icon, #dashboard-info-modal').remove(); // Create info button const infoButton = $('<button id="dashboard-info-icon" title="Dashboard info">ℹ️</button>').css({ cursor: 'pointer', background: 'none', border: 'none', fontSize: '20px', padding: '5px 10px', color: '#666' }); // Add button to toolbar (after Widget button if found, otherwise append to toolbar) const widgetButton = $('button:contains("Widget")').filter(':visible').first(); if (widgetButton.length) { widgetButton.after(infoButton); } else { $('.dashboard-toolbar').append(infoButton); } // Create modal const modal = $(` <div id="dashboard-info-modal" style="display:none; position:fixed; z-index:10000; left:0; top:0; width:100%; height:100%; background:rgba(0,0,0,0.5);"> <div style="background:white; margin:15% auto; padding:30px; border-radius:8px; width:500px; max-width:90%; box-shadow:0 4px 6px rgba(0,0,0,0.1);"> <h2 style="margin-top:0; color:#333;">Dashboard Description</h2> <p style="line-height:1.6; color:#555;">${CONFIG.description}</p> <p style="line-height:1.6; color:#555; margin-top:20px;"> <strong>Feedback:</strong> <a href="mailto:${CONFIG.feedbackEmail}" style="color:#0078d4; text-decoration:none;">${CONFIG.feedbackEmail}</a> </p> <div style="text-align:right; margin-top:20px;"> <button id="close-modal" style="background:#0078d4; color:white; border:none; padding:10px 24px; border-radius:4px; cursor:pointer; font-size:14px; font-weight:500;">OK</button> </div> </div> </div> `); $('body').append(modal); // Event handlers infoButton.click(function() { modal.fadeIn(200); }); $('#close-modal').click(function() { modal.fadeOut(200); }); // Close when clicking outside modal modal.click(function(e) { if (e.target.id === 'dashboard-info-modal') { modal.fadeOut(200); } }); // Close with ESC key $(document).keydown(function(e) { if (e.key === 'Escape' && modal.is(':visible')) { modal.fadeOut(200); } }); }, 1000); });  

Hi Team! Synchronize Widget Details legend colors with conditional formatting. When conditional formatting is applied to a widget (such as colored data bars), the color swatches displayed in the Widget Details (ⓘ) panel should reflect the configured conditional formatting colors instead of generic gray boxes, making the legend easier to interpret.

Introduction In multi-tenant Sisense, a Data Designer may hit intermittent 3404 "Connection is Missing" build errors that reference the wrong tenant's connection, while an admin builds successfully. This guide explains why connection scoping causes it and how to fix it. Step-by-Step Guide Why this happens In multi-tenant Sisense, connections are isolated per tenant and per owner. The 3404 "Connection is Missing" error at build time means the build service cannot resolve the connection OID within the scope of the user running the build. When a Data Designer does not own or cannot see the connection the cube references, resolution falls back and intermittently binds to the wrong tenant's connection - which is why the reported missing connection changes between build attempts with no changes to the cube. An admin succeeds because admin visibility spans all connections. Step 1 - Share the connection with the Data Designer As an admin, go to Admin → Data → Connections. Open the connection the cube uses and share it with the Data Designer user. Grant access with edit rights so builds can resolve it. Repeat this for every connection the cube references. Step 2 - Verify tenant scoping while sharing Confirm the Data Designer is operating in the same tenant the connections belong to. Also confirm that no same-named connection exists in another tenant, since duplicate names across tenants can cause the build service to bind to the wrong one. Step 3 - Refresh the connection binding (if sharing does not clear it) If the error persists after sharing, re-bind the connection at the table level. For each affected table: Change Table → re-parse the SQL expression → Done. This forces Sisense to re-resolve the connection binding for that table. Conclusion Cross-tenant 3404 “Connection is Missing” during builds are almost always a connection-scoping and permissions issue rather than a broken cube. Sharing every referenced connection with the building user, verifying correct tenant scope, and re-binding table connections resolves the error. The key takeaway: a non-admin build user must have visibility of every connection the cube depends on. References/Related Content  Connecting to Data / Connection Manager Sisense Multitenancy Building ElastiCubes

Hello, We are working with snowflake data source and have requirement to capture meta for ecube build query from data source. Please suggest how I can set query tagging ? SET QUERY_TAG = "{Team_Name:TEAM, Application:Sisense ecubename}" I did check pre build plugins but did not get option to set data source session settings or initial sql settings in python script. Please suggest.

Key Takeaway: Professional client reporting means designing for the specific person receiving each report - not sending the same export to everyone. This post breaks down five dimensions of personalisation - brand, audience, format, data, and cadence - and what each one means in a Sisense context. Most Sisense teams send the same report to everyone. Same layout. Same data cuts. Same format. It goes out on schedule and technically does its job. But there is a meaningful difference between a report that gets filed away and one that gets forwarded to a client's leadership team. That difference almost never comes down to the data. It comes down to whether the report was designed for the person receiving it. After working with Sisense teams across a range of industries, we have found that client reporting personalisation breaks down into five dimensions - each one a decision that shapes how the report lands. 1. Brand and visual identity Every external report sends a visual signal before the recipient reads a single number. For client-facing reports, that means deciding how your brand and your client's expectations sit alongside each other - logo placement, color palette, typography, chart styling. A saved brand profile per client eliminates the reformatting work every time. 2. Audience and narrative A C-suite executive wants three numbers and a clear direction. An operations manager wants full trend breakdowns. A finance team wants Excel they can manipulate. The same underlying data needs to be composed differently for each audience - which means the design layer matters as much as the data layer. 3. Format and medium PDF, PowerPoint, Excel, Word - the right choice depends on how the client actually uses the report. A CFO presenting to a board needs slides. An analyst building models needs clean Excel. Asking the question once per client relationship eliminates months of sending the wrong format. 4. Data slicing Every client should receive only their data - isolated by client ID, account name, region, or whatever dimension maps to that relationship. For teams sending the same report structure to many clients, doing this manually does not scale. Filter iteration - defining the report once and exporting one version per client dimension value - is what makes personalised reporting sustainable at volume. 5. Cadence Daily operational reports, weekly summaries, monthly narratives, and quarterly board packs are fundamentally different artifacts designed for different purposes. The reporting rhythm should come from the client's workflow, not your default schedule. We wrote a full breakdown of all five dimensions - including what each one looks like in practice for Sisense users - on the QBeeQ blog. How to Design Client Reports That Each Recipient Actually Wants to Receive

If you manage Sisense, you've had some version of this conversation: someone asks for a report that actually looks like a finished document, not a dashboard screenshot with the edges cut off. There are more ways to solve this than most admins realize, and each one solves a different piece of the problem. A quick rundown: Native PDF export - zero setup, but the layout is whatever the dashboard happens to produce. No control over page breaks, no way to add narrative text, and pivot tables cut off at the edge of the screen. Sisense Report Manager - solid scheduling and delivery, but it's still exporting the dashboard as-is. No design layer, no multi-dashboard composition. Jasper Reports - genuinely pixel-perfect for table and pivot widgets specifically, if you have developer resource to build and maintain JRXML templates. Doesn't touch charts or KPI widgets. SAP Crystal Reports via ODBC - full design control, but it pulls your data out of Sisense entirely to do it, which is a real consideration if data residency matters to you. Where this leaves most teams: something that handles scheduling, or something that handles pixel-perfect tabular data, but not both, and rarely anything that lets you design a report as its own document rather than a dashboard export. That's the gap QBeeQ Report Studio is built for: a canvas inside Sisense where you design the report as a report - pulling from multiple dashboards if you need to, with full control over layout, brand, and every widget on the page. Report Studio Deliver , our scheduled distribution layer, is coming in beta this month. For the full breakdown with a side-by-side comparison table, here's the complete write-up .