Filtered multi-Picklist Solution?

[Anonymous]

Hi folks.

Looking at our NC system we have currently. We've created a filtered picklist workspace to be used for categorising issues.

The filtered picklist has 3 levels. On any single Issue log, we'd like to be able to capture numerous issues ( ie have multiple selections from the 3rd level).

Inspection--|

------1-------| Casting Line--|

----------------------2--------| Broken Drill

----------------------2--------| Face square

----------------------2--------| Surface Finish

---------------------------------------3--------|

I was hoping to have one field of level 1, one field of level 2, and multiple fields of level 3. Problem is, whatever I select in the first level 3 field automatically copies into every other copy of this field.

Is there a way to have the 3rd level field as type: multi-select?

My other option was to use these filtered picklists in the grid tab, however for logging multiple issues, it becomes cumbersome to have to reselect level 1 and 2 for each new row.

Has anyone got any suggestions in implementing this?

Cheers

[john.denner]

Can you share a screenshot(s) of what it looks like? My brain is having a hard time visualizing this; probably because it's Friday. 🙂

[Anonymous]

What I'd like, is to make different selections in the fields issue, issue 2 and issue 3.

Currently, when I select "Coating" in the field 'Issue', this same selection is copied down issue 2 and 3, and there's no possibility of changing them. Does that make sense?

I've not yet tried this in the grid tab, however I would imagine it'll work but require someone to reselect field 1 and 2 for each line of issue they'd like to record.

[dvirh · Accepted solution]

Thanks for the suggestion Stuart. I understand what you are asking for, but it won't work with the solution concept that we have in FLC at the moment. The problem is that there is no hierarchy in FLC. This is a nice feature of the Filtered Picklist implementation in FLC and it means that you can make a selection in the various fields with no particular order. For example, imagine a Filtered Picklist that allows the user to fill in an Address. The user may type in the Zip Code first and then get to see only States that have this Zip Code, or he may select the State first.

If we allowed multiple selections at any of the fields, it will mean that other fields may become ambiguous. This will break the paradigm we have for Filtered Picklists in FLC. If we had a hierarchical paradigm, that would not have been a problem but we would have lost the flexibility that the current paradigm is providing.

The only way I can see to solve your problem is to include multiple sets of Filtered Picklists (either on the Item Details page or the Grid tab).

[Anonymous]

"...it means that you can make a selection in the various fields with no particular order..."

Huh, I hadn't realised that! Now you have me pondering how I could take advantage of this feature other than your example. Food for thought.

Thanks for your detailed response, I'll have a go with the grid tab option route instead, as I think that'll be the next best thing.

Cheers