Every lookup dialog in Business Central has worked the same way for years: click the drop-down arrow, get a full list of records, search or scroll to find the one you want. For a user who works with the same handful of customers, items, or vendors every single day, that full-list-every-time behavior has always meant repeating the same search, over and over, for records the system had no memory of you ever touching before.
Version 29 gives lookups an actual memory, and the way that memory is scoped turns out to be more interesting than the feature description suggests.
What Actually Changed
A new Recent button now appears directly in lookup dialogs, sitting alongside the standard search. Click it, and instead of the full record list, you see the records you’ve personally accessed or worked with recently no searching required for the value you probably want anyway. Clicking Search from that view switches straight back to the standard full-list behavior, so nothing about the existing workflow is removed, only supplemented. If you haven’t touched anything relevant yet, the Recent view is simply empty rather than showing something misleading.
The suggestions are personalized per user and reuse the same server-side intelligence that already powers Autofill Microsoft isn’t building a separate recommendation system from scratch, it’s extending an existing one to a new surface.
The Detail Worth Actually Noticing
Here’s the part that makes this more than a minor UX polish item: the tracking operates at the table level, not the page level. Select an Item while working on a Sales Order, and that same Item shows up under Recent the next time you open an Item lookup anywhere else including on a Purchase Order, a completely different functional area with its own separate workflow.
That’s a meaningful design choice, not an incidental one. Business Central is tracking activity signals per underlying data table, which means recent-record relevance follows the data itself across Sales, Purchasing, and anywhere else that table gets referenced, rather than being siloed to whichever specific page you happened to be using when you touched that record. A user who primarily works in Sales but occasionally creates a Purchase Order for the same items gets a Recent list that already reflects their actual usage pattern, without needing to build up separate history in each functional area first.
Why This Actually Matters for Daily Use
The efficiency gain here isn’t dramatic on any single lookup saving a few clicks and a short search on one dialog is a small thing in isolation. It compounds because lookups are one of the most repeated interactions in Business Central, across every module, every day, for every user. A small reduction in friction applied across an enormous number of repeated actions adds up to something users will actually feel, even if they never consciously notice the individual feature responsible for it.
The cross-functional-area behavior specifically benefits anyone whose role touches more than one process a user who moves between sales and purchasing, or between projects and service, gets recent-record relevance that reflects their actual working pattern rather than resetting every time they switch functional context.
Finally
This is a genuinely small feature, and it won’t anchor anyone’s release-wave keynote. But it’s a good example of a pattern worth watching for across the rest of this release: Microsoft reusing existing platform intelligence in this case, Autofill’s usage-signal collection and extending it to a new surface, rather than building something disconnected from scratch each time.
Small, compounding conveniences like this rarely make anyone’s list of the most important v29 changes. For the person actually using Business Central eight hours a day, they’re often the changes felt the most, precisely because they show up dozens of times daily rather than in one dramatic moment.