Convert a Slush-bucket Field to a Multiple Checkbox Option

[KD Sheridan]

Hello! When we launched SPM, we had included a few slush-bucket fields in our Demand Form. Now, we're thinking of moving those fields to a multi-select checkbox option. We're finding the inability to edit the slush-bucket fields in the list view are cumbersome, but more importantly the behavior for 'show matching' and 'contains =' in the filter view aren't displaying the expected results. 

Looking for advice and feedback from moving away from slush-bucket fields, or any lessons learned in filtering the data while using slush-bucket fields. 

Thank you!

[Uncle Rob]

May need to look at more advanced data structure like a many-to-many table.
In plain language, what are these slush-bucket fields currently storing?

[KD Sheridan]

I was beginning to wonder that myself. We are using them for multi-select impacts, such as technologies, other projects, etc. Thanks!

[Uncle Rob]

The more utility & reportability you need out of that kind of data, the more you need to consider table relationships.  There is a concept of a many-to-many:  "one of these can have many of those, and one of those can have many of these". 

Great example is the group memberships table.  Its a table that stores a reference to a group and a reference to a user on a single record.  Because you have it stored in the table you can do reports or even business logic.  "How many users are in groups where group type is itil" OR "when a user is inactivated, look up all the group membership records for that user and delete them"

You may want to consider that this data is better suited to "many to many"
Here's a video I did explaining how to build it....
https://youtu.be/yJttdDa-9xU

[KD Sheridan]

Thank you so much! I will look into this 🙂