mckenziedubois
Cloud Apps
Joined 3 years ago
User Profile
User Widgets
Contributions
Row-based Jump to Dashboard
We want to be able to disable jump to dashboard for certain rows in a pivot table and bars/pie-slices in various charts. Currently we are only able to disable it completely. We would like to be able to be more specific on the disabling and only remove the jump to dashboard capabilities on the specific rows or bars.336Views2likes0CommentsRow based Jump to Dashboard
We want to be able to disable jump to dashboard for certain rows in a pivot table and bars/pie-slices in various charts. Currently we are only able to disable it completely. We would like to be able to be more specific on the disabling and only remove the jump to dashboard capabilities on the specific rows or bars.Solved739Views0likes1CommentRe: Scaling elasticubes? Updating multiple elasticubes? A single reference elasticube?
Thanks for the quick response David, it seems to me that perspectives is more about defining a subset of tables from within the same database. Doesn't seem like I can have individual perspectives point to different dbs but maybe I've overlooked something. Ideally, we could have Elasticube_Base, Elasticube A (points to db A), Elasticube B (points to db B)... And then an update to Elasticube_Base could be applied to all Elasticubes.952Views0likes2CommentsScaling elasticubes? Updating multiple elasticubes? A single reference elasticube?
We are in the process of converting a single live model into a handful of elasticubes. Previously, we were using parameters and data groups to point the live model to a database depending on the user that was viewing the sisense report. Now we will need to build a elasticube for each of the databases. We will likely have around 100 elasticubes for all of our databases. All the elasticubes are identical except for the database they are being pointed to. Schemas, tables, etc, are all the same. So when a change needs to be made, either adding a relationship or perhaps a new table it will need to be rolled out to all elasticubes. Is there a way we can roll out this change to all the elasticubes? Is there a way to have a base elasticube build that can be referenced and then rolled out to various databases.984Views0likes5CommentsReload dashboard after filterschanged event
Trying to find a way to reload the dashboard completely after the filters are changed. Some of the functionality in my dashboard is lost when I change the filters so would like to completely reload after the filters are changed. The below code was what I thought I could do but it does not work. dashboard.on('filterschanged', function (se, ev) { dashboard.refresh() });879Views0likes1Comment