Hey Civil 3D users,
Civil 3D 2026.1 was just released! 
You now have access to Dynamo Core 3.5, as well as a ton of improved documentation for all the nodes in the Civil 3D section of the library. Here’s a blog post that summarizes everything for you 
I felt excited for the label bugs are fixed and a little bit disappointed the latest 2026.1 Update didn’t include the Dynamo Core 3.6 just released few days ago. I really want to see how much faster and performance improvements in the 3.6 version 
It will come! If you look back at prior releases, you’ll notice that there is typically a few months between a new version of Dynamo Core and when that version becomes available in an update to a host application like Civil 3D or Revit. This is because we need time to integrate the new version, do all the testing, etc. It takes more than a few days 
In the meantime though, you could always download Dynamo Sandbox and try it out. The performance improvements were focused on things like file open/close, graph navigation, custom package loading, etc., which don’t require Civil 3D.
Hi @zachri.jensen,
Cool stuff, and thanks for fixing the reported issues!
One thing I’d like to mention — which I also brought up during the Autodesk Research interview — is that I would really appreciate it if, at least in the case of incremental updates, settings, packages, and file history could somehow be transferred to the new Dynamo version.
While I understand that packages might introduce some issues, I don’t see a reason why settings and file history couldn’t be preserved across versions.
Hi @zachri.jensen ,
In this release the ImportExcel and ExportToExcel nodes seem to be removed.
I think this should be noted in the release notes on the C3D page. This is not mentioned in the Blog post either, only in the Github release notes.
On Github it is stated that Excel Interop Nodes have been obsoleted. I don’t know why these changes have been made and what does it actually mean, but using only the OpenXML nodes is really inconvenient especially for testing as it requires the excel file to be closed while running the script.
I know this is on Core level, but still I had to mention.
Also, Node Autocomplete seems to crash Dynamo for me.
Thanks @kovacsv. We’ll take a look at the autocomplete issue.
I’ll let @solamour and @achintya_bhat comment on the Excel nodes.
@kovacsv Firstly, we apologize for the oversight in not including the information about the removal of the ImportExcel and ExportToExcel nodes in the Dynamo blog post.
This was a miss from our end and a fair callout from your end! We’ll make sure to update the blog post and also work on improving early communication in the future.
The decision to deprecate the ImportExcel and ExportToExcel nodes was made to streamline our approach and make Dynamo more reliable and stable. The new OpenXML nodes were introduced in Dynamo 2.0 as part of this strategy to ensure better interaction with Excel using the OpenXML standard. The legacy nodes relied on the local installation of MS Office, and when not compatible, it led to issues in some cases and wasn’t very stable. You can refer to this forum post for more details here. But this move came with some trade-offs like needing to close the Excel file while running the script.
If you have graphs that are currently using these nodes, and you would like to continue to use them, they won’t be affected. But we recommend you start using the OpenXML nodes.
There are a few bugs and limitations with OpenXML nodes (such as recalculating Excel tables once updated based on formulas), that we are actively working on to bridge the gap before completely obsoleting the legacy Excel nodes. You’ll see improvements in future releases.