Skip to content

docs(data-modeling,skills): re-quote the corrected searchable-fields hint, drop the moot caveat #6980

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
os-project-manager merged 1 commit into from
Aug 9, 2026
+2 −7
Merged

docs(data-modeling,skills): re-quote the corrected searchable-fields hint, drop the moot caveat #6980

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 1 addition & 4 deletions content/docs/data-modeling/schema-design.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -169,14 +169,11 @@ every entry is dropped.

hint: 'search' scans this object's own columns, so a related record's column
cannot be a search target — expand the relation and search the related object,
or copy the value onto a formula field here. Clients echo this declaration
or copy the value onto a stored text field here. Clients echo this declaration
verbatim as the '$searchFields' override, so a stale entry becomes a 400
INVALID_FIELD on list search (#4254), not just a quietly narrowed one.
```

(That hint's "text/formula" family of wording is loose — only the **stored**
half works; see the callout above.)

A request that sends the dotted path is `400 INVALID_FIELD`:

```text
Expand Down
4 changes: 1 addition & 3 deletions skills/objectstack-data/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -168,13 +168,11 @@ every entry is dropped.

hint: 'search' scans this object's own columns, so a related record's column
cannot be a search target — expand the relation and search the related object,
or copy the value onto a formula field here. Clients echo this declaration
or copy the value onto a stored text field here. Clients echo this declaration
verbatim as the '$searchFields' override, so a stale entry becomes a 400
INVALID_FIELD on list search (#4254), not just a quietly narrowed one.
```

(The hint's "formula field" wording is loose — only a **stored** mirror works.)

A request carrying the dotted path is `400 INVALID_FIELD`:

```text
Expand Down
Loading