Issue Exporting to Excel since upgrade to 2024

Hello, I have had a data export to excel functioning over the years on versions since 2019 and everything has been mostly ok. Since I just bumped up to 2024, upgraded the needed packages and tried to run the workflow I’m getting a strange result involving the ‘Data.ExportToExcel’ node.

All my list nodes/transposing ect seem to be giving correct results but when it hits the Excel export node I’m getting a repeated ‘System.Collections.ArrayList’.

Any help would be greatly appreciated

Many Thanks in Advance

Looks like you are providing a CAV as the input file. Try the write to CSV node instead of the excel one.

If you want to keep the excel, I recommend using the OpenXML excel nodes as hey are more stable (any Microsoft update can break the old nodes functionality).

Hi Jacob

Thanks for replying. I tried both the CSV method and the OPENXML and I still get the same result. I seem to get results all the way from each parameter up to list creation just fine its just the export portion its struggling with.


Check to see what data types you have in the list. It may be that you have something which doesn’t serialize to an array properly, such as an element, or enumerator.

Take the last list out of what you are sending into the data input (List.LastItem) and get the data type (Object.Type), then pull the unique items from there (List.UniqueItems).

Those should all be basic data types (strings, doubles, integers, etc.).

All seem to be System.String

Try a List.Count with the levels set to @L2. Somewhere on here there is a data type which is off or a data structure which is off.

Expand all data previews, zoom tight to one node, and export the canvas as an image.

Please see below

COMMS EXPORT IMage 2.pdf (2.3 MB)

Thanks again for the continued help

Try the Object.Type > List.Unique with the input set to @L2 after the List.Transpose. One thought is the type or instance parameter is throwing things off.

Make sure the level is set right. Everything in there should be a string or similar. If that does t work you’ll have to post your dyn and a source rvt.

Yeah ok so when i added i can see it changing at the transpose node.

Set the list level to @L1 on the Object.Type node.

Still the same

Ok… now this is weird.

Try the Object.Type followed by List.UniqueItems before the transpose, before the List.Create, all over the graph as you go. The goal is to find the odd thing in the dataset - a null, empty list, or other oddity.

If nothing turns up, post a sample rvt to reproduce the issue and your DYN so we can help more directly.

The best way to test if it’s the excel node or your data is to send in a very basic 2D list and see if it’s a consistent issue. Recommend doing that before we dive right into the data itself…

Ok i made a very basic list of 1 element and 2 parameters off that element and it works

I then expanded it back to All my objects again but still only drawing the 2 parameters and im back to the error. I tried it with and without a transpose

Ok - this is feeling like an Add-In conflict. Disable all of your Revit add-ins, restart the CPU, and then see if it reproduces.

If so then force quit Revit (don’t close anything after you get the warning) and post your Revit journal from that session. I

f it doesn’t reproduce with add-ins disables, then re-enable all the add-ins and see if the issue comes back. if the issue comes back after re-enabling, post both of the journals from the re-enabled and disabled sessions so we can find the difference.

Ok thanks for dealing with my spam. Item has been resolved. I turned off Rhythm and Orchid and replaced the nodes from those apps I’ve used for the last 3-4 REVIT versions and it is exporting ok now.

Again thanks for the rapid support and apologies for the spam.

3 Likes

Rhythm should be fine - reinstall it from the package manager and it will put the latest and correct version into place.

The Orchid Package may be problematic, but even that is fairly unlikely. Try to get the latest installed and see if that fixes things. If not best to reach out on the project a GitHub (linked above).

Thanks, will keep troubleshooting after now that i know i can get something to work when its going to be critical in the next month.

Those 2 are the only packages i have installed so Its down to one of them.

Many thanks again for the help

Could also be something in Revit causing the issue as those packages are built very well. Disabling Revit add-ins is a must for troubleshooting these kinds of issues (and checking the Revit journals).

Sharing this here too:

1 Like