La communauté HubSpot est disponible en français.

Pipeline specific Default Deal Properties

Hello Team, 

 

Our use case:

We have various pipelines, for various sales cycles and sometimes various types of contacts or companies.

The Deal's information we need to access depend on the pipeline the deal is in. Since the "default deal properties" is made to display the "most important" information of a deal, we need this group of "most important" information to be pipeline specific.

 

Our suggestion:

To propose to create multiple "default deal properties", each one having a name. Then, admin should be able to decide to which pipeline to apply this "default deal properties". A "default deal properties" may be applied to one or more pipelines. It's ok to have a limit on the possible numbers of possible "default deal properties" if needed. 10 or 20 maximum would already be amazing.

 

Note: I've written the above with the understanding that "default deal properties" are controlling both the "about" section on the deal and the properties available when creating a new deal on the card that's opening on the right of the screen.

 

Best, 

Adrien

HubSpot updates
Pipeline specific Default Deal PropertiesModérateur
10-16-2019

Hi Tim, 

 

When combing through the thread, I did notice this to be about 30% of the case that was mentioned. Unfortunately, this is not part of the update I posted about above but it is firmly on our radar. 

 

We are beginning to kick off work on that front (creating deals) but I felt as if the majority of the asks here were around the data that displays on Deals. We're well aware of the case for conditional required properties based on a pipeline an object is created in and will update this thread (or another, if it pops up) once we have that in a beta! 

Thanks as always for your continued feedback on our product 

 

- Dylan

 

Pipeline specific Default Deal PropertiesModérateur
changed to: Delivered
10-16-2019

Hi HubSpot Community,

Thank you for your continued feedback and input on the Community. I'm excited to update this post to "delivered", as of today we have introduced the ability to display conditional data on records into beta. Here is a knowledge doc that explains the capability.

 

In short, Professional users can now add customizable sections to their records; Enterprise users can customize what displays on records depending on the team a user is on or a property on the object (ex: pipeline). This update also comes jam-packed with property updates, such as the ability to delete or regroup HubSpot Default Properties. 

 

We'll have a more detailed product blog post coming soon, but I wanted to personally let all of you on the community know first!

If you're interested in using this functionality - navigate to "properties" within settings. If you are a Super Admin you will see a toggle in the bottom left hand corner that will allow you to unlock the new experience. We hope to make continued improvements to this experience before rolling it out more broadly as the defacto experience. 

As always, thank you for your continued feedback. Here on HubSpot Product we're always eager to improve your experience to help your business grow better! 

 

- Dylan Sellberg
Product Manager

Pipeline specific Default Deal PropertiesModérateur
06-13-2019

Hi HubSpot Community,

We really appreciate the continued feedback on this post. Allowing pipeline specific deal properties is certainly something we hope to look in to. However, at this stage the work has not been planned or scheduled. Please continue to provide examples and use-cases for this feature - it will help us build a better solution when the time comes. We'll update this post when we have further clarity on when we plan to build this functionality. 

 

- Dylan

Pipeline specific Default Deal PropertiesModérateur
10-21-2018

Hi HubSpot community - thank you all for providing your feedback on this issue. I'm a member of our Product team and I wanted to let you all know that this is something we are actively thinking about and hope to deliver soon! Please continue to provide examples and use-cases on this issue, I will provide an update once this functionality is closer to beta. 

87 Commentaires
timjobpal
Nouveau contributeur

Hi Dylan,

 

Thanks for the update — the newly introduced features are great!

 

However (I hope I'm wrong…), this does not at all address the issue of required properties when creating a Deal? This was a core part of this thread.

 

Best,

Tim

SimoneM
Contributeur régulier

Yeah it's a great feature, but the really nice things like custom properties view and dependent section, are only on Enterprise... and in any case seems that you still can't manage custom properties at the moment of creations of a new deal.

 

Simone

Modérateur
Modérateur

Hi Tim, 

 

When combing through the thread, I did notice this to be about 30% of the case that was mentioned. Unfortunately, this is not part of the update I posted about above but it is firmly on our radar. 

 

We are beginning to kick off work on that front (creating deals) but I felt as if the majority of the asks here were around the data that displays on Deals. We're well aware of the case for conditional required properties based on a pipeline an object is created in and will update this thread (or another, if it pops up) once we have that in a beta! 

Thanks as always for your continued feedback on our product 

 

- Dylan

 

timjobpal
Nouveau contributeur

That's great to hear, thank you!

VagaeNatus
Conseiller

@Dylan I am the original creator of this idea, more than 2 years ago. I think it is not right to say this idea is delivered. Below are three reasons why. Hence, could you please change the status back to submitted or something like working on? Here is why:

 

1/ It's Beta, not in Live: The concept of beta means it can still be stopped and never go live or can be changed.

2/ It does not cover the scope of the idea: The feature delivered does not cover new deals, which was part of the original idea (check it one more time). Hence, the feature did not deliver the idea, only a part of it. As such, please do not send to garbage the 200+ upvotes of people over 2 years by marking the idea delivered. Many also voted for the new deal components and for them it's not delivered.

 

Apart from the above facts, it's surprising no one has contacted me from Product Team at Hubspot. A few months after posting the first idea, I mentioned what you needed to develop was actually equivalent to Salesforce Record Type. But you kept focusing on an idea that was 2 years old. We would have liked to make the conditions based on something else than the pipe, we did not get it.

 

JPowell1
Contributeur régulier

I agree this hasn't really been delivered. Properties are still created for all pipelines and only those with enterprise packages can implement a workaround.

 

It's really frustrating to be given a partial solution and see pretty basic functionality added for enterprise customers only (because there is a demand for it, you have to assume).

shancbailey
Nouveau contributeur

I wish that having properties by pipeline wouldn't be only available to enterprise users; It feels like this is basic functionality that should come with having the ability to have multiple pipelines (and atleast be available to professional users).