We have a one-question checkbox (multiple selection) survey in SharePoint.
When selecting "Show a graphical summary of responses" in SharePoint, it tabulates the different combinations of responses as distinct answers as opposed to totaling the number of each option selected.
Is there a way to show the total of each option selected in the Graphical Summary view?
Using only out of the box solutions, no. I have had many users reporting "hey, look, I found a bug in your portal survey" and actually complaining about the problem you're describing here.
The only workaround I've found is to use multiple checkbox fields instead of one multi-choice field. However, this does not look that nice.
Related
I checked SuiteAnswers and here on Stack overflow but don't see an answer. Is there a way to make a Multi-select field in NetSuite as an option for an available filter in a Saved Search. I tried to do this by creating a test MS field on an Employee and creating a saved search. However, when adding it as an available filter it grays out the ability to show in the filter region, which, by all practical purposes, makes it not usable as an available filter.
Has anyone found a way to do this? Or do I have to have multiple searches for variations on the values we want in the multi-select, which is not ideal?
This is very frustrating NetSuite behaviour however I have found a workaround that works some of the time.
Create a saved search
Go to the "Available Filters" subtab
Add the Select/List type field(s) you require
Tick "Show In Filter Region."
At this point the "Show as multi-select" checkbox will be greyed out (disabled.)
Save and run the search.
Click "Edit This Search"
Navigate back to the "Available Filters" subtab and the "Show As
Multi-select" checkbox should now be enabled, tick it.
Save and run your search again.
This will be my first Add-In. Please bear with me.
The goal of my add-in application is to replicate a very tedious, repetitive work by a user. She tells me that she initiates her task by clicking in some sort of combo box or drop-down menu and typing several digits, followed by a click on the "Ok" button.
Question No. 1: What is the official name of that contraption (the one in mustard color) and how is it coded into an Excel cell?
I gather than Add-Ins are coded using something called "Object Model"? I have seen about 4 lines of such code.
Is there a statement like this?
ClickOnCell("E32");
That contraption is a filter.
If she always types the same number into the filter search then you could store the filter as a custom view in the sheet.
Due to the lack of responses, both here and in 2 Microsoft forums, I have decided that the answer is:
There is no way
Then again, with only 13 people reading the question, the chances of one of them knowing the answer are very low.
I want to be able to filter a SharePoint list based on the values present (easy by clicking the filter button at the top of the list for each column). However I'd like to give options in a drop down menu and once chosen the list would be refilted based on the options I give. Is this possibile to do in the browser or would it require designer or actual code? Thank you.
This is all SharePoint 2010 Enterprise Server knowledge; I've never used 2007.
What #Ryan is alluding to here is that you can click a down-arrow on most list columns to filter them. One caveat is that if the column is multi-select, it won't display a drop-down. (SharePoint doesn't know how to group, filter, or sort on multi-select columns.) Another caveat could be that if you're displaying the list items in such a way that their headings don't appear (such as in a List View web part, or maybe in some of the styles...) you obviously won't be able to filter.
A solution might be to use a "SharePoint List Filter" web part, which uses a list column as the source for filter values which can then be sent to other web parts -- such as a List View web part. Presumably, you could use the list you're intending to filter as a source for the Filter web part itself. From a UX perspective maybe this might help you display the list with different styling, but still get the drop-down filter directly in the content area.
A caveat with the "SharePoint List Filter" web part is that it's not actually a drop-down per se, but instead shows a little filter icon that pops up a dialog in which users then have to select a value.
Note there's also the "Managed Metadata Navigation" feature that would give users dropdowns (for e.g. choice columns) and metadata filter fields (for managed metadata columns). These show up in the Quick Launch (left-nav area) if configured on the list/library settings. The feature must first be enabled on the site.
In Microsoft Dynamics CRM 2011 you can create views using advanced find. Inside advanced find, you should define for a specific entity which columns you want to see in the result.
What I want to do is limit or hide specific columns that people can choose for the advanced find.
Any ideas?
Thanks!
Hi Rob,
Out of the box you can disable a column from being 'searched' --
listed in the filtering area of the advanced find.
However, all fields that a user can read are avail for selection in
the advanced find. The only method to change this would be custom
code in a 'plug-in'. Then with a plug-in just about anything is
possible as it is compiled code and you could filter out certain
columns from being available.
Alex Fagundes - www.PowerObjects.com
The comments by Alex Fagundes, with all due respect, are wrong. As ckeller suggested, you can limit the columns displayed to the user, and you certainly don't need a plug-in to do this (nor could you even if you wanted to, so far as I know).
In the client, all you have to do is navigate to the entity the advanced find view of which you want to change, click the "Customize" tab, click "System Views", click on the advanced find view, click "Add Columns", select/deselect the columns you do/don't want to see, then publish your changes.
You can also select/deselect columns of any appropriate related entity this way as well.
If you mean search columns (fields they can search by):
To limit the columns they see in an advanced find search, you have a fun job on your hands.
Go to Settings -> Customisations -> and choose the entity you want and list all the fields.
Double click on each field in turn and you will see a drop down menu called 'Searchable'. Set this to 'No' and the field is hidden from Advanced find searches (after you publish your changes).
Repeat this for all fields required.
If you mean fields they see in their results:
Follow the answer by #jamnap
The solution of Peter will only change the default view for advanced find. The user will still be able to add all columns and customize his own view.
Fields cannot be removed from "add column" in advanced find OOTB. This is what Alex Fagundes from PowerObjects has written.
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".