CRM & sales ops21 categories
Write a Salesforce validation rule
Stopping bad data at entry without blocking every legitimate edge case.
Write a Salesforce validation rule for the requirement below. Return: the formula, the error message as the user will read it, where the error should appear, and the exact conditions under which it fires. Then list what it would wrongly block — bulk loads, integration users, historical records being edited for another reason, record types it should not apply to — and how to exempt them. If a validation rule is the wrong tool and this should be a required field, a flow, or a report, say so. Requirement:
Making it yours
- Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
- Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
- If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.
Automation and admin. Workflows, validation, field design and the documentation nobody wrote at the time.
Related prompts
Design this HubSpot workflowAutomating something in HubSpot without discovering the edge cases in production.Design the field before anyone creates itA request for a new CRM field, which is easy to add and very hard to remove.Write the lead routing rulesDeciding who gets which lead, including the cases nobody thought about.Define lifecycle stages that mean somethingWhen MQL and SQL are used differently by marketing and sales, and handovers keep failing.Audit these automations for conflictsA CRM where several workflows have accumulated and something keeps overwriting a field.Document how this CRM is actually set upAn inherited CRM whose logic lives only in the head of someone who left.
Keep this one
Phrasery saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.
Add to your browser — free