My site has many entries, each having several categories assigned to them. Using Dynamic Parameters, I'd like to allow users to filter the entries to show only those belonging to certain categories, perhaps by selecting checkboxes. That part I know how to do.
The categories parameter in the Channel Entries tag lets you indicate that you want to show entries with ANY of the selected categories (category="2|45|4|9") or ALL the selected categories (category="3&7&8").
Is there any way to let users make the selection of ANY or ALL when they interact with the Dynamic Parameters form? So effectively, they could say either "Show me entries belonging to ANY of the categories I've selected" or "Show me entries belonging to ALL of the categories I've selected"?
Related
I have an entity called Garage that has some properties and a list of Vehicles.
Vehicle is inherited by some entities like Car, Truck, Bike, etc.
I want to make a JSF page to create a Garage, that allows the user to add, remove and edit the list of Vehicles.
I tried to use a DataTable to list the Vehicles, but Car, Truck, Bike, etc have different attributes so each should display different fields.
Is there a way to do this?
Is there a way to display or filter (by editing a Template) all the products that match a certain Custom Field parameter (in example "custitem_outlet)"?
I have already added on the Netsuite backend these custom fields as checkboxes.
I would like to show the items on different Lists, in example one list will show the items with "custitem_outlet" checked and the other with "custitem_arrivals" checked.
Thanks in advance!
I have a standard list in SharePoint, one column of which is of type Person or Group.
When I'm viewing the list from a standard view, the dropdown filter for that column lists, as expected, only those people who are already listed as a value for at least one row.
However, when I view the list from a datasheet view, the dropdown filter lists all of the groups and users on the entire site instead of just those users who are values on the list.
Does anyone know why this is happening and how to configure the datasheet-view dropdown list to only show those users that are listed in a field?
I'm playing with custom module shoppingcart.
I currently have a product part with fields price and sku. What would be the best way to add a configurable product for example a shirt has different colors and sizes. But now all products has to be configurable. I want to have the user select from a dropdown in my view from available sizes.
If I create a new content part and attach enumeration field to i must choose one item when i create product from backend. What I want is to render all the items in the enumeration field in the view and be able to select one.
// Tomas
We have a reporting web site and in the search screen most of the fields are comboboxes. We then AND all the fields together to get a filtered list of records. For example if i chose NY in the City dropdown and priority 1 in the priority dropdown and sales in the team dropdown, it would general something that looked like this (pseudo SQL)
Show me all record where City = 'NY' AND Priotity = '1' AND Team = 'Sales'
We now just added tagging to our records so to support searching by tag(s), we added an additional textbox to search by TAG where you can entered a comma seperated list.
Right now this is an autocomplete textbox which supports multiple entries.(similar to the Multiple Cities (local) example on this page.
When we rolled it out people had different expectation on how search would work when you entered multiple items in the text box. Would it:
Do an AND and only return records that had ALL of the tags listed.
Do an OR and return records that has ANY of the tags listed.
It turns out that we rolled out #1 but many people expected #2. Is this just basically preference or is there a default standard here in this example. Our only solution right now is to add a radio button next to the textbox to say ALL or ANY
If your users expect it to work one way then that's the way it should work.
This is a great example of why you should test early and often with actual users.
I'd say it is not basically preference, but expectations based on what users experience in other types of searches. The "OR" was probably expected by your users as use of tagging gets pretty close to being like a search engine searching on any word in a text and most search engines do an "OR" and then order the results according to how many terms (tags) were "hit".
If going all the way supporting AND and OR operators is not feasible right now, then I would indeed offer an "All" versus "Any" radio button and default it to "Any".