ContributionsMost RecentNewest TopicsMost LikesSolutionsGive developers the ability to explore production without being able to modify right now we can only allow our developers to either edit models in test or read/use. With read/use they aren't able to actually see the cube in the data page. I need my developers to be able to explore connections, schemas and tables in prod without having the ability to actually make any changes. https://community.sisense.com/category/support/discussions/supportportal#case-detail:500Pk00000mKN4vIAG Re: Help with CI/CD Workflow for Sisense + GitHub Integration Hey DRay Dashboards and cubes Re: Help with CI/CD Workflow for Sisense + GitHub Integration DRay The changes that were merged into the main branch in test. Re: CASE WHEN syntax w/ multiple conditions bminehart CASE statement on strings will work in the cube. We have pushed these calcs upstream to the cube or database level. Re: Does the data cube use always inner join? This is a pain point for us as well zoolee . We have been able to bypass this with a custom table like Ido_QBeeQ recommended. What we did was union blank fields so that the inner join won't filter out needed rows from table A if they don't exist on table B. For example: Table A order # | Amount | Sales Rep ID 123 | $500 | x 456 | $200 | y 789 | $100 | NULL Table B Sales Rep ID | Name x | John y | Mark In the scenario if we tried to join table A and table B on sales rep ID we would lose order number 789. By adding null values to table B we are then able to join the null ID on order 789 and keep all of the data from our fact table. SELECT SalesRepID, Name FROM SalesRep UNION SELECT NULL AS SalesRepID NULL AS Name Help with CI/CD Workflow for Sisense + GitHub Integration Hi everyone, We're currently using two environments—test and prod—and recently began using Sisense's Git integration with GitHub. We're now looking to improve our CI/CD process and wondering if anyone has come across solid documentation or examples. Specifically, we're hoping to: Automatically deploy changes from a feature branch in test to main in test after a pull request is merged Then automatically deploy the same changes to prod Has anyone implemented a workflow like this or found official guidance on automating these deployment steps? We'd love to avoid manually pulling these changes into each environment. Appreciate any advice, links, or lessons learned! Lollipop chart how-to Years ago, I found a helpful method for creating a Lollipop chart using a "break-by," but that approach isn’t always feasible. I developed a workaround by combining a stacked bar chart with dots, and now I'm looking to make the dot radius and bar width dynamic based on the number of category values to prevent overlap. Re: GIT Instruction How To Vicki786 DRay How do database connections come into play? If I push my commit from my dev environment to source control can I then pull those into my prod environment that is connected to a different database? Re: Favorite dashboard Please add this feature! It has been requested many times from our users Re: Turning off click to filter on Widget DRay This isn't a Sisense bug, but a bug created by the script we have that is hiding other values. To bypass this we want a script that will ultimately disable any type of filtering this widget when it is clicked on. When the legend or the view is clicked we don't want anything to happen. Does anyone have a script for that?