Skip to content

Logical and physical items

A Weaver project names logical items such as Lakehouse/Landing, Warehouse/Operations, SemanticModel/Parcel and Report/Parcel. workspace-config.yml binds them to physical items of the same type in the selected workspace.

logical item                 physical Fabric item
Lakehouse/Landing      →     Lakehouse/ParcelLandingDev
Warehouse/Operations   →     Warehouse/ParcelOperationsDev
SemanticModel/Parcel   →     SemanticModel/Parcel_Dev
Report/Parcel          →     Report/Parcel_Report_Dev

Your project owns the logical identity. A Fabric workspace owns the physical item.

Item kinds remain aligned: a logical Lakehouse binds to a physical Lakehouse, and a logical Warehouse binds to a physical Warehouse.

Choose one of three ownership cases

Case Where the data lives Weaver's boundary
Ordinary managed item In the physical target bound to a logical item Build reconciles the selected item to project declarations and may prune undeclared co-located content.
Protected managed object In a managed target, with Prohibit rebuild: true on the Table, Folder, or View Weaver still owns the object; the flag only guards replacement during Build.
External physical source In a physical item that is not a managed target, reached through a physical Shortcut Weaver owns the local Shortcut, not the source item or its contents.

Do not bind or select an external source item as a managed target merely to make it readable. Keep it outside the Build boundary and expose only the required Table, Folder, or schema through a physical Shortcut. See Protecting data for the recoverability decision.

Logical identity stays with the source

A logical item identity combines its kind and name. The kind matters: Lakehouse/Shared and Warehouse/Shared are different logical items.

Every Weaver document belongs to one logical item. That ownership keeps otherwise identical object names distinct across items and gives Build, Load and Test a stable item vocabulary independent of Fabric display names.

Commands select logical items. Build resolves them through the chosen workspace configuration. Catalogue-backed Load and Test use recorded installed bindings. Without a catalogue, model refresh and source/file-mode validation resolve the configured targets; there is no installed binding to consult.

workspace-config.yml supplies an environment

In a workspace configuration you can name:

  • the Fabric workspace;
  • the Warehouse containing the Weaver catalogue;
  • the physical target for each logical item;
  • a Fabric Environment for Python work;
  • a source catalogue to mirror when establishing a development estate.

The catalogue is optional for standalone Power BI operations. When configured, its Warehouse stores Weaver state. It is separate from the physical target of a logical Warehouse unless you deliberately host both in the same Warehouse.

One project can bind to development and production

For example, you can give the same Warehouse project these two configurations:

workspace-config.prod.yml
workspace: Parcel Production
catalogue: Warehouse/ParcelCatalogue

targets:
  Warehouse/Operations: ParcelOperations
workspace-config.dev.yml
workspace: Parcel Development
catalogue: Warehouse/ParcelCatalogueDev

targets:
  Warehouse/Operations: ParcelOperationsDev

You still author Warehouse/Operations in both cases. Selecting the production configuration addresses the production workspace and catalogue and builds into ParcelOperations; selecting the development configuration addresses the development workspace and catalogue and builds into ParcelOperationsDev.

same logical project + production config → production physical estate
same logical project + development config → development physical estate

A configuration's targets mapping tells Build where to install. Catalogue-backed Load and Test read the installed binding, so an edited mapping takes effect there only after Build publishes it. Catalogue-free model refresh and file-mode validation instead use configuration. Power BI environment switching shows target names and linked Report bindings.

A build also refuses to install two logical items into one occupied physical target. The exact configuration keys, discovery order and command-line precedence are in Workspace configuration reference.

Weaver documents specifies what a project places inside each logical item.