Liliia_DevX
Sisense Employee
Joined 03-02-2023
User Profile
User Widgets
Contributions
Minimum Information Required for a Sisense Support Ticket
When submitting a ticket to the Sisense Support Team, please always aim to provide clear, categorized details regarding your issue. By supplying all possible answers upfront, you eliminate the need for back-and-forth communication, allowing our engineers to begin investigating and resolving your issue immediately. Ensure you include the following: 1. Problem Definition (What is the problem?) Clear Description: Explain the issue and the functionality that is failing. Expected vs. Actual Results: Clearly state what you expected to happen versus what actually happened. Steps to Reproduce: Provide a specific, step-by-step guide on how the support engineer can replicate the issue. Visual Proof & Network Traffic: Attach uncropped screenshots or screen recordings showing the error or behavior. For web interface issues, please also attach a HAR file (see: Generating a HAR file for troubleshooting Sisense). 2. Scope and Business Impact (Who is affected?) Affected Users/Dashboards/Cubes: Note whether the issue impacts all users, a specific user group, or just a single user. What is unique about the affected group? Does the problem occur across the entire platform, or only on specific dashboards or ElastiCubes? 3. Frequency and Pattern (How often does it occur?) Timeline: Exactly when did the problem first occur? Did it ever work as expected in the past? 4. Environment and Recent Changes (Did something change?) Recent Events: Did the issue start after a specific event, system change, or Sisense version upgrade? Load Changes: Has there been a recent increase in the number of users, data volume, or concurrent builds? Infrastructure Health: Do you observe any infrastructure utilization outliers (e.g., spikes in CPU or RAM) during the occurrence of the problem? For Cloud Customers: Provide the URLs to the affected Dashboard/ElastiCube and, if possible, relevant usernames support can use to troubleshoot. Please make sure the Support Access is enabled on the instance. 5. Technical Artifacts (Logs for On-Premise Customers) Always attach the relevant server-side logs based on the issue. Identifying the Service: If you are not sure which service is affected, use the Sisense Linux Services Guide. The log name corresponds directly to the service name. Extracting Logs: For step-by-step instructions on pulling these files, see: How to identify and download logs from the Sisense server. By packaging your problem description, business impact, recent environmental changes, logs, and a HAR file into your initial request, the Sisense team can bypass the standard fact-finding phase and begin actively resolving your issue immediately.54Views0likes0CommentsRe: The New Sisense Support Portal is Now Live! 🚀
francoisvv​ hi! We've checked the issue and found out that an email with a code was sent successfully. Could you please check with your IT/security team if it could have been blocked by the security settings? Please update me on the result.73Views2likes0CommentsRe: The New Sisense Support Portal is Now Live! 🚀
Hi francoisvv​ , Please accept our apologies for this inconvenience. We're working on the fix of this issue. Please send an email to mailto:[email protected] to create a ticket and reply to the support team back via email for now. Thanks for your patience and understanding.88Views2likes1CommentRe: How to create a week date range with start and end if the week for each week?
Hi, It should be possible to add custom columns in the model for the start and end dates and concatenate them into a string to use as the dimension. Otherwise, swap 'beforeviewloaded' for onBeforeRender prop in CSDK and use the same logic to manipulate highcharts options. Hope that helps :)65Views0likes0CommentsRe: How to create a week date range with start and end if the week for each week?
Hi :) Please try this approach suggested by OleksiiDemianyk​. On the client you need to: Add 6 days to each date returned by Sisense; Change category from the default one to the ${startWeekDate} - ${startWeekDate + 7 days} This can be done on the event beforeviewloaded. Here is the sample where we have week as the only category: const months = { 1: 'Jan', 2: 'Feb', 3: 'Mar', 4: 'Apr', 5: 'May', 6: 'Jun', 7: 'Jul', 8: 'Aug', 9: 'Sep', 10: 'Oct', 11: 'Nov', 12: 'Dec' }; widget.on('beforeviewloaded', (scope, args) => { const [ seria ] = args.options.series; seria.data.forEach((point, index) => { const startDate = formatDate(point.selectionData[0]); const endDate = formatDate(new Date( new Date(point.selectionData[0]).getTime() + 6 * 24 * 60 * 60000), true); args.options.xAxis.categories[index] = `${startDate} - ${endDate}`; }) }) function formatDate( dateItem, returnYear = false ) { const [ year, monthIndex, date ] = dateItem.toISOString().substr(0, 10).split('-'); const monthString = months[parseInt(monthIndex)]; return returnYear ? `${date} ${monthString} ${year}` : `${date} ${monthString}`; } Hope that helps!146Views0likes2CommentsRe: Querying Model in Text Widgets?
Astroraf​ Hi 🙃, According to our dev team, there is no need to query data inside a text widget. Instead, load the data with a separate useExecuteQuery hook (example on playground). You can also render this data in any format anywhere on the page. If you need to inject a new widget to the existing dashboard on the fly, you can add a new widget (e.g., TextWidget with a static data-string) like in this example. Even a better option is to create your own custom widget (example) with any data visualization you need. CustomWidget is a much more powerful and flexible solution and is a direct replacement for the BloX plugin in the Sisense native application. Hope that helps!87Views1like2CommentsRe: How to create a filter within a widget?
Hi Astroraf​ ! It might be possible to use Blox to create buttons with filters instead of the drop-down like in this guide: https://community.sisense.com/kb/blox/changing-measures-in-the-entire-dashboard-using-blox-user-interface/8802/comments/26261#M3953 It's changing values but I believe that similar logic could be used for your case. Anyway it will be still a separate widget.47Views0likes0CommentsRe: JumpToDashboard - Troubleshooting the most common configuration issues
Hi Astroraf​! Please try to use resetDashFilterAfterJTD to reset filters on your JTD dashboards after jumping to them. It might be a spelling issue. If it's not, please raise a support ticket providing parent and drill dashboards examples along with the JumpToDashboard configuration for us to review :)53Views2likes0Comments