ContributionsMost RecentNewest TopicsMost LikesSolutionsRe: Using BLOX input.toggle element to add additional dropdown menu Thanks DRay , I'll reach out and see how to move forward from here! Using BLOX input.toggle element to add additional dropdown menu Hi there, I have a BLOX widget that I'm using as a controller for a line chart on my dashboard. This BLOX widget is used to change the date granularity as well as change which KPI's are displayed in the below line chart. At a baseline, it works, but I'm actually looking to modify this widget by adding a toggle that when enabled adds another KPI dropdown that the user could then interact with. I've got some screenshots that mock up what I want this to look like, but I'm unable to get this actually working. I'm having a hard time passing the true/false data (true when checked, false when unchecked) to be evaluated by a condition element that is yet to be added. I'm including the configuration for the BLOX widget below as well. The item set I want removed is the 3rd Input.choiceset with the class "togglable" The actual action script seems pretty straightforward once I can have the dropdown added reliably. I appreciate any help, and thank you very much in advanced! { "actions": [], "body": [ { "items": [ { "columns": [ { "items": [ { "style": { "color": "", "font-weight": "bold", "margin": "auto", "padding-left": "20%" }, "text": "Choose a Date Granularity and Performance Metric", "type": "TextBlock", "weight": "regular" } ], "type": "Column" }, { "items": [ { "choices": [ { "title": "Years", "value": "years" }, { "title": "Quarters", "value": "quarters" }, { "title": "Months", "value": "months" }, { "title": "Weeks", "value": "weeks" }, { "title": "Days", "value": "days" } ], "class": "dropDown", "displayType": "compact", "id": "dateGran", "style": { "font-family": "Roboto", "visibility": "visible", "margin": "auto" }, "type": "Input.ChoiceSet", "value": "1" } ], "type": "Column" }, { "items": [ { "choices": [ { "title": "Theo Win Per Unit Per Day", "value": "1" }, { "title": "Actual Win Per Unit Per Day", "value": "2" }, { "title": "Coin In Per Unit Per Day", "value": "3" }, { "title": "Leased Fees Per Unit Per Day", "value": "4" }, { "title": "Net Theo Win Per Unit Per Day", "value": "5" }, { "title": "Net Actual Win Per Unit Per Day", "value": "6" }, { "title": "Theo Win", "value": "7" }, { "title": "Actual Win", "value": "8" }, { "title": "Coin In", "value": "9" }, { "title": "Net Theo Win", "value": "10" }, { "title": "Net Actual Win", "value": "11" }, { "title": "Games Played", "value": "12" }, { "title": "Avg Bet", "value": "13" }, { "title": "Occupancy", "value": "14" }, { "title": "Net Theo Win Index VS Floor", "value": "15" }, { "title": "Net Actual Win Index VS Floor", "value": "16" } ], "class": "dropDown", "displayType": "compact", "id": "KPISwitch", "style": { "font-family": "Roboto", "margin": "auto" }, "type": "Input.ChoiceSet", "value": "1" }, { "choices": [ { "title": "Theo Win Per Unit Per Day", "value": "1" }, { "title": "Actual Win Per Unit Per Day", "value": "2" }, { "title": "Coin In Per Unit Per Day", "value": "3" }, { "title": "Leased Fees Per Unit Per Day", "value": "4" }, { "title": "Net Theo Win Per Unit Per Day", "value": "5" }, { "title": "Net Actual Win Per Unit Per Day", "value": "6" }, { "title": "Theo Win", "value": "7" }, { "title": "Actual Win", "value": "8" }, { "title": "Coin In", "value": "9" }, { "title": "Net Theo Win", "value": "10" }, { "title": "Net Actual Win", "value": "11" }, { "title": "Games Played", "value": "12" }, { "title": "Avg Bet", "value": "13" }, { "title": "Occupancy", "value": "14" }, { "title": "Net Theo Win Index VS Floor", "value": "15" }, { "title": "Net Actual Win Index VS Floor", "value": "16" } ], "class": "dropDown togglable", "displayType": "compact", "id": "KPISwitch", "style": { "font-family": "Roboto", "margin": "auto", "visibility": "visibile" }, "type": "Input.ChoiceSet", "value": "1" } ], "type": "Column" }, { "items": [ { "actions": [ { "title": "Apply", "type": "UpdateData" } ], "style": { "align-self": "", "font-family": "Roboto", "margin": "auto", "padding-left": "" }, "type": "ActionSet" }, { "type": "Input.Toggle", "title": "Compare 2 KPIs", "id": "DualAxisToggle", "style": { "margin": "auto", "font-weight": "bold" }, "valueOn": "false", "valueOff": "true", "value": "true" } ], "type": "Column" } ], "type": "ColumnSet", "width": "" } ], "type": "Container", "width": "" } ], "carouselAnimation": { "showButtons": false }, "script": "$('.dropDown').find('.placeholder').remove().end().prepend('<option class = placeholder value=\"\" disabled selected>Select Filter</option>')", "showCarousel": true, "style": "", "title": "", "titleStyle": [ { "display": "none" } ] } Re: Enabling Jump to Dashboard once a user drills down to a certain level Thank you very much Daniel for the explanation, this ended up working for me. The error in the console.log shouldn't be an issue, but would be great if there was a less disruptive way with interacting with JTD/Jump items. Appreciate the help! Re: Freezing pivot table first column Piggy backing on this, Adding a pivot table design option in the design editor that allows us to select what number of columns to freeze (Starting from the left). Enabling Jump to Dashboard once a user drills down to a certain level Summary is in the subject line. I know that there's Jump to Dashboard configurations that allow users to jump to different dashboards depending on the column set. However I don't see my particular case, in which I only have a single dashboard to jump to, but I only want to jump there after the user drills down and reaches a specific granularity. In my case: I have a dashboard that is on a "game theme" level. From here a user can drill down to Players who play on this machine. After drilling down to the player level, I would then (and only then) like the option to "Jump" to a Player Market dashboard. This dashboard provides analytics tailored to a single player. It wouldn't make too much sense looking at multiple players. Is there a way to hide the option to "jump" to this dashboard until our user drills down to the player grain? SolvedRe: Calculated Dimensions Thank you very much for the input everyone. I'll report back to let you know if these suggestions worked! Calculated Dimensions The idea here is to expand the formula editor (Specifically CASE WHEN Statements) to allow the creation of dimensions or "buckets" based on filtered data. This is useful on the dashboard level as we may want to recategorize our data dynamically after filtering the dashboard. Lets say I have a pretend table holding daily customer transactions. In my report I'd want to see each customer's average spending for an arbitrary time frame. I'd also like to categorize that player BASED off that average spending. Which could change based on any filters I use. IE) CASE WHEN [Avg Money Spent] > 999 then '1000+' WHEN [Avg Money Spent] > 699 then '700 to 999' WHEN [Avg Money Spent] > 399 then '400 to 699' ... WHEN [Avg Money Spent] >= 0 then '0 to 99' ELSE NULL END I would then use this calculated dimension in visualizations like pie charts, etc. I'm not sure if this is possible, but being able to use this dimension as a filter would be very useful as well. IE) Show me all the customer who fall under '400 to 699' range for any given period.