Creating Mandatory Properties in Custom Objects

[HBruce]

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. 

[AOlivabr]

Crucial! +1!

[LudmillaGarcia]

This would be an excellent feature for our customers! I always get tickets about this subject! 😎

[ahashimi]

Recently upgraded to custom objects with the expectation that the custom object pipelines behaved the same way as default object pipelines, disappointed to learn that this isn't the truth. The inability to update stage properties and set them as required is going to cause us issues moving forward, please provide an update on the status of this feature addition, it's a necessity to scale any system using custom objects.

[JByrne2]

This is a must. I have just found out the hard way that this is not possible!! 

[MTarnopolska]

I have found it out in a very hard way.

[REelkmanRooda]

We really need this functionality - currently our data is incomplete and no way to track progress correctly

[Faxon]

Echoing the same concern and supporting to upvote this idea to Dev Team to implement. Custom Objects needs same or more functionaility as Deals. Stage Properties and Workflows is what I need urgently. 

[NDunderdale]

Upvote from here too, massively disappointing that this functionality is not replicated across for CO pipelines. Putting in manual  data governance processes on items such as this is causing a huge headache for us.

[Ezra_Wilson]

This would be a real Quality-of-Life improvement to COs, and we've encountered multiple use cases for multiple Clients where this is vital.

[mandou13]

Definately required !!!! Why is not already available ? That's a MUST

[PJaiswalEE]

This is the most basic requirement of any object. Navigation through stages must need checkpoints. Without it CO feature is of no use

[MaartenDeGroot]

I just saw in my portal that this functionality has been added! 😄

[Rob_Moneyball]

What would be cool is if you could not only show/require properties at certain stages in a pipeline, but also have them be conditional based on other properties. For example, if you require a "Plan" field and a sales rep chooses Plan 1, then it could require the completion of additional properties related to Plan 1. But, if they choose Plan 2, then it could require the completion of a different property (or set of properties). We have tons of automation baked into a deal close -- notifications, tasks, tickets, etc. to the fulfillment teams -- but if a sales rep closes the deal the wrong way, it creates a lot of confusion. Conditional follow-up properties would help us simplify deal closing.