Skip to main content

Hi all,

Instead of using picklists for everything, I feel it’d be useful if we could limit the input range in integer fields.

Use case:

We are measuring stakeholder relationship influence with a 0-5 range. This value is used in a stakeholder relationship health calculation, and we consequently need them as integers, not picklist values.

Instead of using a picklist to force CSMs to pick a value between 0 and 5 R360 > People, and then having to use silly case statements in a rule to populate ANOTHER “hidden” integer field in our calculation, we’d like them to be able to just type in the number or use arrows to decrease or increase the previously set value without being able to go above or below the specified range.

Proposal:

Not sure why it’s not been requested before, haven’t found it anyway. 

Thanks!

A

 

I did! I submitted this one that is a bit more broader, and your use case is captured in the thread 😁

 

 

​@romihache and I can see I apparently was also inspired with the same request 3 months ago, even though I don’t recall having the need then 🤣 … 😶

 

Hi ​@revathimenon Can we merge this idea with ​@romihache ‘s idea: Ability to set input restrictions in different field types | Gainsight Community. Totally didn’t come up in search.

​@romihache and I can see I apparently was also inspired with the same request 3 months ago, even though I don’t recall having the need then 🤣 … 😶

 

 

LOL🤣

On it ​@alizee 

Idea merged into:

All the votes from this idea have been transferred.
Terms & ConditionsCookie settingsAccessibility statement