La fonction de suggestion automatique permet d'affiner rapidement votre recherche en suggérant des correspondances possibles au fur et à mesure de la frappe.
We have created a Custom Object for Sales Tickets and use a pipeline BUT we are not able to make any properties mandatory unless its at the creation stage. We want to be able to make certain properties mandatory at certain pipeline stages.
For example, when the ticket goes to Closed, we have a Closed Reason section but this is being missed as it is not mandatory.
Great idea. To ensure that users comply with the process then you have be able to make fields mandatory. It is also extremely important for reporting purposes.
Was disappointed today to see that this isn't currently possible. It's getting a bit old to have to double back on what I tell customers is possible. I figured that when you added in pipelines for CO's, they'd be on par with pipelines for Deals, but come in to find that half of the features are taken out.
Have a major use case on a big client for this, another hamstringed project so long as it's not there...
Required fields for Pipeline stages are a pretty big need for reporting on Custom Objects. This would make data cleanliness and adoption for custom objects way easier to manage. Mandatory fields for stages are critical for data cleanliness and adoption!
Some workarounds include:
- Sending an email for each missing field instance - which can be easily ignored by the rep.
- Creating a report/dashboard that shows the missing fields - but we would need to meet and review with the team frequently to get clean data.
I was quite disappointed that this isn't a feature right now as this feels like one of the fundamental requirements. The pipeline stages are not followed properly because there is no obligation to fill in the right properties at the right time.
now we have to work with automated task creation to chase the users for the right info, not ideal.
Adding a +1 for this. Awesome that it is possible to create pipelines for custom objects but a real pain point that it is not possible to get the full functionlality of a trackable pipeline. Need the ability to trigger a 'close reason'.
Without this functionality, custom objects are essentially useless for our company. There's no way I can bank on people filling out fields between stages without them being prompted and forced to.
Darn, will go back to using the ticket pipelines instead.
To bo honest I was a bit in shock when I saw that there is no possibility to add mandatory fields in custom obcjects pipeline. This functionality is a must! Please consider to add this as soon as possible - without this - it is extremly hard to manage some sales suppost processes.
I created a few custom objects (my first time) only to find out this isn't a possibility! 🙈
Had to delete every last custom object and create ticket pipelines instead. Just causing such a mess on our end as I just KNOW this must be something that will eventually get made by HubSpot, in the meantime I will continue to build the tech-debt in HubSpot.
This is crucial to mantain data quality a create more complex worfklows between different objects. No bother having an enterprise account and then not being able to use it properly
Pour ajouter un commentaire ici, vous devez être inscrit. Si vous êtes déjà inscrit, connectez-vous. Dans le cas contraire, inscrivez-vous puis connectez-vous.