Troubleshooting Property Mapping

This article covers the most common problems when setting up Property Mapping in the ClashWise plugin for Navisworks. Property Mapping has its own window (ClashWiseAI ribbon tab → General panel → Property Mapping). For setup steps, see the Configuring Property Mapping article.

"No properties found in the current document. Please ensure you have clash tests with results."

Cause: ClashWise could not find model data to map — usually because there are no clash tests with results in the document.

Solution:

  1. Run your clash tests in Navisworks Clash Detective and make sure they produce actual clash results (not zero clashes).
  2. Save your Navisworks file.
  3. Close and reopen the Property Mapping window.

The model tree is empty

Cause: Same as above — ClashWise lists the source models it finds in your open document, and it needs clash results to work from.

Solution: Confirm your document has appended model files and at least one clash test with results, then reopen the window.

The Property dropdown is disabled

Cause: No category has been selected yet. The Property dropdown only activates after you choose a property category in the first dropdown of that row.

Solution: Select a category first. If the property you need still doesn't appear, try a different category, or type the exact property name directly — both dropdowns are editable.

Preview or Sample Elements shows nothing, or the wrong data

Symptoms: columns stay empty, the Name column shows numbers, the ID column shows text, or the Category column shows file paths.

Solution:

  1. Use Sample Elements for a quick automatic check — it samples elements from the selected source or level and fills the grid. For a manual check, click Preview and then click elements in the Navisworks model view.
  2. A few blank cells are normal — not every element carries every property. A column that is consistently blank or wrong means that field points at the wrong property.
  3. Go back to the affected field, pick a different category/property pair, and sample again. Repeat until each column shows the kind of data you expect.
  4. Click a preview row to select that element in Navisworks — comparing against the native Properties panel is the fastest way to spot which property a value really lives in.
  5. If a value looks like "Int32: 123456", that's just how Navisworks displays the raw property — ClashWise cleans this up automatically when it uses the value.

Note that ClashWise reads properties from whole elements: even if a clash or selection lands on a raw geometry fragment, the values are resolved from the element it belongs to.

A level shows different data than its source

Cause: Levels inherit their source's mapping, but a level exported with a different structure may need its own field settings.

Solution: Select the level in the tree and change just the fields that differ — each change is saved as an override for that level (the level gets a ● marker). Use the reset arrow on an overridden field to inherit the source again, or the Clear button to drop all of the level's overrides.

The Start button in Title Update stays disabled, or "Required Property Mappings Missing" appears

Cause: A Title Update run requires every model in the document to have all six fields mapped.

Solution: The warning takes you to the Property Mapping window at the first unmapped model. Work through every source carrying a warning icon in the tree and complete the missing fields (all six, marked with a red asterisk). The run cannot start until every model is fully mapped.

A "Property Mapping Validation" warning appears during a run

Cause: After you click Start, ClashWise samples your clash data and checks whether the properties needed by your chosen naming standard actually return values. If some are missing, it asks whether you want to continue.

Solution: Choose No to cancel, fix the affected mappings, and run again — this gives the best titles. Choose Yes to continue anyway; clashes will still be processed, but titles may be less detailed where data is missing.

"Apply to Other Models" produced wrong results on some models

Cause: The target models have a different property structure — usually because they come from a different source application or were exported with different settings.

Solution:

  1. Only apply a configuration across models from the same source (Revit to Revit, IFC to IFC).
  2. Select each target model and verify it with Sample Elements.
  3. Manually reconfigure any model where the preview looks wrong.

Also note the dialog's own guard messages: "Current configuration is empty. Please configure properties first." means the source model has nothing to copy yet, and "No models selected." means you clicked Apply without ticking any target models.

When a level is selected, Apply to Other Models... lists the sibling levels of the same source instead, and copies the level's overrides to the ones you tick.

Configuration doesn't persist after reopening

Cause: Mappings are saved automatically to your Windows user profile — if they vanish, something is preventing ClashWise from writing its settings.

Solution:

  1. Check that you have write permissions to your own user profile folder.
  2. Ask your IT department whether settings storage is restricted on your machine.
  3. If the problem persists, contact support at support@clashwise.ai — the Report Bug button on the ribbon's Support panel attaches the plugin logs automatically.

Property names appear in a different language

Cause: The model was authored, or Navisworks is running, under a different language. This is normal and expected.

Solution: Simply select the properties as they appear — ClashWise works with property names in any language. Note that mappings remember the language they were saved under: if you change the Navisworks display language, ClashWise re-detects the properties for that language, so review your mappings after a language change.

A "Select Category Property" dialog appeared

Cause: During some data-extraction flows (for example, creating a clash matrix through the plugin's Wise chat), ClashWise needs you to confirm which property identifies element categories and sources.

Solution: In the dialog (headed Category Property Selection Required), pick the same category and source properties you configured in the Property Mapping window, then click OK. Use Refresh Properties if the lists look incomplete.

Still stuck?

Email support@clashwise.ai, or use Report Bug on the ClashWiseAI ribbon's Support panel — it bundles the plugin logs with your report automatically.

Related topics

Start free trial Download plug-in See pricing