Reference¶
Use Reference to look up current public interfaces, exact representations and operation behaviour. For a worked task, start with Lakehouse, Warehouse, Semantic models, Reports or Coordinate your estate.
Find the definition for your item¶
| Item | Authored definitions and relevant interfaces |
|---|---|
| Lakehouse | Python and Spark SQL Tables, Folders, Shortcuts, Python authoring and runtime requirements. |
| Warehouse | T-SQL Tables, Views, schema metadata and programmables. |
| Semantic models | Native layout, TMDL merging, annotations, extension API and DAX validations. |
| Reports | Discovery and local model association, deployment binding and target mappings. |
For Lakehouse and Warehouse validation declarations, use Test, Assumption and Python validation objects. Test behaviour distinguishes installed definitions and recorded results from source/file execution. Reports have no Load or Test; refresh and validate their semantic model.
Look up a shared operation¶
Selection and identity defines item and document names. Load selection defines whole-name regular expressions and ancestor/descendant expansion; reload defines the destructive scope. Workspace execution settings defines resource ceilings alongside the invocation caps in Build, Load and Test.
Model source mappings and connections are distinct from destination names and credentials. Build behaviour defines the separate source-item and model/Report Build calls. For recorded estate evidence, use Health behaviour and the catalogue schema.
Complete reference areas¶
| Area | Use it to look up |
|---|---|
| Weaver documents | Authored locations, forms and metadata. |
| Semantic models and Reports | Native project layout, TMDL policy/composition, annotations, DAX validations and compatibility modes. |
| Python API | Public exports, call shapes and result types. |
| CLI | Commands, options and shared CLI behaviour. |
| Configuration files | Workspace, workflow and Fabric Environment definitions. |
| Operation behaviour | Selection, state changes, outcomes and failure boundaries. |
| Catalogue schema | Public _ tables, columns, types and keys. |
| Build bundle format | Manifest, payload and destination-bound installation handoff. |
| Machine-readable output | Command-specific CLI JSON documents and exit outcomes. |
For options in an installed CLI version, run:
These pages record current formats where no separate compatibility policy exists. They do not make every machine shape or stored column a stable cross-version contract.