# Conditional Deal Stage Properties

**URL:** <https://community.hubspot.com/t/conditional-deal-stage-properties/52414>\
**Category:** HubSpot Ideas\
**Tags:** reports, properties\
**Created:** [March 2, 2022, 10:11am UTC](https://community.hubspot.com/t/conditional-deal-stage-properties/52414 "2022-03-02T10:11:41Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![SamuelBanks](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/samuelbanks/32/20710_2.png) [@SamuelBanks](https://community.hubspot.com/u/SamuelBanks)\
**Post date:** [March 2, 2022, 10:11am UTC](https://community.hubspot.com/t/conditional-deal-stage-properties/52414/1 "2022-03-02T10:11:41Z")

</div>

Hey HubSpot,  
We find great value in the “Update Deal Stage properties” feature in HubSpot to standardise data collection. However, there’s a challenge when we have deals that are going through our Pipeline/Process that warrant different data to be collected at the same stage.  
Currently we have two options,  
A) Which is to list out all fields and possibilities at that stage as “unrequired” which isn’t user-friendly  
B) Split out into separate pipelines which is drastic and affects forecasting (as you can only look at one pipeline at a time).  
**Summary**  
Without splitting this out into an identical, yet partitioned pipeline - we’d much prefer it to all sit in the same pipeline, but have functionality by saying if Deal Property is X, then show only Fields Y and Z at this stage.

---

<div class="post-metadata">

