Skip to main content
alizee
VIP ⭐️⭐️⭐️⭐️⭐️
February 14, 2025
New Idea

Store failure reasons as string (instead of rich text) in AO Failed Participants (and anywhere else)

Related products:CS Journey Orchestrator
  • February 14, 2025
  • 6 replies
  • 97 views

Hi there

I need to analyze some data around participant failure reasons and ô surprise, I can’t do that within Gainsight because that value, which is a couple of dozen characters max, is stored as rich text.

Which means:

  • Can’t search
  • Can’t filter
  • Can’t group by

In short: can’t use.

Meanwhile, Failure Reason in AO Participants is a string that we can search through, can filter on and can group by.

This is inconsistent and doesn’t add up.

It needs to be a string everywhere. If it can be in AO Participants, IT CAN ALSO BE in AO Failed Participants.

A

 

6 replies

romihache
VIP ⭐️⭐️⭐️⭐️⭐️
February 14, 2025

#Parity please!

Continuous improvement is better than delayed perfection
dayn.johnson
VIP ⭐️⭐️⭐️⭐️⭐️
February 14, 2025

… Failure Reason in AO Participants is a string that we can search through, can filter on and can group by. This is inconsistent and doesn’t add up.

It needs to be a string everywhere.

If it can be in AO Participants, IT CAN ALSO BE in AO Failed Participants.

This seems like a massive oversight, and yet another case of lacking #productparity. ​@revathimenon, ​@Kenneth R, can we get some product owner eyes on this?

Staff CS Content & Comms Manager, 2x Gainsight CS Ops Product Council Member
alizee
alizeeAuthor
VIP ⭐️⭐️⭐️⭐️⭐️
February 17, 2025

Support has informed me that what I thought to be “RICH TEXT” is “JSONSTRING”. Great - because they are not visually different from each other in the UI, and THEY SHOULD. 

​@rakesh This looks like an oversight on the design side, as two similar objects and fields using different data types to store that Failure Reason field doesn’t make sense, and this is creating an additional burden on the admin side (exporting to Excel or converting that into a DD when we should normally just be able to stay within a report). Is AI going to solve this soon, or are there plans to make changes to the MDA to achieve the required consistency? 

The most expensive part of building is the mistakes. That's true in construction. Not so much in CSOps. So ask questions, make mistakes and learn. All views expressed here are my own.
revathimenon
Gainsight Community Lead
February 18, 2025

On it ​@dayn.johnson 

Where focus goes, energy flows.
vmallya
Gainsight Employee ⭐️
Gainsight Employee ⭐️
February 21, 2025

Thanks for sharing this. This design comes from the old version but I will keep this in mind as we are evaluating improvements for JO reporting.

Vijay | PM | JO | Gainsight
alizee
alizeeAuthor
VIP ⭐️⭐️⭐️⭐️⭐️
February 21, 2025

Thanks for sharing this. This design comes from the old version but I will keep this in mind as we are evaluating improvements for JO reporting.

Thanks for clarifying that this has been inherited from old JO ​@vmallya. Hope to see parity in the near-ish future (although we both agree there are more exciting things coming). 

The most expensive part of building is the mistakes. That's true in construction. Not so much in CSOps. So ask questions, make mistakes and learn. All views expressed here are my own.