Commands  ›   ›  Layout Apply Pending Placements To Revit

Layout Apply Pending Placements To Revit

writes to model Public API · not yet exposed

Coming soon

Before you run this

change id resolvable in staging DB.

After it runs

FamilyInstances created inside one Transaction; change transitioned to 'applied'.

When to use this

Don't use this when

Dry-run / preview — use LayoutPreviewPlantroomSolveWithPreset.

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "plantroom_layout" Deterministic config preset

Decision flow

1) change id required.
2) Load pending_placements for the change.
3) For each placement: resolve FamilySymbol (unique id first, then name fallback).
4) Open Transaction. Activate symbol if not active. Call NewFamilyInstance. Record per-placement outcome.
5) Commit; transition change to 'applied'. On no successes, roll back + mark 'rejected'.

What you'll see in the chat

on start
Applying staged plantroom placements…
thinking
Loading pending_placements…
Creating FamilyInstances inside one Transaction…
on success
Created {instances_created} instances.
on failure
Apply failed: {error}

REST API

Not yet exposed

This command does not carry a [RestApi] attribute today. Once tagged, this section will auto-populate with:

  • POST /api/v1/commands/layout_apply_pending_placements_to_revit
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

layoutapplypendingplacementstorevit · apply plantroom placements · commit staged layout

Pillar