Duplicate IFC Export over Multiple Documents

Revit
1

Hi @Alban_de_Chasteigner,

I’m currently working on exporting IFC views from approximately 50 documents and came across a similar thread while testing my workflow.

My script is nearly complete, but I’ve noticed an issue: it only returns the IFC view from the active document. For the other files, the IFC view is either null or blank. Although the output reports a successful execution, when I open the exported files, I find that the same IFC view from the active document has been exported repeatedly across all four files.

I’m trying to understand what might be causing this behavior. Has anyone encountered a similar issue, or does anyone have suggestions on what I should check?

Any guidance would be greatly appreciated. Thanks!

IFC_Export_2026-08-13_08-36-24
IFC_Export_2026-08-13_08-36-245996×1862 574 KB

2

Python code in Export IFC in Document only takes the first document

if inputdoc[0] == None:
    doc = DocumentManager.Instance.CurrentDBDocument
elif inputdoc[0].GetType().ToString() == "Autodesk.Revit.DB.Document":
    doc = inputdoc[0]
else:
    doc = DocumentManager.Instance.CurrentDBDocument
3

Hi Mike,
Great news, the script seems to export the individual files. The python code remains unchanged and the current settings are simplified.
Looking ahead, would it be possible to add more flexibility to the Python code or the Export IFC custom node, particularly when:

  • “Export User Defined Psets” is true.
  • There are two shared coordinate systems available for export.
4

yeah as Mike say…why not try create a solution with birdtool multiplayer and run document by document

5

and PS for Pset shouldnt that isnst should be path for that…not sure…

6

From what I understand, that would simplify the script as well. Thanks for your perspective.

7

yes just more simple and guess stable as well…instead of background open in dynamo :wink: i always do these task that way, if that is possible :wink:

8

You can probably use list levels to solve this also in a single run, but agree dynamo multiplayer is great for solving a single run that you want replicated over multiple documents, especially if ACC is involved.

Having had to make a remote tasker runner internally at work in c# I have great respect for it.

9

Yeaps Gavin always respect for data…hahaha :wink: