Inventor BIM Export to Revit Family (Bug?)

[SteveK88]

When exporting a ipt to a Revit Family using the BIM Content Environment the new rfa cannot be exploded in Revit.  This is due to having a Mirror Feature in the Inv ipt.
When the Mirror feature is removed, the rfa can be exploded.  We must have exploded rfas to select Faces in Revit.
Using Inv 2026.3 & Revit 26.4.10.51

[SharkDesign]

Did you simplify the part first? That could be your issue. 

Could be a bug though as Inventor does not send features to Revit, it converts them all to an intermediate file first and then into RFA. 

[Yijiang.Cai]

@SteveK88 I could reproduce the issue, and it has been tracked as [INVGEN-91777] for investigation. 

Will keep you updated, and many thanks!

[rena_andrews · Accepted solution]

Hi @SteveK88, many thanks for reporting the issue! While I also see the issue using Inventor 2026.3, it appears to be fixed testing on a recent 2026.4 internal build + Revit 2026.4.1 and Inventor 2027.0.1 + Revit 2027.0.2. Hopefully you can get the fix soon.

Thanks,

Rena

[SteveK88]

Hi, is there a date for the release of 2026.4?
This is becoming a larger issue for us.
We are also using Delete Face in Inventor to simplify before going into Revit.  Is it known if this 2026.4 will also support rfa expode if Delete Face is used?

[rena_andrews]

Hi @SteveK88, thanks for the follow-up. While we don't have a public release date for Inventor 2026.4 yet, I would estimate August or September at the latest.

The good news is I'm still able to do a Partial and Full explode after exporting your sample file SEFCOR AFNC2-20-4B.ipt and some other test files containing Mirror features to RFA using the latest 2026.4 internal build.

However, I get the same explode error when I include a Delete Face feature in your part. After investigating further, I realized that it unfortunately appears no surface bodies can be exploded in Revit, and it looks like using Delete Face causes the entire solid body containing the face to be converted into a Surface body. If there's at least one solid body, instead of showing an error, all of the other surface bodies seem to disappear during the Explode command, so only the solid bodies can be exploded. I created a defect to investigate adding support for exploding surface bodies [INVGEN-92297]. 

I'm not sure the exactly how you're trying to simplify, but I tried using the newer Part Simplify command to simplify some features instead of Delete Face and was able to explode the resulting RFA in Revit (I suppose since it doesn't create any surface bodies). This may not be sufficient since you're trying to delete entire/specific faces, but can the ability to exclude solid bodies and features using Part Simplify serve as a partial workaround in the meantime?

Thank you once again for the extremely valuable feedback! 

Best,

Rena

[SteveK88]

Hi Rena, thank you for the replies.

We are using the Simplify tool Remove Details. This allows us to be specific on the details removed and not a general overall remove details.  Please see image.
The Part Simplify that you are speaking of is too general for us.
Many components we receive or use from our Inventor libraries have more detail than what we need in the Revit construction.

[SteveK88]

Hi Rena, I did some further testing.  It might be not the remove face but the Thread Images.  The part I had has threads created in Inv. Once I suppressed the bolting in the part, I was able to explode in revit. It made sense now as you mentioned surface bodies.

Attached is the problem part with suppressed bolting. Suppressing the bodies that had threaded features allowed me to explode the resultant rfa.

[rena_andrews]

Hey Steve, thanks for investigating it further! Yes, I can also still explode that file with DeleteFace, thanks for sharing this example. Would it be possible to share the reference for the suppressed bolting, so I can reproduce that specific explode issue and update the defect? (Feel free to send it via direct message if you prefer). I tried adding some basic threads to that part and exporting some other parts with thread features, but I was still able to explode the RFA after exporting from 2026 and an internal 2026.4 build, so maybe there's a more specific thread feature causing the issue with your file? Either way, it would be great for me to reproduce it so we can also try to fix it. Thanks in advance!