Skip to main content

Hi! I would like to have a feature similar to the “data validation” one in Excel/Sheets, where you can choose beforehand either to reject the input completely or show a warning. 

I will explain with some use cases: 
 

  • An Id number that has to have 8 digits
  • A date field that can’t be set in the future
  • A string that follows this schema: a letter, 7 numbers, and another letter: X0000000X.

We can set controls afterwards, like rules and CTAs asking them to update it properly, but it would be much more efficient to avoid the problem altogether by avoiding human error.

Thank you,

 

Great idea. I can think of so many ways we could use this!

I would need to also add:

  • “Field cannot contain” and then setting the list of strings it cannot contain, i.e. @gmail.com 

Simply put, we would love to have “validation rules/logic” in place in Gainsight. This would allow admins to create a simple logic statement that either tests true or false. When applied to a field, it would enforce this logic, and require the input data to match before being allowed to save a record.

Salesforce had done a great job of creating this feature already

I have another case to use as an example:
Users need to select a value from 1 to 5 via a “dropdown”. However, to enable real-time average calculations across multiple fields with this identical structure for display in C360 (using an advanced formula), the input cannot be a standard dropdown because the values are stored as strings.

There's no built-in mechanism to prevent user input errors.

That feeling when you already voted.

However… new comment. Would love to have something that refused to accept strings in all caps.

Not a good look to say: “Hi BOB, hope you’re doing well.”

Similarly, to have something for strings that says “can’t all be lowercase.”

That feeling when you already voted.

However… new comment. Would love to have something that refused to accept strings in all caps.

Not a good look to say: “Hi BOB, hope you’re doing well.”

Similarly, to have something for strings that says “can’t all be lowercase.”

100% yes! 
And sweet sweet tooltips (hopefully, auto-created from the field restrictions themselves and not by manually updating any C360 where those fields exist), to guide the end users. A gal/pal/person can dream, right? 

Ahhh, yes ​@romihache – tooltips and Gainsight user PX. 🙏

That’d be so, so nice.

Also: an integer field can only have values comprised between 0 and 5. 

Terms & ConditionsCookie settings