Ability to Control Which Fields are Required on an Opportunity

I agree with this - though there is a way to accomplish this with some custom development. A couple years ago we actually created and self-host a pretty basic Opportunity Intake Form that does this for us internally.

It leverages the D-Tools Cloud API and effectively replicates the New Opportunity 'Wizard' from the D-Tools Cloud web interface but gives us granular control over the required fields

• It searches/allows you to select your existing D-Tools Cloud Clients, or create a new Client if needed

• Any field from the D-Tools Cloud new Opportunity wizard are replicated here with one exception - Referred By isn't part of the API specification so that can't be used

• You actually can add a few more Opportunity fields than the wizard exposes, such as Estimated Start Date and Estimated End Date

Beyond the absent Referred By section the only caveat is Opportunities created through the API do no auto-create a Quote upon initialization - the Quotes table/section is empty and the first Quote just needs to be added the same way you would add any additional Quotes to an Opportunity

You can see in the attached image we've got Template, Square Feet, Lead Source, Estimated Close Date, Estimated Start Date, and Estimated End Date all as required fields that the form will not proceed without.

Of course it can be entirely bypassed just by using d-tools.cloud to create your Opportunity instead of the custom intake form but that's more of an employee management issue more than a technical one if that happens.