Ability to set input restrictions in different field types

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, so the field is an integer.

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

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.