Skip to main content

Hey all

I logged a ticket about this a while back and flagged it within the beta but seen as it doesn’t seem to be getting traction, posting here as it’s one of those big blockers and hinderance in Dynamic JO:

Calculated fields don’t work on multi-select picklists (them again!!!). 

 

The challenge:

It’s pretty frequent for multi-select picklists to be used in Gainsight, to qualify / assign roles to contacts (for example). 

It’s equally frequent to want to tailor a message or an experience based on that person belonging to a role or another.

But it’s impossible to do so (without lengthy queries converting multi select picklist into boolean attributes - WHY would I have to go through that pain unless maybe we can have an auto conversion of multi-select picklist to booleans?)

It’s also tricky to use an EQUALS operator as will it take the GSID for that value of the display name? Guessing GSID and then we go down the eternal annoyance of figuring out GSIDs for dropdown values. 

The need: 

Multi-select picklists need to be supported as evaluation criteria in calculated fields. That’s it. That’s the ask.

 

#themultipicklistsong @darkknight 😅

Yep, I totally agree. 
This limitation has become a blocker to us being able to launch a program. 
I’m surprised this even is a limitation - seems like they should be able to support all field types as filter criteria...


The challenge:

It’s pretty frequent for multi-select picklists to be used in Gainsight, to qualify / assign roles to contacts (for example). 

It’s equally frequent to want to tailor a message or an experience based on that person belonging to a role or another.

But it’s impossible to do so (without lengthy queries converting multi select picklist into boolean attributes - WHY would I have to go through that pain unless maybe we can have an auto conversion of multi-select picklist to booleans?)

The need: 

Multi-select picklists need to be supported as evaluation criteria in calculated fields. That’s it.

 

A year (plus) later, and this is still an issue. Why?

Thanks to ​@kstim for brainstorming with me today to build out a YAW (yet another workaround) to solve this issue to allow us to send different email templates in a dynamic JO program.

Our challenge

Based on whether a customer can (or cannot) receive live link HTML emails, send a different template. Requirements/specs: event based source, communication type brought in as a calculated field (so can’t filter a single template with versions since email version filters don’t support calculated fields). Our communication type field is a picklist.

Our solution

Create a new field (Boolean) powered by a rule for “Is HTML Live Links”. Now to hope. 🤞


That term “YAW” needs to become a hashtag