Data sourced from Dakota Marketplace for Salesforce, the global LP and GP intelligence platform trusted by investment professionals. Learn More | Book a Demo
Version 4.0 of Dakota Marketplace for Salesforce shipped 133 features and enhancements. The one your team will notice first is also the smallest: you can now save a search.
That sounds minor until you count how often the same search gets rebuilt. A fundraiser covering the Northeast opens Salesforce, sets metro area, sets channel type, sets an AUM band, then scrolls to find who moved since last week. It takes ninety seconds and produces an identical list every time. Multiply that by a distribution team and a calendar year, and the cost stops being trivial.
Custom list views close that gap. They sit on the Marketplace Accounts and Marketplace Contacts tabs, they hold whatever filter combination you built, and they are there when you come back.
In this article, we’ll cover ten specific ways saved list views change how a distribution team works inside Salesforce, from territory planning to bulk linking to what your team stops arguing about.
10 List Views For Making Salesforce Faster and Easier
1. Your territory stops being a search you re-run
Set metro area and channel type once, name the view, and it persists. “Boston RIAs” or “Midwest Corporate Pensions” becomes a thing you open rather than a thing you rebuild.
The filters available are the ones a fundraiser actually segments by: metro area, country, channel type, CRD, parent account, and investment preferences. A view can combine them.
2. Accounts and contacts live on separate tabs
Marketplace Search used to be one tab. In 4.0 it’s two, Marketplace Accounts and Marketplace Contacts, and each loads its data automatically when you open it.
That matters more than it sounds. Firm-level work and person-level work are different jobs, and running both through one filter set meant re-filtering every time you switched between them.
3. Record counts sit in the header
Each tab shows the total record count and the selected count. You see the size of the job before you commit to it, and you see what you’ve selected as you work through it.
A view returning 1,200 accounts is a different week’s work than one returning 40. Knowing which before you start is the difference between planning and discovering.
4. Select All works across paginated results
This was a real bug and it’s fixed. Previously “Select All” stopped at the page boundary, so working through a long result set meant selecting, acting, loading more, and selecting again.
Now it spans the full set behind Load More. A 500-record action is one action.
5. The view becomes the work queue, not the lookup
From a saved view you can link or create up to 500 records at once. Dakota fuzzy-matches against your existing Salesforce accounts by name, phone, website, or CRD, so you’re reviewing matches rather than hunting for them.
That inverts the usual order. Instead of finding a record and then deciding what to do with it, you define the set and act on the set.
Want to see saved views running against your own Salesforce instance? Book a demo of the Marketplace for Salesforce App.
6. Export to Excel without leaving the tab
Board packs, call sheets, and territory reviews all tend to end up in a spreadsheet. Records export directly from the tab, so the trip out of Salesforce and back is one click instead of a copy-paste job.
7. Pin the views your week actually runs on
Views can be saved, renamed, updated, pinned, unpinned, and deleted. Pinning is the one that keeps the tab usable.
Most fundraisers have two or three views they live in and a long tail they built once. Pin the former, unpin the rest, and the list stays short enough to scan.
8. Roll up an aggregator into one view
Filtering by parent account or CRD pulls an aggregator’s offices together rather than leaving you to chase them one at a time.
For anyone covering RIA aggregators or multi-office broker-dealers, this is the difference between one view and fifteen searches.
9. Build views on what allocators buy, not just where they sit
Geography is the obvious filter and the least differentiating one. Investment preferences let you build a view around the allocators whose stated interests match what you’re raising.
A view of family offices in the Southeast is useful. A view of family offices in the Southeast with a stated private credit preference is a call list.
10. The views are yours
Saved views belong to the user who built them. Your team isn’t working from one shared filter set, and nobody overwrites the view you spent twenty minutes getting right.
What This Adds Up To
None of these is dramatic on its own. Saved filters, working pagination, a count in the header, an export button. Together they remove the part of CRM work that nobody was hired to do.
That’s the test worth applying to any CRM feature: does it give time back to the people whose job is talking to allocators? A saved view that opens to the right 200 accounts on a Monday morning does. A search rebuilt from scratch does not.
Dakota Marketplace for Salesforce puts verified allocator accounts and contacts into the CRM your team already runs on, filterable by metro area, channel type, CRD, parent account, and investment preferences, and saveable as the views your team opens every morning. No custom development required.
Book a demo of the Marketplace for Salesforce App.
