Import Table by Key
Overview
Import Table by Key imports a plain spreadsheet that has no Element Id column — a schedule export, a consultant's list, a vendor sheet — by matching each row to elements through a key value instead of an Element Id. You choose the target category, the spreadsheet column that identifies the element, and the Revit parameter that holds that same value; because the match is by value, one row can update many elements at once (one lot code updating all of its rooms). It then reuses the same preview-and-apply flow as Import Parameters from Excel.
How matching works
- The Key Column holds the value in the spreadsheet; the Match Parameter is where that same value lives on the elements.
- Every element whose Match Parameter equals a row's key receives that row's mapped values — this is why one row can update many elements.
- Key schedules are a special case: the match is on Key Name, so no match parameter is required.
How to use
- In the B45 Labs | Coordination tab, open the External Tools panel and click Import Table by Key.
- Pick the .xlsx file to import.
- In the setup window, choose the target category — model and annotation categories are offered, with the model's key schedules listed first.
- Confirm the header row (auto-detected), then pick the Key Column (the spreadsheet column that identifies elements) and the Match Parameter (the Revit parameter that holds the same value).
- Review the column-to-parameter mapping — columns are auto-matched to same-named parameters, and you can override any target or set it to (skip).
- Continue to the preview, opt rows in or out, then Apply to write the values in a single undo step.
- Read the final report — matched elements, unmatched keys, and any warnings.
Tips & Notes
- Use it for sheets that key on Mark, Type Mark, a room number, or a custom code instead of Element Id — anything the elements already carry in a parameter.
- Because a single key can match many elements, one row fans out to all of them; make sure the key is unique enough for what you intend to change.
- Choosing a key schedule as the target matches on Key Name automatically — the match-parameter step is skipped and the key column defaults to "Key Name".
Limitations
- Active document only; read-only models are rejected before the setup window opens.
- Keys that match no element are reported as unmatched rather than written.