Commands  ›  Clash Manager / Finder  ›  Clash Finder Import Results From Navisworks Xml

Clash Finder Import Results From Navisworks Xml

Clash Manager / Finder writes to model Public API · not yet exposed

Coming soon

Before you run this

file path points to a valid NW exchange XML.

After it runs

Zero or more ClashRecord upserts.

When to use this

Don't use this when

Re-running detection — this is purely ingestion.

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "clash_tolerances" Deterministic config preset

Decision flow

1) file path required; file must exist.
2) Read text + delegate parsing to ImportClashesFromNavisworksFile.Read.
3) For each row, build ClashRecord with id = row.Id (or SHA-256 over rule + sorted guids if blank); state already normalised by the reader.
4) ClashesRepository.Upsert; count inserts vs updates.
5) Emit imported + upserted + skipped.

What you'll see in the chat

on start
Importing NW XML into staging DB…
thinking
Reading file and parsing…
Upserting each clashresult…
on success
Imported {imported}; upserted {upserted}.
on failure
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/clash_finder_import_results_from_navisworks_xml
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

clashfinderimportresultsfromnavisworksxml · import nw clash xml · nw bridge import

PillarClash Manager / Finder