검색은 쿼리가 아닙니다

19개 언어로도 제공

English · Español · 日本語 · Português (Brasil) · Français · Deutsch · Italiano · 简体中文 · Português (Portugal) · 繁體中文 · Bahasa Indonesia · Türkçe · Polski · Tiếng Việt · ไทย · Українська · Español (México) · Français (Canada) · Deutsch (Schweiz)

A fishing net full of silver fish being lifted out of the sea over the side of a small boat, water streaming from it. — AI로 생성한 이미지

Module 5 of 5 in the chapter Query and Retrieval Architecture, chapter 8 of the Data Architect course. Each module stands on its own. ⟲ Previous: How Salesforce Executes a Query · Next: the next chapter, Integration and Data Movement ⟲

이 모듈이 답하는 질문: 언제 쿼리 대신 검색해야 할까요?

쿼리, 인덱스, 선택도, 쿼리 계획, 스키니 테이블에 관한 세 모듈은 모두 한 가지를 전제합니다. 무엇을 찾는지 안다는 것. 오늘의 Redrock 배송. 어제 이후 수정된 케이스. 파트너 참조 번호가 DLV-8472914인 배송. 구조화된 질문들입니다. 하지만 사람들이 늘 구조화된 질문을 하지는 않습니다. 때로는 이렇게 말합니다. “고객이 템피에서 냉장고가 파손됐다고 했던 것 같은데, 찾을 수 있을까요?” 그건 사실 쿼리 문제가 아닙니다. 검색입니다. 그리고 검색은 쿼리가 아닙니다.

쿼리는 구조에서, 검색은 단어에서 시작합니다

SOQL은 우리가 구조를 알 때 환상적입니다. 객체, 필드, 조건. 리테일 파트너가 Redrock이고 예정일이 오늘인 작업 주문. 정보가 어디에 있고, 어떻게 표현되고, 무엇을 검사하는지 알고, 데이터베이스는 이 장에서 설계한 모든 것을 쓸 수 있습니다.

이제 “고장 난 냉장고라는 표현이 들어간 레코드를 찾아 줘.” 어느 객체인가요? 케이스, 작업 주문, 메모? 제목, 설명, 다른 텍스트 필드? 사용자는 모르고, 알 필요도 없어야 합니다. 여기서 Salesforce Object Search Language, SOSL이 등장합니다. “어느 필드로 필터링해야 하지?” 대신 **“이 텍스트를 찾아 줘”**에서 시작합니다. 근본적으로 다른 조회 문제입니다.

개발자들이 검색을 SOQL에 억지로 밀어 넣는 것을 본 적이 있습니다. “사용자가 텍스트를 입력하면 고객을 찾아 줘.” 그러면 쿼리가 자랍니다. Name LIKE … OR Email LIKE … OR Phone LIKE … OR Description LIKE … OR 또 다른 필드, 또 다른 필드. 어느 시점에서 멈추고 물으십시오. 우리는 쿼리하고 있나요, 검색하고 있나요? 요구사항이 여러 필드에 걸친 텍스트 발견이라면 SOSL이 더 깔끔한 도구일 수 있습니다. 그게 SOSL의 용도입니다. SOQL이 가장 많이 쓰는 도구라는 이유로 검색 문제를 쿼리 모양에 억지로 넣지 마십시오.

Remember the hardest case from module 3: contains. Description LIKE '%refrigerator%' has no way into the drawer, so the librarian walks every shelf. Search was built for exactly that question. Salesforce says it directly: “When a given search can use either language, SOSL is generally faster than SOQL if the search expression uses a CONTAINS term,” because “SOSL can tokenize multiple terms within a field (for example, multiple words separated by spaces) and builds a search index off this.” Looking for “John” in “Paul and John Company” is a search question (Using SOQL and SOSL (새 탭에서 열림), Best Practices for Deployments with Large Data Volumes, Winter ‘27). ⟲

클릭하여 확대

“Contains” forced into a query: no way into an index. Slow. ⟲

클릭하여 확대

The same words, asked as a search: straight to the matches. Query knows the structure. Search knows the term. ⟲

