Saved views and search across Sales
Save a filtered list you actually reuse, share it with the team, and search across every sales record at once instead of remembering where something lives.
The lists you look at every week deserve names. “Leads from the trade show that nobody has called”, “deals over ten thousand stuck in proposal”, “customers in Texas”. ERPClaw’s built-in Sales lets you save a filter once and replay it by name, and when you cannot remember where a record lives at all, one search sweeps everything.
Say it the way you would out loud:
“Save a view called Hot Leads: status qualified, sorted by newest first. Share it with the team.”
A view is a filter with a name
A saved view belongs to one kind of record, such as leads, deals, customers, or the contacts and companies you maintain, and holds the filter, the sort order, and the grouping you chose. A view built on your pipeline stages is how “deals stuck in proposal” becomes one click. Replaying it gives you today’s records through that same lens:
“Show me the Hot Leads view.”
Views are checked when you save them and again when you run them, against the fields that record actually has, so a view cannot silently reference a field that was never there or return something other than what it claims.
Yours or everyone’s
A view is private to its owner unless shared. Shared views are readable by the whole company, and only the owner can change or delete one. That split matters: the team’s “This Quarter’s Committed” view should not be editable by whoever opened it last.
When you cannot remember where it lives
“Search everything for Acme.”
One search runs across leads, deals, customers, contacts, and companies at once and comes back ranked, exact matches first, then close ones. The result names which kind of record each hit is, so “Acme” the company, “Acme renewal” the deal, and “[email protected]” the contact all land in one list.
Common questions
What is the difference between a saved view and a search? A search is a question you ask once. A view is a question you ask every week, saved with its filters and sorting so you never rebuild it.
Can views filter on my custom fields? Yes. Fields you have added to a record type are usable in views on that type, checked with the same care as built-in fields.
Who sees a shared view? Everyone in the company can use it. Only the owner can edit or delete it.
How current are view results? Live. A view stores the question, not the answers, so replaying it always reflects today’s records.
Is there a way to misuse filters to pull data out? Filter values are handled as data, never as code, and filters are validated against an allowlist of fields and comparisons on both save and run.
How short can a search be? Two characters. Results are ranked and capped, so a broad search stays usable instead of endless.
Reference: the actions behind this page
You never have to type these. They are what ERPClaw runs when you ask, and they are here for anyone calling the API or MCP surface directly, or reading a log.
add-crm-saved-view --name "Hot Leads" --entity-type lead --filter-json '{"field":"status","op":"eq","value":"qualified"}' --is-shared
apply-saved-view --view <id>
list-crm-saved-views --entity-type lead
update-crm-saved-view --id <id> --owner-user-id <owner>
delete-crm-saved-view --id <id> --owner-user-id <owner>
global-crm-search --query "Acme"
list-leads --saved-view-id <id>Filter JSON supports eq, neq, contains, gt, lt, in, and between, validated against each record type’s field allowlist, with values always bound as parameters.