Importing External Excel Lists via Tables into Revit

Planworks Support
  • Updated
Follow
FAQ – Importing External Excel Lists via Tables into Revit

FAQ – Importing External Excel Lists via Tables into Revit

Category: Tables  ·  Topic: Data Exchange / IFC / Excel Import

This FAQ answers common questions about exchanging fire protection parameters between a fire protection engineer and an architecture firm using Tables and Excel — particularly when working with IFC imports.

QWhy does the Excel import fail in the architect's Revit model?▼

Tables uses Revit Element UniqueIDs (UIDs) as unique identifiers to match parameters between Excel and Revit. These UIDs are model-specific — they only apply to the Revit model in which the elements were originally created.

When an IFC file is imported into Revit, all elements receive new UIDs. The UIDs in the fire protection engineer's Revit model therefore do not match those in the architect's Revit model — Tables cannot map the rows in the Excel file to any element in the target model.

Root Cause From Tables' perspective, these are two entirely different Revit models with different UIDs for the "same" elements. A direct match is not possible with the current approach.
QHow can we still exchange fire protection parameters across model boundaries?▼

The recommended solution uses the IFC GUID as a shared identifier between models. Follow these steps:

1
IFC export with GUID embedding: When exporting the IFC file (from the architecture model or your model), make sure that the IFC GUIDs are written into the corresponding elements. This option is available in the Revit IFC export settings.
2
Import IFC into Revit: Import the IFC model into Revit. The elements will receive the parameter IFC GUID, which creates a direct link to the architect's original model.
3
Tables export with IFC GUID: In your Revit model, use Tables to create an Excel list containing the fire protection parameters and the IFC GUID parameter.
4
Import at the architect's end using VLOOKUP: The architect can use Tables together with Excel lookup functions (e.g. VLOOKUP) to match the fire protection parameter values to the correct elements in the ARC Revit model using the IFC GUID.

Workflow overview:

ARC Revit Model
→
IFC Export (with GUID)
→
Import into FPE Revit
→
Tables Export (GUID + FP params)
→
Excel at ARC (VLOOKUP)
→
Tables Import into ARC Model
Tip Sounds complicated — but it really isn't! The key step is using the IFC GUID as a shared "key" in both models.
QWhere do I enable IFC GUID embedding during export?▼

In Revit, go to the IFC export dialog under Export Settings → General and enable the option "Write IFC GUIDs to element properties" (exact wording may vary depending on your Revit version and IFC exporter). After importing the IFC into Revit, the IFC GUID parameter will be visible on each element and can be used in Tables lists.

Note Both the fire protection engineer and the architect must ensure that GUID embedding is active during their respective IFC exports — only then will the values match across both models.
QWhy does Tables use Revit UniqueIDs (UIDs) instead of IFC GUIDs by default?▼

Tables is primarily designed for data exchange within the same Revit model or between models sharing the same origin elements. In these cases, Revit UIDs are the most reliable and fastest identifier available.

Exchanging data across IFC boundaries — as in the scenario described here — is a specialised use case that requires the IFC GUID workaround described above.

QWill this workflow be simplified in a future version of Tables? Roadmap▼

Yes. A future version of Tables is planned to include a general data link that will allow different data sources to be connected in a unified way — without the need for Excel formulas like VLOOKUP. This will significantly simplify cross-model parameter transfers.

Coming Soon With the planned data link, manual Excel lookups will no longer be necessary. Exchanging data between different Revit models — including via IFC — will be possible directly within Tables.
QIs there a guide or video for this workflow?▼

At this time, there is no dedicated guide or video specifically for this IFC GUID workflow. However, our support team is happy to assist you directly.

Contact Support Feel free to reach out to us — we offer direct consultation and can walk through the workflow with you. Write to us at: support_fra@kopnyc.com

Summary: IFC GUID Workaround

Since Tables uses Revit UniqueIDs (UIDs) internally for element matching, the following workaround is required when exchanging data across IFC boundaries:

  1. IFC export with GUID embedding enabled (architect → fire protection engineer)
  2. Import IFC into Revit → elements receive the IFC GUID parameter
  3. Tables export: fire protection parameters + IFC GUID exported to Excel
  4. Architect maps values using VLOOKUP based on the IFC GUID
  5. Tables import into the ARC Revit model

Questions or issues? Contact us: support@planworks.de

Related articles

Comments

0 comments

Please sign in to leave a comment.