How Search Works: Tokens First, Then the Fetch

Back to the library. A database index is the catalog for “books by this author” or “books with this identifier.” Now I want every book containing the phrase “broken refrigerator.” Reading every page of every book for each search would be ridiculous, so search builds its own index over the words. “The Salesforce search architecture is based on its own data store, which is optimized for searching for that text” (Search Architecture (새 탭에서 열림), Winter ‘27): a different engine for a different kind of question. ⟲

How does it fill that store? “When you create a record, the search engine breaks up the searchable content into smaller pieces, called tokens. It stores the tokens in a search index. The search index is much like a book index—each token in the index has a link back to the record it came from” (How Einstein Search Works (새 탭에서 열림), Salesforce Help). When you search, your words are broken into tokens the same way and matched against that index. ⟲

And then comes a step people miss. “Salesforce performs indexed searches by first searching the indexes for appropriate records, then narrowing down the results based on access permissions, search limits, and other filters … The result set is then used to query the records from the database to retrieve the fields that a user sees” (Search Architecture (새 탭에서 열림)). In module 4’s four words: search finds which records in its own index, and then a regular fetch from the database brings back their fields. Two engines, one after the other. ⟲

And it’s not only the search box. Salesforce lists search behind “Advanced and global searches”, “Find boxes and lookup fields”, “Suggested Solutions and Knowledge Base”, “Web-to-Lead and Web-to-Case”, “Duplicate lead processing”, and SOSL from Apex and the API (same source). Like the librarian, search is working in places nobody thinks of as “search.” ⟲

검색은 객체를 넘나들고, 너무 많이 찾을 수 있습니다

SOSL의 강점 하나는 사용자가 어느 객체에 답이 있는지 몰라도 된다는 것입니다. 조정 담당이 “Henderson”을 검색하면, 그것은 계정일 수도, 연락처, 작업 주문, 케이스일 수도 있습니다. 사용자는 그 대상을 찾는 것이지, “먼저 Contact.LastName을 쿼리하고, 그다음 Account.Name, 그다음 작업 주문의 수령인, 그다음 케이스 설명”을 생각하지 않습니다. 검색은 사람들이 실제로 정보를 찾는 방식에 맞습니다.

That creates another problem. Make everything searchable (every object, field, historical record, every bit of text) and then search “Smith,” and the user is overwhelmed. Search didn’t fail; it found too much. That’s search crowding, and at scale it matters as much as speed. ⟲

Search Crowding, Step by Step

Salesforce defines it plainly: “Search crowding–having too many unhelpful search results–can overwhelm you with irrelevant records and slow down search. To avoid search crowding, the search engine limits the number of records it analyzes” (How Search Crowding Affects Search Results (새 탭에서 열림), Salesforce Help). The limit is there to protect search. The cost is that the record you wanted can fall outside it. ⟲

Let’s walk through one search. A Steve Trucking care agent is looking for a case about a damaged refrigerator for a customer named Henderson. She types Henderson into global search. Henderson is also a city, so the word appears on thousands of delivery addresses. Salesforce’s own example uses these numbers, so let’s use them too: ⟲

Every record that matches. The search index finds 3,200 records with the word Henderson: accounts, contacts, cases, and a great many work orders. ⟲
The limit. “Search limits the results to the first 2,000 records found, so 1,200 records aren’t included in your search results” (same source). If her case is among those 1,200, it’s gone before anything else happens. ⟲
Permissions. Only now does search check what she can see. “Search analyzes only 2,000 records, which can include records you don’t have access to. Of the 2,000 analyzed, you don’t have access to 100 of them so you don’t see them in your results. You only see 1,900 records returned” (same source). Those 100 still took up room in the 2,000. Read that again: the cutoff comes before sharing, so records she will never see can take places in the 2,000 and push the record she needs past the line. ⟲
Shared out across objects. When a search names several objects, the 2,000 are shared out. In Salesforce’s words: “If you query one object only, a maximum of 250 records are returned. To return up to 2,000 results, include either the WHERE clause or ORDER BY clause. If you query multiple objects, each object returns up to the minimum number between 2,000/n (where n=number of objects) and 250.” Search ten objects at once and each one gets at most 200. And the results aren’t the same for everyone: “Admins (users with the View All Data permission) see the full set of results returned”, while other users see only what they have access to, and “Results sets and order vary by the user issuing the search and can change throughout the day as records are added or removed from the index” (same source). The order varies too: Salesforce ranks results “based on search term frequency, order, uniqueness, record activity, and access permissions. Search result relevance can vary for each user” (How Einstein Search Works (새 탭에서 열림)). So when someone says “I searched and it wasn’t there,” the first questions are: how many records matched before the limit, and who were you? ⟲
Ranked. What’s left is put in order of relevance, so even when her case survives, it may be far down the list under 1,900 other Hendersons. ⟲