**Author:** ![abrow](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/abrow/32/92090_2.png) [@abrow](https://community.hubspot.com/u/abrow)\
**Post date:** [November 8, 2022, 3:38pm UTC](https://community.hubspot.com/t/conditional-deal-stage-properties/52414/2 "2022-11-08T15:38:30Z")

</div>

We are in desparate need of this as well.  
We have gone the route of:  
A) Which is to list out all fields and possibilities at that stage as “unrequired” which isn’t user-friendly  
And it is a nightmare! People simply skip fields that they should be filling out (because I can’t make them required, because in certain circumstances they shouldn’t be required).  
For us, we have a deal pipeline that contains all our upsells, downsells, and renewals. As you can imagine, when an upsell is ‘won’ you should fill out drastically different fields than if a renewal is ‘won’, and same for downsells. We end up with a large number of fields being displayed when a rep moves a deal to ‘won’ and they are prompted with so many fields that just don’t pertain to their deal at all, that they end up ignoring the fields that DO pertain to that deal plus filling out fields that DONT pertain to that deal. It’s a mess, and splitting out upsells, downsells, and renewal deals into a different pipeline would cause much more chaos in forecasting and usability too.

---

<div class="post-metadata">

**Author:** ![Ellesyanna](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/ellesyanna/32/55434_2.png) [@Ellesyanna](https://community.hubspot.com/u/Ellesyanna)\
**Post date:** [January 19, 2023, 10:56am UTC](https://community.hubspot.com/t/conditional-deal-stage-properties/52414/3 "2023-01-19T10:56:23Z")

</div>

Very much needed! Similar topics here: [https://community.hubspot.com/t5/HubSpot-Ideas/Dependent-fields-on-deals/idc-p/743868#M133034](https://community.hubspot.com/t5/HubSpot-Ideas/Dependent-fields-on-deals/idc-p/743868#M133034) & [https://community.hubspot.com/t5/HubSpot-Ideas/Pipeline-with-conditional-mandatory-properties/idi-p/447575](https://community.hubspot.com/t5/HubSpot-Ideas/Pipeline-with-conditional-mandatory-properties/idi-p/447575)

---

<div class="post-metadata">

**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:06am UTC](https://community.hubspot.com/t/conditional-deal-stage-properties/52414/4 "2023-07-26T00:06:02Z")

</div>

This would be a game changer.

---

<div class="post-metadata">

**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:14pm UTC](https://community.hubspot.com/t/conditional-deal-stage-properties/52414/5 "2023-08-02T15:14:20Z")

</div>

Get this done ASAP.

---

<div class="post-metadata">

**Author:** ![SamWadey](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/samwadey/32/38459_2.png) [@SamWadey](https://community.hubspot.com/u/SamWadey)\
**Post date:** [September 28, 2023, 1:47pm UTC](https://community.hubspot.com/t/conditional-deal-stage-properties/52414/6 "2023-09-28T13:47:57Z")

</div>

In desperate need of this feature.

---

<div class="post-metadata">

**Author:** ![Sophieecarrillo](https://avatars.discourse-cdn.com/v4/letter/s/b38774/32.png) [@Sophieecarrillo](https://community.hubspot.com/u/Sophieecarrillo)\
**Post date:** [October 2, 2023, 11:35am UTC](https://community.hubspot.com/t/conditional-deal-stage-properties/52414/7 "2023-10-02T11:35:49Z")

</div>

Completely agree - this is so needed!

Leaving them as unrequired is not ideal. We need conditional logic for conditional stage properties ASAP.

---

<div class="post-metadata">

**Author:** ![Edyta7510](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/edyta7510/32/89259_2.png) [@Edyta7510](https://community.hubspot.com/u/Edyta7510)\
**Post date:** [November 6, 2023, 2:03pm UTC](https://community.hubspot.com/t/conditional-deal-stage-properties/52414/8 "2023-11-06T14:03:11Z")

</div>

This is truly needed!

I’ve been thinking myself about setting a workflow that would automatically fill in these “unrequired” properties if my condition is unmet, but many of them are dropdown lists, etc; I can’t add NA as an option 😞

---

<div class="post-metadata">

**Author:** ![mangelet](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/mangelet/32/83031_2.png) [@mangelet](https://community.hubspot.com/u/mangelet)\
**Post date:** [November 7, 2023, 11:54am UTC](https://community.hubspot.com/t/conditional-deal-stage-properties/52414/9 "2023-11-07T11:54:05Z")

</div>

Hey there! I noticed some activity around this idea and thought I’d chime in on points A and B mentioned earlier.

First off, the option to create conditional properties is now available and out of beta. I think that’s what sparked this idea in the first place, right? You can check it out – here’s the link.

> **[Set up conditional logic for enumeration properties](https://knowledge.hubspot.com/properties/set-up-conditional-logic-for-enumeration-properties)**
>
> Set up conditional property logic to display or require additional properties when users select a specific value on enumeration or datetime properties.

Secondly, there’s another cool feature you might find useful. It’s called “Forecast Category.” What it does is let you group deal stages from different pipelines into categories. That way, you can see a consolidated forecast of all your pipelines. Here’s the link for that too.

> **[Set up the forecast tool](https://knowledge.hubspot.com/forecast/set-up-the-forecast-tool)**
>
> Learn how to set up and customize the forecast tool to track your sales team's progress and set forecastable revenue goals.

I wanted to share this info because I saw people discussing this issue, and also to check if these two features actually solve your problems.

So, what do you think? Are we all set with these updates, or is there still something else we need to tackle? Let me know!

---

<div class="post-metadata">

**Author:** ![Edyta7510](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/edyta7510/32/89259_2.png) [@Edyta7510](https://community.hubspot.com/u/Edyta7510)\
**Post date:** [November 7, 2023, 12:07pm UTC](https://community.hubspot.com/t/conditional-deal-stage-properties/52414/10 "2023-11-07T12:07:39Z")

</div>

Hi @mangelet , thanks for chiming in 😉

I am aware of the conditional properties, yes.

However, is it possible to apply them in a way that would meet what we need here?

As far as I know and based on my tests, I am able to set the following:

If deal property → deal stage = LEAD, ask for additional properties. However, there’s no way to make those additional properties that pop-up compulsory?

Perhaps I’m looking at this with a wrong filter

---

<div class="post-metadata">

**Author:** ![mangelet](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/mangelet/32/83031_2.png) [@mangelet](https://community.hubspot.com/u/mangelet)\
**Post date:** [November 7, 2023, 3:51pm UTC](https://community.hubspot.com/t/conditional-deal-stage-properties/52414/11 "2023-11-07T15:51:34Z")

</div>

Hey @Edyta7510 I think conditional properties could definitely help you out.

Let’s think of an example I just tested.

In a normal Sales Pipeline, at the Qualified stage, I’m asking for priority as required.

Now, the conditional logic works like this:

1️⃣ if the priority is low, I’m asking you to explain why you’d still want to move forward with this opportunity.

2️⃣ And if the priority is super high, I’m asking what your next action will be.

In both cases, I’m making these fields mandatory. So, if the priority is high, you must provide your next step; and if it’s low, you need to explain why you want to continue with this opportunity.

These required fields depend on the priority level, which means we’re dealing with fully conditional logic here.

I believe this would work well for your needs. What do you think?

If you’re thinking of a specific scenario and can describe it in detail, we can look into that too.

---

<div class="post-metadata">

**Author:** ![FPistorius](https://avatars.discourse-cdn.com/v4/letter/f/8e7dd6/32.png) [@FPistorius](https://community.hubspot.com/u/FPistorius)\
**Post date:** [April 3, 2024, 1:54pm UTC](https://community.hubspot.com/t/conditional-deal-stage-properties/52414/12 "2024-04-03T13:54:40Z")

</div>

This this something we are desparately needing as well! When different agreement types are selected for example, different properties are required to be completed and its gets meesy/cosnfusing when all properties are visible, but not required for a specific ageement.

---

<div class="post-metadata">

**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:01am UTC](https://community.hubspot.com/t/conditional-deal-stage-properties/52414/13 "2024-04-15T09:01:53Z")

</div>

There are various threads on this now and there’s been no movement on it for years, any chance of getting this delivered HubSpot?

---

<div class="post-metadata">

**Author:** ![JSPrenovost](https://avatars.discourse-cdn.com/v4/letter/j/c37758/32.png) [@JSPrenovost](https://community.hubspot.com/u/JSPrenovost)\
**Post date:** [April 17, 2024, 5:41pm UTC](https://community.hubspot.com/t/conditional-deal-stage-properties/52414/14 "2024-04-17T17:41:17Z")

</div>

EDIT : Nevermind, i figured out how to do it. It’s anything but intuitive. You need to make the conditional logic at the Deal form edit stage. Then when adding required properties in the pipeline conditional properties, the logic follows.

--------------------------------------------------------------------------------

In desperate needs of this.

In a specific deal stage, following the choiceion a dropdown menu, if a specific option is selected, it is required to upload a file to the deal to automate a ticket generation. That file upload doesn’t make sense for any other option in that dropdown menu. The other options all require different properties to be filled in. That’s just one additional use case on top of everything being said here.  
As mentionned, adding a NA field and leaving all propertties as required is less than ideal and it’s not something we want rto move forward with. Building different ppipelines is just not working for us. We would need 6 pipelines.

Isn’t it all about frictionless sales cycle? This condiotional logif feature within deal stages would remove a lot of friction…

---

<div class="post-metadata">

**Author:** ![FPistorius](https://avatars.discourse-cdn.com/v4/letter/f/8e7dd6/32.png) [@FPistorius](https://community.hubspot.com/u/FPistorius)\
**Post date:** [April 18, 2024, 9:03am UTC](https://community.hubspot.com/t/conditional-deal-stage-properties/52414/15 "2024-04-18T09:03:51Z")

</div>

@JSPrenovost please do share where I can find the ‘deal form edit stage’ - thank you!

---

<div class="post-metadata">

**Author:** ![JSPrenovost](https://avatars.discourse-cdn.com/v4/letter/j/c37758/32.png) [@JSPrenovost](https://community.hubspot.com/u/JSPrenovost)\
**Post date:** [April 18, 2024, 12:11pm UTC](https://community.hubspot.com/t/conditional-deal-stage-properties/52414/16 "2024-04-18T12:11:56Z")

</div>

@FPistorius ,

Create a new deal.

On top of that form there is the “edit this form” link. Click it.

Then on the left side, you have the option to add property dependancies based on values in a property. Create your dependencies there.

Then go to your pipeline settings and add contional properties at the desired stages. Your previously created dependancies will follow when moving in deal stages.

I hope this helps.
