Multiselect Picklist

[D365Ideas_Admin]

When I was working in 3.0 for a customer, I created a multi select picklist using the inbuilt options from Dynamics CRM. If I could do this then I believe MS can build it and help a lot of customers.

In the advanced find for any status, optionset field in the filter criteriea, we get a multi select picklist. We can move values around in that and it displays the multiselected values as well. I have used this same window and a couple of XML strings to create a similar field on a Form. The XML strings store the Values in my case.

This solution would certainly help a lot of customers and enhances the CRM product as well. The customers I speak to say that it is available in other products and why not here. I see that there is a possiblity and hope you can release it.

[D365Ideas_Admin]

Thank you for your feedback. This is a great suggestion! We will consider this in our roadmap.

Sincerely,
Neeraj Nandwana
PM, Microsoft

[D365Ideas_Admin]

We receive a lot of requests where customers are looking for multi-select pick-list in CRM. Customers try to implement various workarounds that breaks there environment with unsupported customizations sometimes. If we have this as a feature in CRM, it would avoid such scenarios.

[D365Ideas_Admin]

Thank you for your feedback. This is a great suggestion, and we will consider this in our roadmap.

[D365Ideas_Admin]

Just as this hasn't been updated for 7 months now, I wanted to add that I am working on a CRM implementation now, and this is one of the most frustrating portions of it. We will be creating several hundred customized fields and over a dozen custom entities. Many of them would be easily simplified by having a multi-select picklist which is in many products. This is compounded because the workaround posted of creating the custom entity will not only create more entities we have to work with, but also creates an issue for product adoption. When the workaround for having an associated entity is used, you must save the original entity before you can access/use the "multi-select picklist." This is sometimes difficult to remember as we're developing it, but being rolled out to several hundred people, it could become a serious pain point. Even with the idea of creating javascript workarounds, this will have to be done for several dozen fields. The product even has the equivalent of a multi-select picklist when creating system views, so not having it when creating an entity makes the product fairly difficult to work with as a whole.

[D365Ideas_Admin]

Number one pain point, for sure. People have been hacking workarounds since the earliest days of the product; I'm astonished this isn't addressed yet.

[D365Ideas_Admin]

So this is marked as resolved...does that mean we should be seeing it soon?

[D365Ideas_Admin]

This is marked as resolved, but it really isn't. Most competing software has this feature but it is still not present in Dynamics CRM. The usual workarounds (N:N relationships or storing text of selected options in a hidden field) do not work in a multi-language scenario.

[D365Ideas_Admin]

More "how did they do it" context: https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/field_types.htm#i1435691 https://developer.salesforce.com/docs/atlas.en-us.196.0.soql_sosl.meta/soql_sosl/

[D365Ideas_Admin]

Salesforce.com has this natively: https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/field_types.htm

[D365Ideas_Admin]

@Stuart Brown, UK - Good points. Also ~native~ N:N relationships also don't work for reporting purposes either. And, with salespeople wanting to operate more and more on their iPads, there really needs to be a way to report on multi-select via OOB dashboards. Connections (an OOB ~manual~ N:N) gives us reporting capabilities but, man, the UI is not ideal (even in the browser) and new Connections can't be made on the iPad anyway. -- @MSFT - Use case #1: -open the CRM form (say, Project), -area of the form for tags is visible by not populated, -when I click on the area it opens a page of all the relevant existing tags, -I select the ones I want, -if I can't find one I add it (and doing so notifies a designated "tag wrangler" team), -click save and am returned to the CRM form with a cloud of the tags I just applied to that record Use case #2: -Toppings "field" (tag cloud) has the available tags of - cheese, mushrooms, pepperoni, black olives. -I populate the tag cloud with all but pepperoni. -The Crust field would have available tags of - original, thin, stuffed crust (aka none of the Toppings tags would show up as available tags for the Crust field). http://www.xrmconsultancy.com/what-we-do/tagging-for-microsoft-dynamics-crm/