@MFrankJohnson @jennysowyrda I’m not sure these solutions are really solving the initial problem. I have the same issue with “required” properties being skipped at deal creation.
In my industry we have a lot of information we like to track: labor hours sold, project cost, proposal number, etc. These propertiess are required as a NEW deal moves through the pipeline stages. NONE of these properties would be known with a “NEW” deal. The deal is “NEW”: I don’t have all the particulars yet, I don’t know exactly what the project will entail, I don’t have a proposal yet, so I can’t have a proposal number…so these properties CANNOT be required when I create a deal…but I can enter the deal into my pipeline in order to track it, remember it, talk about it, manage my sales reps, etc.
Sometimes a deal is NEW and WON on the same day. If upon creating a deal, I set the deal stage to WON, I bypass ALL required fields from ALL the stages except for the create stage.
To be clear…an example
- IF I create a deal and set the deal stage to WON, I am NOT required to enter in how many labor hours were sold or what the proposal number is.
- IF I make the “Labor Hours Sold” and “Proposal Number” properties required when creating a deal, I cannot create the deal as I do not have those pieces of information yet. (and our sales reps will just input nonsense in order to create the deal and our data will be false)
A simple suggestion: Remove “Deal Stage” from the default, required properties list when creating a deal. No choice given upon creating a deal. Have it default to the first stage upon creation. Give users the option of adding it to Create Deal. That way, every deal, when created will start at the beginning of the pipeline. In this way, the required properties for each stage will remain required.
Thanks!