Add guardrail when setting a tech as the Sold By of an estimate: Tech must have non-0 split on the job

Issue

Techs are allowed to be set as the Sold By on an estimate even if they are not assigned to the job/ or have a 0% split. This causes reporting issues in the Tech Performance dataset (some Sales KPIs show the estimate, whereas others do not. This causes reporting to look incorrect, however it's just reacting to "bad data" in).

The issue is a workflow issue-- techs that were not assigned to the job could not have sold an estimate on that job.  Additionally, techs with 0% splits will not show in certain sales metrics.

Possible Solution

If a user attempts to set the Sold By of an estimate as a technician, and the technician being set does not have a non-0 split on the job on which the estimate was sold, they should be warned in some way:

• User should not be able to assign the tech as the Sold By until the tech is assigned to the job AND GIVEN A SPLIT, or
• User should get a warning message that the tech is not assigned to the job OR that tech must have a non-0 split. To maintain accurate reporting, please give the tech a non-zero split on the job.

This should only happen if the user being set as the Sold By is a technician. If it is an employee, then the user should not experience any guardrails.

Wins

Accurate reporting, increases trust in reporting

Fewer Support cases

Dispatch/CRM:

Ideally this would function with Dispatch/ CRM as well. If a tech is unassigned from a job on which they sold an estimate OR if split is set to 0%, they should experience the same guardrails.