Commands  ›   ›  Import Navisworks Clash Xml

Import Navisworks Clash Xml

writes to model Public API · not yet exposed

Coming soon

Before you run this

Active document should be saved so QA paths resolve beside the RVT.

After it runs

New timestamped results_*.xml may be written, or JSON feedback is returned via CommandExecutor.SetResultObject.

When to use this

Don't use this when

Silent headless import without user file selection in interactive Revit sessions.

What you'll see in the chat

on start
Opening file picker for Navisworks clash XML…
Merging Navisworks clash report into QA results…
thinking
Validating active document and import path…
Calling ReadWriteClashResultsToXml.MergeImportedXml…
Reading merged clash count from latest results…
on success
Import complete — merged {count} clash rows into {outputPath}.
on failure
Navisworks XML import 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/import_navisworks_clash_xml
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

import navisworks · import clash xml · navisworks clash report

Pillar