In Forms when you set a field to be validated as Numeric, it would be nice to be able to show a field based on the number being =, >, <, <>, ⇐, >=.
I have seen questions on this, but couldn't find a submitted idea.
Sign in to see the current vote count, add your own vote, or leave a comment.
I'm trying to create a project intake form, and we have a policy that projects over a certain dollar amount require an additional approval step. I've set up the field to accept numbers only in the form and formatted it to USD$ currency in the sheet, but the only options for conditional logic in the form are for "contains, does not contain, blank, not blank." There is no option to trigger a follow-up question if the number is greater than a defined value.
I asked this as a question in another thread, and this is not a current feature, but I can imagine others would also like to have this functionality.
@Iowa.KatelynH While you may not be able to trigger a follow up question if the entered number is above a certain threshold, your comment about an "additional approval step" may be covered by an approval automation workflow that triggers based on the number being submitted (if your approval process is managed in SS).
Hi, I was creating new dashboard and thought it'll be so nice to have easy drag and drop Report widget capability from Workspace Panel since I always group set of reports under one folder (for ease of finding them what goes on the dashboard). I think this would be great time saver especially if you have similar name…
In the Resource Management Plan Settings in Control Center, there is no way to link the Client and Project Code fields even though they are not Custom fields and part of the first 3 fields you enter when creating a new project. I can't select them in the Custom Resource Management Information Fields because they are not…
Since the license model has changed, the option to Share should default to VIEW, not EDIT. The View option allows less-experienced users to share that way by default, and share as Edit only when needed. This allows for less cleanup during true-up. This also prevents users from adding provisional licenses unknowingly.
