Import Excel Revit 2026

[hayet.sassi2]

I’m using @Dynamo v3.6.0 © 2025 Autodesk, , and I can’t find the Import Excel node. Instead, I tried using Data.OpenXML.ImportExcel , but I don’t understand the error message I’m getting.

Any help would be greatly appreciated thank you!

[jacob.small]

Basically one of the tools used for loading Excel data via open XML isn’t loading for some reason. Usually the root cause is a package conflict.

Can you check your Dynamo log for any issues with conflicts or loading errors?

[RevitRobot]

Try typing Excel instead of Import to find the node you’re looking for.

[_Vijay]

you can try like this.

Data.OpenXMLImportExcel node Error when importing

Got it. Alternatively, you can use Python to import the data [image] import clr import System from System.IO import FileInfo import DSOffice # Take path string from Dynamo input path = IN[0] # Convert to FileInfo object fileInfo = FileInfo(path) # Import Excel data = DSOffice.Data.ImportExcel(fileInfo, "Sheet1", False, True) # Output to Dynamo OUT = data

[jacob.small]

@RevitRobot

Excel instead of Import to find the node

There is a release or two of Dynamo (maybe 3.6?) which removed the deprecated excel nodes from search as part of the end of support process. Only the XML options will surface for many now.

[RevitRobot]

Why is xlsx reading being depracated?

[jacob.small]

Reading an xlsx isn’t being deprecated; that node is. The open XML nodes offer too many advantages.

• No chance for installations or updates to seemingly unrelated Microsoft tools to break your graphs (seriously updating teams shouldn’t break excel, but here we are), requiring admin installation efforts to fix the issue.
• No requirement for office to be installed, thereby allowing use in cloud environments and any system
• No 32/64 bit office version issues
• Launching excel isn’t required (even the headless version), resulting in less clutter on your CPU’s task list (everything runs faster)
• Faster read/write as they don’t have to open excel

This has long been in the works (the original request for feedback on the OpenXML nodes started in July of 2021), and is generally a VERY good thing for the community. A brief timeline:

1. Version 2.12 released the OpenXML methods
2. Version 2.18 fixed a scientific notation issue with the OpenXML methods
3. Version 3.5 marked the Excel interop methods obsolete (hiding them in the library so new uses won’t show up)

Version 4.0 still has the code to use existing Excel interop nodes so opening old graphs with them will work (for now), but you’ll get the warning message below. This means you should spend the next year or so updating old graphs to use the new method whenever you can.