This article covers the most common problems when setting up Property Mapping in the ClashWise plugin for Navisworks. Property Mapping lives on the Property Mapping Configuration tab of the Enhance window (ClashWiseAI ribbon tab → Clashes panel → Enhance). 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:
- Run your clash tests in Navisworks Clash Detective and make sure they produce actual clash results (not zero clashes).
- Save your Navisworks file.
- Close and reopen the Enhance window.
The Model File dropdown 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 shows nothing, or the wrong data
Symptoms: columns stay empty when you click elements, the Name column shows numbers, the ID column shows text, or the Category column shows file paths.
Solution:
- Make sure Preview is running: click Preview, then click elements in the Navisworks model view — the grid fills from the objects you select. (If you see "Please select a model file first." or "Please configure at least one property mapping first.", do that first.)
- 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.
- Go back to the affected field, pick a different category/property pair, and preview again. Repeat until each column shows the kind of data you expect.
- 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.
The Start button stays disabled
Cause: The Start button on the Clash Tests tab only enables once at least one clash test is selected and every model file listed in the Model File dropdown has all six fields mapped.
Solution: Step through each model in the Model File dropdown and complete any fields that are blank. All six fields (marked with a red asterisk) are required for every model.
"Required Property Mappings Missing" when starting an Enhance run
Cause: One or more models in your document still have incomplete mappings.
Solution: The warning lists the required fields, and clicking OK takes you to the Property Mapping Configuration tab. Check each model file in the dropdown and complete the missing fields. 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:
- Only apply a configuration across models from the same source (Revit to Revit, IFC to IFC).
- Select each target model and verify it with Preview.
- 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.
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:
- Check that you have write permissions to your own user profile folder.
- Ask your IT department whether settings storage is restricted on your machine.
- 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 disciplines.
Solution: In the dialog (headed Category Property Selection Required), pick the same category and discipline properties you configured on the Property Mapping Configuration tab, 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
- Introduction to Property Mapping
- Configuring Property Mapping
- Property Mapping FAQ