HubSpot should allow admins to define a different set of required properties based on the pipeline a deal or ticket is created in. This will help ensure tha tthe correct data is being added to the CRM.
Example: For deals created in pipeline A - require "deal amount" to be populated For deals created in pipeline B - require "local currency" to be populated
Hi everyone! The feature "Customize 'Create record' form by pipeline" is in public beta, which means that customers can opt themselves in under Product Updates > Betas. Note that it is Pro+, all hubs.
If you have feedback about this feature or related functionality you'd like to see, please fill out this form. We're actively looking for input to shape our roadmap and may reach out to respondents with follow-up questions. Thank you in advance!
👋Hi all! An update for you - we are now in private beta for a feature that will enable you to customize the ‘Create record’ form by deal, ticket, or custom object pipeline. This means that different properties will be displayed on the ‘Create record’ form depending on which pipeline a user selects.
Your CSM can request access to this beta on your behalf. We plan to move this feature to public beta in the near feature based on usage and customer feedback, at which point customers will be able to opt in themselves. Thank you all for your feedback!!
Hi all, this functionality is now in design research! It was a long road to get to this stage - thanks for your patience during the lengthy radio silence.
We've cooked up several options for this functionality. Now it would be great to get input from you on what works best. If you'd be interested in sharing feedback on early prototypes, please fill out this questionnaire. Thank you in advance for your time!!
Hey all, I'm Jeff from the CRM Product team. Don't blame @Dylan for the radio silence - blame me!
Happy to share that we are working towards support for this. There are several hurdles in our way to doing it right, we'll deliver it when it's ready.
We don't have an idea status that properly covers this stage, but it's gone beyond planning. It's on the list, and I'm looking forward to bringing it to you in the future.
Still cannot offer a firm timeline, I hope you'll understand at this point predicting a release date is not possible. Please keep the use cases and requests coming. Thank you all!
I wanted to post a quick update on the status of this idea.
As of right now, we do not have an ETA for delivering this functionality. We have a good understanding of the pain you all experience by not having this functionality and absolutely plan to address this idea. In fact, it's been something we've had several lengthy discussions about internally. The solution we're considering at this time is rooted in a significant change to our platform - allowing all properties (in this case, deal pipeline) to have other properties that are required depending on the original property chosen. It is certainly possible we take a more short-term approach to solve this specific problem, but at this stage our efforts are focused on higher impact updates to the HubSpot CRM overall.
Your continued feedback is very helpful for our team to prioritize this idea, so keep the use-cases and comments coming! Either myself or a member of our team will update this idea once we have a better idea on delivery + timing specifics.
Thank you as always for your continued input, it helps us build a better product.
Hey @carldavies1 - thank you for following up! We haven't made any significant progress on this quite yet, but it's something we're working towards with a series of other changes (like dependent properties for all objects and properties) with the hope that we can solve several big issues in a single release.
I don't have any clarity on timing there, but it's certainly something on our minds and being discussed. I'll follow up on this issue as soon as we have some progress...and likely will reach out personally for some input on our concepts!
We have 2 pipelines - one for e-commerce and one for normal sales. Both need very different properties to be filled out when the deal is created. This does seem like something quite basic that should be in the CRM already.
I wanted to post a quick update on the status of this idea.
As of right now, we do not have an ETA for delivering this functionality. We have a good understanding of the pain you all experience by not having this functionality and absolutely plan to address this idea. In fact, it's been something we've had several lengthy discussions about internally. The solution we're considering at this time is rooted in a significant change to our platform - allowing all properties (in this case, deal pipeline) to have other properties that are required depending on the original property chosen. It is certainly possible we take a more short-term approach to solve this specific problem, but at this stage our efforts are focused on higher impact updates to the HubSpot CRM overall.
Your continued feedback is very helpful for our team to prioritize this idea, so keep the use-cases and comments coming! Either myself or a member of our team will update this idea once we have a better idea on delivery + timing specifics.
Thank you as always for your continued input, it helps us build a better product.
Are there any new updates regarding this feature? Indeed, as was stated many times already, this feature would be really useful and greatly improve our way of working with HubSpot.
Hubspot missing out on increased revenue since this still isn't done. I have renewed my subscription for my own department but the rest of the company doesn't want to join since we'd be fighting to much on which fields to make mandatory since completely different sales Products and Cycles.
Our specific use case has 2 pipelines: one for sales and one for outreach to investors. Operated by two different teams and two completely different characteristics of the pipeline and deals within them.
We've made some fields required upon deal creation for the Sales team, as otherwise half of the stuff never gets submitted. But as an expected consequence, the team targeting Investors is up in arms because they are now required to submit info that's nowhere near relevant for their deals.
I love how you're considering to fix this by implementing that some properties can be set to required based on a value chosen in another. I've got some use cases for that as well. First that comes to mind: Closed Lost Reason specification. If Closed Lost Reason was "went to competitor", make a specification field required: Which competitor?
I also have a lot of use cases for this function, the one that @Bob2245 said is also a great one that we have here too, but here's another one:
I have a field in which our sales team can choose where the deal came from, if it was via inbound, outbound, or a referral/indication, for indications for example I have 2 options, one for partners and another one for clients, and for those two, I also have another field for each one of them in which the team can say which client or partner referred that deal, and because I can't require this last field when the first one is chosen as client or partner indication, this info a lot of times doesn't get submitted, and i don't know which partner or client to thank for that indication
Definitely need this! We have three sales teams, each of which needs to collect different info when they enter a deal. It would make for a much better experience if Pipeline A showed A fields only, Pipeline B only showed the B fields. etc.
@Dylan - just following up since your last post in Oct 2020. We are struggling quite a bit without this feature. There are 3 different BU heads and as youd' imagine they have different sales pipeline. For last 2 yrs we have been managing with making fields non-mandatory as we add new pipelines. However this has resulted in significant loss of data completeness because unless fields are mandatory, sales team does not fill it. Can you please provide an update on IF at all this feature of having separate properties while creating new deals under separate pipelines be available ever?
Hi @Dylan , I came here to post this idea as well. It would be so great to have this kind of specification way. Any idea about when we have accessibility to do this?
