Displayr

Displayr's controls are all form fields — combo box, list box, text box. There's no way to present a selection as a grid of clickable tiles, which is the standard way to offer a small set of choices on a dashboard landing page. This should be a control, not a visualization. A visualization can't hold state, so a tile grid built as one can't filter anything — the click has nowhere to go. As a control, it inherits everything that already works: it holds a value, R can read it, and it can drive a filter. What it would need: Items from a variable's categories or a list, laid out vertically, horizontally, or as a grid of rows and columns. An optional second line per tile showing a value from the data, beneath the item label An optional icon or image per tile Per-tile accent color, and formatting for the selected, hover, and unselected states Fixed tile size or fit-to-space Power BI ships this as the button slicer, generally available, with this exact feature set, including grid layout, per-button images, and "highlight labels" showing a value below the button text. Its nearest Displayr equivalent is a combo box.

This feature request would be to allow users to omit the "Missing Data" category from being a selectable option in a combo-box control, but still allow the "(All)" selection to mean "all respondents." Users will often create a combo-box filter that uses a variable that has missing data. However, it might be undesirable to include "Missing Data" as an item in the combo-box or list box. (See the screenshot attached, for example). In these cases, the user wishes to remove the "Missing Data" option from the combo-box, but this changes the mechanics of the combo-box filter. Now, when "(All)" is selected in the combo-box, this does not represent ALL respondents; rather, it represents all the matches with the list of text that is in the combo-box. The workaround for users is to program an "if statement" in the R Code of the combo-box filer. For example, in the screenshot below, if a user wants to omit "Missing Data," from the list of options in the combo-box, doing so will cause "Missing data" to be filtered out of the combo-box filter. Instead, what they can do is modify the code of the Combo-Box filter to something like: if (length(combo-box) == 9 {rep(1, length_of_data_set)} else { <normal combo-box filter mechanism> }

Reset all combo-boxes

Like Displayr's other controls, this button control would allow users to set up custom inputs where a viewer clicks a button on a page to do something (change a filter, change selections, etc.) just as you do with other controls. The buttons could work singly or in concert with other buttons.

The user wishes to change the font color of one item in the Item list. Example: They wish to 'grey out' the Missing Data item.

If a user has a date picker in their published dashboard, they must go through a number of steps if they want the date picker to default to the current date. The reason is that the selection in the date picker will default to whatever date it was set to when it was published. But often, dashboard developers will want a date picker to default to the current date (whatever that happens to be). We do have a workaround that requires that the document automatically republish. But this feels like an ugly workaround.

When combo boxes get particularly large or run off screen it can be difficult for viewers to find what they want to select. Allowing a viewer (or user) to type in the combo box and allow it to search through the selectable results, similar to other searchable drop-down boxes on other sites, would help alleviate the problem.

It should be possible to create a single object that allows users to select dates between a "from" and "to" date with intelligent elimination of impossible dates based on the selection in both fields.

When adding a Control to a Master View it’s not possible to go to Properties > GENERAL > Name and rename it. You can change it by opening the Page in the Page panel and renaming the item itself. Also reported as a bug: [ https://numbers.atlassian.net/browse/RS-14736|https://numbers.atlassian.net/browse/RS-14736|smart-link ]

At the moment, to filter a table's rows or columns using a combo box, I have to turn it into a visualization or create a calculation first. I would like to be able to set a relationship between any basic (not R-based) table and a combo box so that the selection in the combo box acts with the table to show/hide rows or columns in the table.