I had so many support complaints about this I likely have to use a different form builder, or roll my own JS hack, to avoid this next event (June). It's skewing our data (this is a type of survey).
Comment actions
Post
Follow
Price field type needs to accept (not invalidate) more input options
Hi team,
I submitted this to support (ticket 547312) who said it's normal expected behaviour. Two things:
1) It's daft, see below
2) You need a feedback loop in your support processes where things that are pointed out as stupid actually get escalated for review, rather than just closed with "that's the way it is". I've had so many of this category over the years, it's really tedious to have to jump in and create feature requests every time.
Scenario:
We have a custom object form linked to a Price field, that's not accepting price values properly.
Price field on custom object form embedded in an OntraPage (separate issue about needing OntraPages for COs). Not sure if this happens on Contacts too, haven't tested.
Input Scenarios & Outcomes:
Input $500,000 fails
Input 500,000 fails
Input 500000 works
Expected Behaviour:
They should all work.
Please sign in to leave a comment.
1 comment