# Pipeline with conditional mandatory properties **URL:** \ **Category:** HubSpot Ideas\ **Tags:** reports, object\ **Created:** [June 15, 2021, 2:57pm UTC](https://community.hubspot.com/t/pipeline-with-conditional-mandatory-properties/38953 "2021-06-15T14:57:15Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![EmaRuiz](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/emaruiz/32/62605_2.png) [@EmaRuiz](https://community.hubspot.com/u/EmaRuiz)\ **Post date:** [June 15, 2021, 2:57pm UTC](https://community.hubspot.com/t/pipeline-with-conditional-mandatory-properties/38953/1 "2021-06-15T14:57:15Z")
It would be nice that within the pipeline flow we could place mandatory properties as it can be done today but that depend on another property, if I have a customer that I know visits my branch, the date is mandatory but if he does not visit it, it is not, for instance ---
**Author:** ![LeonardoV](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/leonardov/32/99678_2.png) [@LeonardoV](https://community.hubspot.com/u/LeonardoV)\ **Post date:** [July 7, 2021, 3:16pm UTC](https://community.hubspot.com/t/pipeline-with-conditional-mandatory-properties/38953/2 "2021-07-07T15:16:50Z")
Its a good idea, we are look for a similar solution. ---
**Author:** ![Robse89](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/robse89/32/35926_2.png) [@Robse89](https://community.hubspot.com/u/Robse89)\ **Post date:** [July 18, 2021, 8:59pm UTC](https://community.hubspot.com/t/pipeline-with-conditional-mandatory-properties/38953/3 "2021-07-18T20:59:15Z")
nice! we also look für a solution! ---
**Author:** ![matheusjiran](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/matheusjiran/32/12336_2.png) [@matheusjiran](https://community.hubspot.com/u/matheusjiran)\ **Post date:** [July 26, 2021, 9:11pm UTC](https://community.hubspot.com/t/pipeline-with-conditional-mandatory-properties/38953/4 "2021-07-26T21:11:33Z")
Great suggestion! Another use case would be: If “Requires PO Number for Billing” is ‘Yes’, then make “PO Number” mandatory. And there is a significant number of times I found business needs that would be simply covered by this conditioning but had to say it couldn’t be done. ---
**Author:** ![JGeorge9](https://avatars.discourse-cdn.com/v4/letter/j/7ab992/32.png) [@JGeorge9](https://community.hubspot.com/u/JGeorge9)\ **Post date:** [June 27, 2022, 3:29pm UTC](https://community.hubspot.com/t/pipeline-with-conditional-mandatory-properties/38953/5 "2022-06-27T15:29:22Z")
Any update on this request? We have a similar need where field-2 needs to entered only when a particular option is selected in the field-1. Any color if very much appreciated. ---
**Author:** ![tmitch\_sona](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/tmitch_sona/32/59778_2.png) [@tmitch\_sona](https://community.hubspot.com/u/tmitch_sona)\ **Post date:** [January 17, 2023, 6:40pm UTC](https://community.hubspot.com/t/pipeline-with-conditional-mandatory-properties/38953/6 "2023-01-17T18:40:55Z")
Yes please to this. Would make a lot of people here very happy and less stressed 😅 ---
**Author:** ![JRoux4](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jroux4/32/22307_2.png) [@JRoux4](https://community.hubspot.com/u/JRoux4)\ **Post date:** [May 9, 2023, 3:56pm UTC](https://community.hubspot.com/t/pipeline-with-conditional-mandatory-properties/38953/7 "2023-05-09T15:56:15Z")
This feature is much needed. I hope you’ll add it to your product roadmap soon ---
**Author:** ![bryceanelson](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/bryceanelson/32/62359_2.png) [@bryceanelson](https://community.hubspot.com/u/bryceanelson)\ **Post date:** [May 24, 2023, 5:17pm UTC](https://community.hubspot.com/t/pipeline-with-conditional-mandatory-properties/38953/8 "2023-05-24T17:17:50Z")
Agreed - we have a pretty diverse business and different pipelines to match. There are many properties that are only important on certain conditions and I don’t want to ask for property updates if those conditions aren’t met, it would be way too many. ---
**Author:** ![tcxen](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/tcxen/32/99782_2.png) [@tcxen](https://community.hubspot.com/u/tcxen)\ **Post date:** [July 26, 2023, 12:05am UTC](https://community.hubspot.com/t/pipeline-with-conditional-mandatory-properties/38953/9 "2023-07-26T00:05:38Z")
This would be a game changer. ---
**Author:** ![JSteer](https://avatars.discourse-cdn.com/v4/letter/j/3ab097/32.png) [@JSteer](https://community.hubspot.com/u/JSteer)\ **Post date:** [August 2, 2023, 3:13pm UTC](https://community.hubspot.com/t/pipeline-with-conditional-mandatory-properties/38953/10 "2023-08-02T15:13:55Z")
Get this done ASAP. ---
**Author:** ![phst](https://avatars.discourse-cdn.com/v4/letter/p/57b2e6/32.png) [@phst](https://community.hubspot.com/u/phst)\ **Post date:** [September 6, 2023, 2:25pm UTC](https://community.hubspot.com/t/pipeline-with-conditional-mandatory-properties/38953/11 "2023-09-06T14:25:29Z")
This would be really helpful! We currently use quite a lot of non-mandatory properties, but this is not user-friendly and we have no control over how we enforce data entry. ---
**Author:** ![AGerrard0](https://avatars.discourse-cdn.com/v4/letter/a/5f9b8f/32.png) [@AGerrard0](https://community.hubspot.com/u/AGerrard0)\ **Post date:** [November 9, 2023, 7:14pm UTC](https://community.hubspot.com/t/pipeline-with-conditional-mandatory-properties/38953/12 "2023-11-09T19:14:59Z")
We also have a use case for this idea. We only want properties to be required in the pipeline if another property meets criteria. ---
**Author:** ![GMcDaniel7](https://avatars.discourse-cdn.com/v4/letter/g/d78d45/32.png) [@GMcDaniel7](https://community.hubspot.com/u/GMcDaniel7)\ **Post date:** [January 23, 2024, 4:11pm UTC](https://community.hubspot.com/t/pipeline-with-conditional-mandatory-properties/38953/13 "2024-01-23T16:11:44Z")
Following up on this as it’s a feature that has been requested for almost three years. HubSpot team - is this on the feature road map? ---
**Author:** ![shyrahnama](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/shyrahnama/32/69256_2.png) [@shyrahnama](https://community.hubspot.com/u/shyrahnama)\ **Post date:** [February 29, 2024, 8:53pm UTC](https://community.hubspot.com/t/pipeline-with-conditional-mandatory-properties/38953/14 "2024-02-29T20:53:19Z")
How has this not been done yet? Feels like very basic CRM configurability. ---
**Author:** ![beckylimina](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/beckylimina/32/83873_2.png) [@beckylimina](https://community.hubspot.com/u/beckylimina)\ **Post date:** [April 15, 2024, 9:00am UTC](https://community.hubspot.com/t/pipeline-with-conditional-mandatory-properties/38953/15 "2024-04-15T09:00:44Z")
Just adding to see if there’s been any movement on this at all given the idea was submitted nearly 3 years ago! ---
**Author:** ![TalKalderon4](https://avatars.discourse-cdn.com/v4/letter/t/96bed5/32.png) [@TalKalderon4](https://community.hubspot.com/u/TalKalderon4)\ **Post date:** [June 6, 2024, 8:46am UTC](https://community.hubspot.com/t/pipeline-with-conditional-mandatory-properties/38953/16 "2024-06-06T08:46:08Z")
Still very needed, our whole business is based on different pipelines. We should be able to use diverse conditional logic. ---
**Author:** ![ErikaJ](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/erikaj/32/2401_2.png) [@ErikaJ](https://community.hubspot.com/u/ErikaJ)\ **Post date:** [October 17, 2024, 7:53pm UTC](https://community.hubspot.com/t/pipeline-with-conditional-mandatory-properties/38953/17 "2024-10-17T19:53:01Z")
This logic would be incredibly useful and significantly reduce the number of complicated duplicate pipelines that need to be created/used just to include a required field under a certain condition. It seems fairly simple given all of the other places we can now set up Conditional Fields. i.e. if Billing Frequency is Monthly then require Monthly Payment Amount at the Contract stage. If the Billing Frequency is Annual, then don’t show the Monthly Amount field. ---
**Author:** ![gcollette](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/gcollette/32/58551_2.png) [@gcollette](https://community.hubspot.com/u/gcollette)\ **Post date:** [April 15, 2025, 6:27pm UTC](https://community.hubspot.com/t/pipeline-with-conditional-mandatory-properties/38953/18 "2025-04-15T18:27:37Z")
Adding another comment for visibility. Depending on the service line, we have different information that’s required at different stages. ---
**Author:** ![SaritaUrban](https://avatars.discourse-cdn.com/v4/letter/s/838e76/32.png) [@SaritaUrban](https://community.hubspot.com/u/SaritaUrban)\ **Post date:** [April 22, 2025, 10:31am UTC](https://community.hubspot.com/t/pipeline-with-conditional-mandatory-properties/38953/19 "2025-04-22T10:31:24Z")
Adding another comment for visibility. This has been a blocker for us. ---
**Author:** ![RFio123](https://avatars.discourse-cdn.com/v4/letter/r/e0b2c6/32.png) [@RFio123](https://community.hubspot.com/u/RFio123)\ **Post date:** [July 29, 2025, 1:06am UTC](https://community.hubspot.com/t/pipeline-with-conditional-mandatory-properties/38953/20 "2025-07-29T01:06:23Z")
How does this not exist? We sell to multiple personas, and the information we need to know for those different personas differs meaningfully. Using separate pipelines doesn’t work because we don’t know until after the first call