Skip to content
Core Studio

Indexing and Search

A workspace-wide map of F&O code and metadata.

Core indexes the application catalog in tiers, makes early results visibly partial, and updates affected records as workspace files change.

The Studio's search view listing code-level source matches with method paths and snippet lines for a query over the ERP metadata
  1. Query by name, type, model, property, or code — scoped filters
  2. Quick Open searches elements and source files
  3. The index reports its own state in the status bar

Core Studio 2.0.0 (signed) · estate rig · captured 2026-09-04

Tiered startup

The index builds in tiers; the tree becomes browsable early and results are flagged partial until the deep tiers complete.

Documentation →

Incremental updates

File watchers reindex the records affected by a save; the rest of the index stands.

Documentation →

Query types and ranking

Name, type, model, property, and full-text queries with snippets and model-scoped filters, ranked against the metadata.

Documentation →

State behavior, visible.

The index reports its own state — partial, converging, stale, or error — in the status bar and in results.

Index states as surfaced in the shipped 3.0 build.
Capability Evidence Scope
Partial results while tiers run Indexing guide Startup and root change
Converging after a save Index lifecycle Incremental reindex of affected records
Stale / error reporting Troubleshooting Status bar and result flags

Benchmark summary.

Internal certification measurements on a D365 development VM against the product's own prior baseline — engineering-progress numbers, not independent benchmarks.

Jump to definition, anywhere in the ERP

16.7 s → 62–117 ms

Internal certification measurements on a D365 development VM against the product's own prior baseline — engineering-progress numbers, not independent benchmarks.

Quick-open file search (Ctrl+P)

281–530 ms → 3–16 ms

Internal certification measurements on a D365 development VM against the product's own prior baseline — engineering-progress numbers, not independent benchmarks.

Save a file

16.4 s → 13 ms

Internal certification measurements on a D365 development VM against the product's own prior baseline — engineering-progress numbers, not independent benchmarks.

Recovery: a stale or corrupt index is rebuilt from the workspace on demand — see Indexing and Troubleshooting.