Required Fields for Opportunities
complete
I
Idan zivon
It would be extremely helpful to have the ability to define required fields at the Opportunity level.
Suggested functionality:
Allow to mark specific Opportunity custom fields as required.
Option to define required fields per pipeline.
Option to define required fields per stage.
Prevent saving or moving an Opportunity to the next stage until all required fields are completed.
Display a clear validation message indicating which fields are missing.
Log In
P
Pallavi Kothari
updated the status to
complete
Hi
Thanks for upvoting this idea - its now live
Please try it out and share your feedback
M
Michael Garcia
Hi Pallavi Kothari, thank you! I’ve tried it out, and the feature is very helpful.
One thing that would make it even more useful is if the current limitations could be increased. Right now, it’s limited to 10 conditional logic rules, with up to 5 custom fields per conditional logic.
If you could increase these limits, it would be a big help for more complex Opportunity setups where we need more conditional fields.
A
Alex Moyies
Michael Garcia I completely agree, it is a fantastic feature but the limitations do not allow for much complexity. It is too restrictive.
J
Jake Padiernos
Hi Pallavi Kothari,
thank you for releasing this feature. It’s very helpful, but we noticed an issue with conditional fields when creating an Opportunity.
If a field has conditional logic and there is no answer yet, the same field will appear twice. This happens consistently when creating a new Opportunity because the fields do not have any values yet at that point.
Ideally, the conditional field should only appear once. If the field is already displayed on the blue line/section, it should only remain there and should not show up at the bottom.
I understand that the system is simply pulling the same field when it appears on the blue line, but it is still being displayed twice, which can be confusing for users. We’ve also noticed that this can still happen even when there is already an answer in the field before clicking create.
It would be great if the system could recognize that the conditional field is already being displayed and prevent it from appearing twice when the field is unanswered.
Thank you! This would make the Opportunity creation process much cleaner and less confusing for users.
A
Austin Asplund
Currently this is my number 1 struggle. I need to be able to make certain fields required in order to keep data entry clean and standardized.
C
Cameron Thomas
I completely Agree!!!!