搜尋不是查詢

🌐 另有 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)

圖片由 AI 生成

由 AI 翻譯，尚未經過社群審閱。 閱讀英文版 本節的英文原文已有變更，尚未重新翻譯。 (102)

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 的配送。這些都是結構化的問題。但人們並不總是問結構化的問題。有時他們會說：「我記得客戶提到過坦佩（Tempe）有一臺損壞的冰箱。你能找到嗎？」這其實不是一個查詢問題。這是搜尋。而搜尋不是查詢。

查詢從結構開始；搜尋從詞語開始

當我們知道結構時，SOQL 非常出色：物件、欄位、條件。零售合作夥伴是 Redrock、計劃日期是今天的工作訂單。我們知道資訊存放在哪裡、如何表示、我們在檢驗什麼，資料庫也能用上這一章裡我們設計的一切。

現在換一個：「找出包含 broken refrigerator（損壞的冰箱）這個短語的記錄。」哪個物件？案例、工作訂單，還是備註？主題、描述，還是另一個文字欄位？使用者不知道，也不應該需要知道。這就是 SOSL（Salesforce 物件搜尋語言）登場的地方。它不是從「我該篩選哪個欄位？」開始，而是從**「找到這段文字」**開始。這是一個本質上不同的檢索問題。

我見過開發人員硬把搜尋塞進 SOQL。「讓使用者輸入一些文字，然後找到客戶」，於是查詢越寫越長：Name LIKE … OR Email LIKE … OR Phone LIKE … OR Description LIKE … OR 又一個欄位，再一個。到了某個點，停下來問一問：**我們是在查詢，還是在搜尋？**如果需求是跨欄位的文字發現，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.” ⟲

新鮮度是設計的一部分

That index is asynchronous. New and changed records are queued and indexed by separate servers, and “it could take about 15 minutes or more for the updated text to become searchable” (Search Architecture （在新標籤頁中開啟）). Big loads take longer: “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 for it to be indexed” (How Einstein Search Works （在新標籤頁中開啟）). So after a migration, the search index is behind for a while, just as module 4’s notebook of statistics is behind until the nightly run. ⟲

So search and query have different freshness. Steve Trucking creates a case at 10:00; at 10:01 a SOQL query returns it, while a text search for words in its description depends on whether the search index has caught up. That isn’t a defect. It’s a property of the mechanism. “The moment a delivery exception is created, our automation must find it.” Would I build that on text search? No. The process knows the work order, the exception type, the date and the status, so a structured query is the deterministic choice. “A care agent wants old cases where customers mentioned damaged refrigerators”? Search makes far more sense. Different requirement, different engine, different freshness. Choose the retrieval mechanism from the question, not from habit. ⟲

搜尋跨越物件，也可能找到太多

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: ⟲

1. Every record that matches. The search index finds 3,200 records with the word Henderson: accounts, contacts, cases, and a great many work orders. ⟲
2. 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. ⟲
3. 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. ⟲
4. 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? ⟲
5. 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: ⟲

1. 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. ⟲
2. 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. ⟲
3. 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 （在新標籤頁中開啟）). ⟲
4. 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. ⟲
5. 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. ⟲

用搜索來發現，用查詢來運營

這不是二選一。客服記得「damaged refrigerator 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。
• 「找出有人提到 loading dock damaged（裝卸平台損壞）的記錄。」詞語已知，欄位或物件未知：文字發現。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. ⟲