Skip to main content
New Idea

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

Related products:CS Journey Orchestrator, Email & Notifications
  • February 14, 2025
  • 6 replies
  • 66 views
  • johntrask_bt
    johntrask_bt
  • DannyPancratz
    DannyPancratz
  • Sam77
    Sam77
  • Deja

alizee
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • 649 replies

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
Forum|alt.badge.img+8
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • 420 replies
  • February 14, 2025

#Parity please!


dayn.johnson
Forum|alt.badge.img+6
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • 636 replies
  • February 14, 2025
alizee wrote:

… 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?


alizee
Forum|alt.badge.img+11
  • Author
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • 649 replies
  • 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? 


revathimenon
Forum|alt.badge.img+6
  • Gainsight Community Manager
  • 565 replies
  • February 18, 2025

On it ​@dayn.johnson 


vmallya
Forum|alt.badge.img
  • Gainsight Employee ⭐️
  • 48 replies
  • 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.


alizee
Forum|alt.badge.img+11
  • Author
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • 649 replies
  • February 21, 2025
vmallya wrote:

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). 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings