I have created a simple Pivot viewer catelogue and in the Filter Panel it has a slider for the price with all other Facets below.
How do you bring one of them to the top and sort Alpha rather than Quantity?
If you click the "Sort:Quantity" tag, it should change the sort to alpha.
Are you using the original PV or the new one in SL5? To change the filters in the original one, you need to change the order of the facet definitions in the cxml file. To change the filters in the SL5 version, you simply need to change the order of the PivotViewer properties.
Related
I have a dashboard with two worksheets. One of the worksheets is a bar chart with just one dimension, Model Name. I've added a Top N parameter to it, set to display only the Top N highest priced items.
The other worksheet is a bar chart at a higher category level, and I'm using that as a filter for the other. So when I click on one of the categories, the other worksheet should display the Top N items for that category. But, when I click on a category, the other bar chart goes blank. My thinking is that the parameter is applying to the entire dataset, and not recognizing the filters applied.
I've tried changing the filters to context, but that hasn't rectified the situation. Is there a way that I can get the parameter to recognize the active filters?
If you want the filter to be evaluated first, you can do that by right-clicking on the filter item and select "Add to context."
For more, see Tableau's "Use Context Filters".
I've been looking for an approach to remove unwanted values from a views grid column filtering dropdown but I'm not sure if its even possible.
A specific view in our app only displays results where the column will contain 5 values, however the column option set has 20+. Is it possible to remove the unwanted 15 values from being displayed when the view's filter by function is used?
This documentation does not mention any way the values can be hidden.
I have added a web resource to a view column before, to change text values into an image, however I don't think this is an applicable place to add a script to hide filter by values.
I have developed plugins so not against using this medium if the approach works and does not introduce a performance hit.
Unfortunately that header filter is not open for customization/configuration. Though MS mention it as Excel like filter, it is not going to give the filter options for only values from current list. It will load the full options list.
When we had such requirements in the past - we have developed a PCF control with grid + filters and used it instead.
In the below link when i select something the filter gets displayed but the chart does not changes
here is my jsfiddle link: jsfiddle.net/amru/t56z8w2w/3/
Filters do not apply to groups defined on the same dimension as the filter. Define another chart based on a different dimension and it should change when you make a selection.
I am looking for a way to filter a table based on clicking a dynamic value in a Textarea in Spotfire 7.0.
I have a Textarea with an image and a bunch of calculated values over the top of that image (essentially a non geographic "map" of values). I would like to filter a table to show the rows which contribute to that dynamic value.
How can I filter the table based on the value clicked in the Textarea?
You can use Spotfire bookmarks. Create bookmarks and then configure images as a buttons and apply click action on them to redirect user to the particular bookmark.
You can also apply marking on Calculated values in a way that you can set your child visualizations to be limited by your dynamic value marking.
Is there a way to add a field into the valuePicker with the possibility of adding new values in it? The valuePicker get's the values from a view, and I wouldn't want to add another addButton to add some values withing that view, in separate way. I would like a dialogBox like the valuePicker + the option to add new documents withing it. It is possible?
That functionality isn't available in the Value Picker. It's unlikely to be added, because of the variety of dataProviders, which makes it difficult to know where to add the option to make it available to other documents, and also ensure validation of options.
Typeahead on an Edit Box control allows you to add entries not in the list.
Alternatively, you can add a separate Edit Box to your XPage to include a value not in the list. But if you want to store the new option in the same field, you'll need to write the code to add the option to the source of the list. E.g. if it's the dataProvider of your Value Picker is a dominoViewValuePicker, you'll need to create a document in that view as well; if it's a simpleValuePicker, you'll need to compute the options so they also look to this field. Otherwise, when the user edits the document again, the option will not be available in the list, so may get removed.
Why do you want the user to insert new values into a field in valuePicker? Instead, let the user add the new value direct into the field which is the valuePicker related to.