클릭하여 확대

The cutoff comes first, sharing second. Records she can’t see take places in the 2,000, and her case lands in the discarded bucket. ⟲

Now push it to the worst case the mechanics allow. An object holds 100,000 records, and sharing lets this user see 1,000 of them. She’s looking for 10 specific records, and she can see all 10. Her search term matches 3,000 records. The first 2,000 found are all records she can’t see; her 10 are among the 1,000 past the cutoff, in the discarded bucket. Sharing removes all 2,000 that were kept, and she gets no results, for records she knows are there and is allowed to see. ⟲

클릭하여 확대

Visible to her, and still not found: the 2,000 places went to records she can’t see. ⟲

To be fair to Salesforce, this is the edge, not the everyday. The same Help article says: “The search engine’s priority is to return accessible records for users with limited access in an org” (How Search Crowding Affects Search Results (새 탭에서 열림)), and relevance takes access into account. Most of the time that keeps users with narrow access out of this trap. But when someone with limited access swears a record is missing from search and then finds it by opening a list view, this is why, and the fix is the same: a more specific search, fewer objects, fewer records that compete. ⟲

That’s the heart of it. “The search engine looks for matches to the search term across a maximum of 2,000 records”, and only then applies each user’s permissions, so the user sees only what they’re allowed to (SOSL Limits on Search Results (새 탭에서 열림), SOQL and SOSL Reference). So 2,000 irrelevant matches, including records this user can’t even see, can crowd out the one they wanted before sharing ever trims the list. The question isn’t only “how fast is search?” It’s did we design search so the useful answer can surface? ⟲

So when someone says “I searched and it wasn’t there,” the first questions are: how many records matched before the limit, how many objects were searched, and who was searching? ⟲

Mitigating Search Crowding: A Playbook

The fix is always the same idea: fewer, better matches before the limit. Here’s the playbook I’d hand an admin and an architect when someone says “I searched and it wasn’t there.” Work through it in order. ⟲

클릭하여 확대

Rule out freshness, access and searchability first. Then measure. ⟲

Step 1: Rule Out the Other Causes

Not every missing record is crowding. Check the simple causes first: ⟲

Is it too new? Text can take a few minutes to be indexed, and “If a record is created or updated using bulk API, it may take more than 15 minutes for the record to be searchable … wait for a few hours” (How Einstein Search Works (새 탭에서 열림)). A record loaded this morning may not be searchable yet. ⟲
Can this user see it? Open it from a list view or report as that user. If they can’t, it’s access, not search. “Admins can also check profile and permission settings for access to objects” (How Search Crowding Affects Search Results (새 탭에서 열림)). ⟲
Is the object searchable at all? “By default, search is disabled for new custom objects. Admins enable Allow Search when setting up new custom objects” (though “A custom object that’s associated with a custom tab is searchable by default”) (Searchable Fields: Custom Object (새 탭에서 열림)). And remember the 120-day rule: an unsearched custom object can lose searchability. ⟲
Does an exact, unique term find it? Search for something only that record has, like its full name or reference number. If that works and the broad term doesn’t, you’re looking at crowding. ⟲

Step 2: Measure the Crowd

Search the broad term again, then search it in one object at a time. If a search comes back at the limit, 2,000 overall or 250 for a single object without a WHERE or ORDER BY, the results were cut off. Note which object supplies most of the matches. In the Henderson example, it’s the work orders, whose delivery addresses are full of the word. ⟲

