Skip to main content
Question

Rule Engine - Rich Text field not showing in the Criteria field list

  • January 28, 2026
  • 7 replies
  • 58 views

Hello, 

we are setting a rule to trigger CTAs when we get an NPS Detractor and that survey response has comments.

As for now, our NPS Survey is coming from an external source and the Improvement (Comments) field is a rich text one.

When preparing the rules the dataset has all information we need :

 

 

But when going into the criterias, the improvement (comment) field is not showing, everything else is.

HTML has already been disabled.

Is there a workaround?

7 replies

  • Gainsight Community Moderator
  • January 28, 2026

Hi ​@cinquecristina ,

You can convert the Rich Text Field to String. Follow these steps:

  1. Perform a transform on your Dataset.
  2. Click on ‘Add Formula Field’
  3. Give a name to the field, choose Data Type as ‘String’.
  4. Choose the function as ‘To String’, put in the Rich Text Field.

 This would create the Rich Text field into a String Type and you’ll be able to use it in criteria while creating a rule action.

Thanks!


  • Author
  • Contributor ⭐️⭐️
  • January 29, 2026

@Yogita thank you so much this is super helpful!

One question, when I am setting the function it asks me to add a Value, should I put the same name of the field (field is called improvement (comment))?

Thank you so much!


romihache
Forum|alt.badge.img+9
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • February 2, 2026

@Yogita thank you so much this is super helpful!

One question, when I am setting the function it asks me to add a Value, should I put the same name of the field (field is called improvement (comment))?

Thank you so much!

Jumping in here. That last argument is a default value in case the transformation fails (null input), you have to input a string of your chosing like X or if you want to keep it null, just type null

@Yogita who is the best person to alert regarding documentation updates? Users are being stuck because:

· Rules Engine Doc The formula isn't listed here at all, despite being supported.
· Data Designer Doc: The formula is listed, but the value argument is left unexplained. We learned the null “trick” based on trial and error, as it isn't documented as a valid option.


  • Gainsight Community Moderator
  • February 2, 2026

Hi ​@romihache ,

Glad to know you worked this out!
For feedback - you can share it with your CSM and they will pass it along to our Documentation Team. For now, I’ve made a note of this, and will share the feedback with them. 

Thanks!


romihache
Forum|alt.badge.img+9
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • February 2, 2026

Hi ​@romihache ,

Glad to know you worked this out!
For feedback - you can share it with your CSM and they will pass it along to our Documentation Team. For now, I’ve made a note of this, and will share the feedback with them. 

Thanks!

Thank you ​@Yogita, I’m sending this to our CSM and will keep it in mind moving forward. 


romihache
Forum|alt.badge.img+9
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • February 2, 2026

@Yogita 
Adding some context: the only documentation I can find in Gainsight Go is tucked under the Bionic Rules directory. The resources are significantly outdated; the migration to Horizon dates back to ‘22, yet I can’t find a relevant article for Horizon Rules at all:
 


For Bionic, there are 17 articles listed, for Horizon, 8.
 


  • Gainsight Community Moderator
  • February 4, 2026

Hi ​@romihache 

Thanks for the context. The feedback has been shared with our documentation team!

Thanks!