@JohnB691

Here’s the thing: the OOTB search won’t match across two separate columns, so give it a single searchable field. Create a Text property like .FullName and populate it with FirstName + " " + LastName via a declare expression or on-save data transform (also handle middle names and extra spaces). Add .FullName to the class’s search index fields in Dev Studio (Search settings → choose your class → include property), then trigger a full reindex of that class. After reindexing, users can type “john smith” and hit the .FullName tokens instead of needing two filters. If you need partials like “jo smi,” enable the standard analyzer (works fine) or add an n-gram/custom analyzer if your version supports it. For lists where you can’t change the index, add a Report Definition with a calculated column that concatenates names and filter with “contains.” Finally, surface that RD behind a “People search” view or action so users have one simple box that just works.