Step 3: Cut the Noise at the Source

Data can deserve to exist without deserving to appear in search. These are Setup changes, made in Search Manager (“To use Search Manager: Customize Application AND View Setup”). Do them in this order, from the cheapest to the most structural: ⟲

Turn off objects these users don’t search, by profile. “You can manage searchable objects for each profile in global search.” From Setup, enter Search Manager, select Query Configurations, select the configuration, and “in the Objects List, select an object and turn searchability on or off” (Manage Searchable Objects and Fields (새 탭에서 열림)). If care agents never look for work order line items, their profile shouldn’t search them. ⟲
Take noisy custom fields out of the index. From Setup, enter Search Manager, select Index Management, choose the object, and next to the field choose Remove from search index. “Removed fields don’t appear in search results and aren’t used to match results. You can’t remove standard fields,” and “Your changes can take a few hours” (Manage the Search Index (새 탭에서 열림)). A long description or address field that matches everything is a good candidate. ⟲
For an object nobody should search, disable its search index. That stops “making its data searchable and stop[s] index credit consumption for that object” (Explore the Search Index with Search Manager (새 탭에서 열림)). ⟲
Archive history that no longer needs to be found. Old completed work orders stay in the index and keep competing. Archiving (chapter 7 and module 4’s wrap-up) shrinks the crowd for search and for queries. ⟲
Put identifiers where search looks first. A lookup searches only the record name, and a NAME search group only name fields. If people find a delivery by its partner reference, make sure that value lives in a field search treats as a name or identifier. ⟲

Step 4: Fix the Searches You Build

For every custom search, in Apex, in a component or in an agent’s tool: ⟲

Return only the objects the question needs, each with a WHERE: “For SOSL, selective filters reduce the number of irrelevant results” (SOQL and SOSL (새 탭에서 열림), best practices, Winter ‘27). ⟲
Use a search group: IN NAME FIELDS, EMAIL or PHONE, so an address field full of “Henderson” doesn’t match a name search. ⟲
Prefer specific terms to wildcards, and single-object searches “for greater speed and accuracy” (Searching (새 탭에서 열림), best practices, Winter ‘27). The next section, Asking Search Well, has the details. ⟲

Step 5: Teach the People Searching

Put three habits in the training and the help text: ⟲

A more specific term: “Use a more specific search term, such as Industrial Computing San Francisco” (How Search Crowding Affects Search Results (새 탭에서 열림)). For our agent, Henderson refrigerator, or the customer’s full name. ⟲
One kind of record: “if you’re looking for an account record, search for Industrial Computing in Accounts” (same source). ⟲
The complete name in a lookup: “A lookup search uses only the record name”, so “enter Jupiter Hotels instead of just Hotels” (same source). ⟲

클릭하여 확대

The same search, done well: a specific term in one object, and her case comes through. ⟲

Step 6: Verify as That User

Index changes “can take a few hours”, so check the next day, not the next minute. Repeat the original search as a user with that profile, not as an admin. An admin with View All Data sees results other users don’t, so an admin’s search proves nothing about crowding. ⟲

Step 7: Keep It Healthy

Searchability drifts as an org grows, so make it part of the regular review: ⟲

When a new object or a big text field arrives, decide on purpose whether it’s searchable, and for which profiles. ⟲
Watch the 120-day rule for custom objects people search only rarely. ⟲
Keep sensitive fields out of the index. Search applies field-level security only to “up to 100 searchable custom fields per object” (Explore the Search Index with Search Manager (새 탭에서 열림)), and Salesforce’s advice is direct: “If a field contains sensitive information and you couldn’t apply field-level security to it, remove the field from the index” (Manage the Search Index (새 탭에서 열림)). ⟲

클릭하여 확대

Fewer, better matches before the limit. Three people can make that happen. ⟲

Asking Search Well

You don’t need to write SOSL to be an architect, but you should recognize the levers, because they’re how you keep the right answer from being crowded out: ⟲

