Q: 11
Northern Trail Outfitters uses a custom object Invoice to collect customer payment
information from an external billing system. The Billing System field needs to be filled on every
Invoice record.
How should an administrator ensure this requirement?
Options
Discussion
Why not just use D here if you want to block record creation in UI?
A imo, universal required ensures Billing System is always filled, no matter if it comes from UI, API or import. This matches Salesforce official guide. Anyone see a reason to use Process Builder instead?
C . I remember a similar question and approval processes can enforce required fields during submit/approval. Might not catch everything from API/import but seemed close if the flow uses approvals for each Invoice. Not 100% sure though, could be missing an edge case.
Its A
A here, system required covers UI, API, imports. D only blocks in UI so that's not enough.
Its A, clear requirement and universally required makes sure every Invoice needs that field. Nice straightforward scenario.
Be respectful. No spam.
Question 11 of 30