Search groups. Search only the kinds of fields that matter: “Search groups include NAME, EMAIL, and PHONE fields. For example, FIND ‘Avery Smith’ IN NAME FIELDS RETURNING Account(Id,Name), Lead(Id,Name)” (same source). ⟲
RETURNING. Name the objects, and the fields to bring back, and add a WHERE or ORDER BY to get past the 250-record default for one object. ⟲
Specific terms. “Keep searches specific and avoid using wildcards, if possible. For example, search with Michael instead of Mi*.” And “Use single-object searches for greater speed and accuracy” (Searching (새 탭에서 열림), best practices, Winter ‘27). ⟲
Wildcards and operators. An asterisk matches “zero or more characters at the middle or end of your search term”, and a question mark exactly one. Quotes keep a phrase in order, and AND, OR and AND NOT combine terms (FIND {SearchQuery} (새 탭에서 열림), SOQL and SOSL Reference). Notice: the middle or the end. Like the index in module 3, search does best when it knows how a word starts. ⟲
Divisions. SOSL can be limited to one division (WITH DivisionFilter), the partitioning tool from module 4. ⟲

And a few limits worth knowing. A transaction in Apex can run “Total number of SOSL queries issued: 20”, and “Total number of records retrieved by a single SOSL query: 2,000” (Execution Governors and Limits (새 탭에서 열림), Apex Developer Guide, Winter ‘27). One quiet trap: “If SearchQuery is longer than 4,000 characters, any logical operators are removed. For example, the AND operator in a statement with a SearchQuery that’s 4,001 characters defaults to the OR operator, which could return more results than expected” (SOQL and SOSL Limits for Search Queries (새 탭에서 열림)). ⟲

Test knowledge. Know SOSL’s limits: at most 2,000 records searched, then permissions applied; 250 for one object unless you add WHERE or ORDER BY; up to 2,000 divided by the number of objects (and no more than 250 each) when you search several; 20 SOSL queries per Apex transaction. Know the levers: search groups (NAME, EMAIL, PHONE), RETURNING, specific terms over wildcards, and wildcards only in the middle or at the end. ⟲

Search Runs as Someone

Search reaches across many objects and returns text, so who it runs as matters. In Apex, that changed recently. “Apex database operations, such as SOSL and SOQL queries, DML statements, and Database methods, now run in user mode by default. In user mode, database operations enforce the sharing rules, field-level security, and object permissions of the current user. In earlier API versions, database operations default to system mode” (Database Operations Run in User Mode by Default (새 탭에서 열림), release notes, API version 67.0 and later). Code can still say which mode it wants: “To indicate an access mode for a SOQL or SOSL query, insert a WITH USER_MODE or WITH SYSTEM_MODE clause” (Set an Access Mode for Database Operations (새 탭에서 열림), Apex Developer Guide). ⟲

And because a search screen takes whatever the user types, it’s a door for injection. Salesforce’s Well-Architected guidance names it: “SOQL or SOSL injections are scoped to a reading that discloses records or fields that the caller shouldn’t be able to reach by widening query conditions”, and asks you to “Validate and sanitize all user input that prevents injection across SOQL, SOSL, and HTML contexts” (Trust (새 탭에서 열림)). ⟲

Search in Other Languages

If your org works in more than one language, search doesn’t behave the same in all of them. “Search is available for Fully Supported Languages. However, not all features, including lemmatization and synonym groups, are available in all languages and for all objects. Only exact matches are returned for searches in End-User Languages” (How Einstein Search Works (새 탭에서 열림)). Lemmatization is what lets a search for “deliveries” find “delivery”; without it, only the exact word matches. And for languages written without spaces, the engine uses “morphological tokenization” to find the words, so a search for Kyoto (京都) doesn’t match Tokyo Prefecture (東京都) (FIND {SearchQuery} (새 탭에서 열림)). For a global care team, test search in each language people actually use. ⟲

발견하려면 검색하고, 운영하려면 쿼리하십시오

양자택일이 아닙니다. 상담원은 “냉장고 파손 Henderson”을 기억합니다. 검색이 케이스나 작업 주문을 찾고, 그 식별자를 얻으면 구조화된 조회가 이어받습니다. 발견하려면 검색하고, 운영하려면 쿼리하십시오.

하지만 양쪽 모두에 함정이 있습니다. 검색이 좋아지면 팀은 구조에 게을러집니다. “그건 모델링할 필요 없어요, 사람들이 검색하면 돼요.” 아닙니다. 정보가 자동화, 통합, 보안, 보고서, 비즈니스 규칙, 매칭, 결정론적 조회를 좌우한다면 구조를 주십시오. 리테일 파트너가 의미 있는 관계라면 모델링하고, 그 이름을 설명란에 묻어 둔 채 검색이 찾아 주기를 바라지 마십시오. 검색은 발견에 훌륭하지만 데이터 모델은 아닙니다. 반대도 마찬가지입니다. 사람들이 정말로 여러 필드와 객체에 걸쳐 텍스트를 발견해야 한다면, 개발팀에게 더 쉽다는 이유로 구조화된 필터의 미로를 지나가게 하지 마십시오.

Salesforce’s own case study shows the pattern for a custom search screen. A customer let users search on any of 20 fields, with wildcards, across several objects, and performance suffered. The fixes: “Use only essential search fields”, “De-normalize the data from the multiple objects into a single custom object”, and “Dynamically determine the use of SOQL or SOSL to perform the search based on both the number of fields searched and the types of values entered. For example, very specific values (i.e., no wild cards) used SOQL to query, which allowed indexes to enhance performance” (Custom Search Functionality (새 탭에서 열림)). Exact values go to the librarian; words go to search. ⟲

검색이 다시 흥미로워졌습니다

오랫동안 저는 Salesforce 프로젝트에서 SOSL이 SOQL만큼 쓰이는 것을 거의 보지 못했습니다. 트랜잭션 개발은 구조화된 레코드와 구조화된 쿼리에서 시작합니다. AI가 검색 아키텍처를 다시 흥미롭게 만들고 있습니다. 에이전트는 늘 WHERE Retail_Partner__c = 'Redrock'에서 시작하지 않습니다. 누군가 “가전 파손에 대해 불만을 제기한 고객은 누구죠?”나 “Henderson 지점의 배송 문제에 관한 게 있나요?”라고 묻습니다. 이제 우리는 정확한 구조화 조회에서 단어로 찾는 쪽으로, 결국에는 의미로 찾는 쪽으로 움직입니다.

And keyword search still isn’t semantic search. SOSL finds words. “Find customers unhappy because deliveries keep arriving late” may match records that say “missed window,” “driver arrived after closing,” “third reschedule” or “came two days later,” none of them using the words in the question. Now we’re asking about meaning, which brings in semantic retrieval, and, combined with structure, hybrid retrieval. The grounding chapter takes that up in Choosing How the Agent Gets the Data (coming soon). ⟲

Agents search too. Salesforce’s hosted MCP server gives AI agents a find tool alongside soqlQuery: it “Executes a text search across multiple Salesforce objects simultaneously … Returns a maximum of 2,000 records total. Use search groups to narrow scope” (SObject All (새 탭에서 열림), Hosted MCP Servers, checked 2026-10-22). The same limits, the same crowding, the same need for specific terms, now asked by a machine that doesn’t get tired of asking. ⟲

Steve Trucking: 어떤 도구일까요?

“오늘의 Redrock 배송을 주세요.” 객체, 파트너, 날짜: 구조화된 질문. SOQL.
“누군가 하역장 파손이라고 언급한 레코드를 찾아 주세요.” 아는 단어, 모르는 필드나 객체: 텍스트 발견. SOSL.
“반복된 지연에 불만인 것 같은 고객을 찾아 주세요.” 비슷한 의미, 다른 단어: 시맨틱 조회.
“이번 주에 활성 배송이 있는 불만 많은 Redrock 고객을 찾아 주세요.” 의미와 구조화된 필터: 하이브리드 조회.

아키텍트가 여기서 결정하는 것

Whether a requirement is structured retrieval, text discovery or something else, instead of defaulting to SOQL; and whether a “contains” belongs in search. ⟲
대용량 잡음이 쓸모 있는 결과를 밀어내지 않도록, 어떤 객체와 콘텐츠가 검색될 가치가 있는지.
Whether search-index freshness is acceptable, including after bulk loads, or the process needs deterministic structured retrieval. ⟲
How the 2,000-record limit, its split across objects, and permissions affect search quality at production volume. ⟲
Who search runs as, in code and for agents, and how user input is protected from injection. ⟲
How search behaves in each language the business uses. ⟲
어디서 검색이 레코드를 발견하고 어디서 구조화된 쿼리가 이어받아야 하는지.

파트너가 Redrock이고 날짜가 오늘인 작업 주문을 묻는다면 구조화된 질문이니 쿼리입니다. 누군가 고장 난 냉장고에 대해 쓴 레코드를 묻는다면 검색하고 있는 것이니 검색입니다. SOQL이 익숙하다고 OR 열 개를 만들지 말고, 어디서나 검색을 켜기 쉽다고 온 우주를 검색하지 마십시오. 검색은 쿼리가 아닙니다. 그러면 다음 질문이 쉬워집니다. 나는 구조를 아는가, 단어를 아는가, 의미를 아는가?

더 알아보기

Salesforce Developers, Best Practices for Deployments with Large Data Volumes (Winter ‘27), checked 2026-11-01: Search Architecture (새 탭에서 열림), Using SOQL and SOSL (새 탭에서 열림), best practices for Searching (새 탭에서 열림) and SOQL and SOSL (새 탭에서 열림), and the Custom Search Functionality (새 탭에서 열림) case study. ⟲
Salesforce Developers, SOQL and SOSL Reference, SOSL Limits on Search Results (새 탭에서 열림) and FIND {SearchQuery} (새 탭에서 열림), checked 2026-11-01. ⟲
Salesforce Help, How Einstein Search Works (새 탭에서 열림), checked 2026-11-01: tokens, indexing time, the 120-day rule, ranking, languages. ⟲
Salesforce Developers, SOQL and SOSL Limits for Search Queries (새 탭에서 열림) (Limits Quick Reference) and Apex Developer Guide, Execution Governors and Limits (새 탭에서 열림) and Set an Access Mode for Database Operations (새 탭에서 열림), Winter ‘27, checked 2026-11-01. ⟲
Salesforce Help, release notes, Database Operations Run in User Mode by Default, Not System Mode (새 탭에서 열림), API version 67.0, checked 2026-11-01. ⟲
Salesforce Architects, Well-Architected, Trust (새 탭에서 열림), checked 2026-11-01: SOQL and SOSL injection. ⟲
Salesforce Developers, Hosted MCP Servers, SObject All (새 탭에서 열림), checked 2026-11-01: the find tool. ⟲
Salesforce Help, How Search Crowding Affects Search Results (새 탭에서 열림), checked 2026-11-01: the definition, the numbers and the suggestions. ⟲
Salesforce Help, Search Manager: Manage Searchable Objects and Fields (새 탭에서 열림), Manage the Search Index (새 탭에서 열림), Explore the Search Index with Search Manager (새 탭에서 열림), and Searchable Fields: Custom Object (새 탭에서 열림), checked 2026-11-01. ⟲

검색은 쿼리가 아닙니다

쿼리는 구조에서, 검색은 단어에서 시작합니다

How Search Works: Tokens First, Then the Fetch

최신성은 설계의 일부입니다

검색은 객체를 넘나들고, 너무 많이 찾을 수 있습니다

Search Crowding, Step by Step

Mitigating Search Crowding: A Playbook

Step 1: Rule Out the Other Causes

Step 2: Measure the Crowd

Step 3: Cut the Noise at the Source

Step 4: Fix the Searches You Build

Step 5: Teach the People Searching

Step 6: Verify as That User

Step 7: Keep It Healthy

Asking Search Well

Search Runs as Someone

Search in Other Languages

발견하려면 검색하고, 운영하려면 쿼리하십시오

검색이 다시 흥미로워졌습니다

Steve Trucking: 어떤 도구일까요?

아키텍트가 여기서 결정하는 것

더 알아보기