How to maintain sub assembly names

Hi

I am exporting a 3D CAD file to a Parasolid file using the A3DSDKHOOPSExchangeLoader.Convert function. However, the sub-assemblies in the Parasolid file do not retain the original names from the source file. What steps should be taken to ensure the parts and sub-assemblies in the target file maintain their original names?

Thanks

Hello @kokkilaa
Something that comes to mind is setting m_bStrictAssemblyStructure to true.
Could you please provide more information, such as screenshots (before and after converting to X_T)? It would also be great if you could share a sample CAD file—this would help us better understand the issue. Thank you!

Best Regards,
Man

Hi @Man,

I am exporting a 3D CAD file to a Parasolid file using the A3DSDKHOOPSExchangeLoader.Convert function through indirect integration. Despite setting m_bBStrictAssemblyStructure to TRUE, the subassembly names in the exported Parasolid file do not match the original names in the source file. Please refer to the attached image for reference:

The left side shows the original source 3D CAD file, while the right side displays the exported Parasolid file. The naming discrepancy is evident.

Could you guide me on how to ensure that the exported file retains the same subassembly names as the source file?

Thank you for your assistance.
Kokkilaa

Hello @kokkilaa
Thank you for the screenshot. I looked and found that the naming is to add “-” and a number at the end. I checked the team and we have not yet figured out what caused it. Therefore, if possible, I would like to ask for the CAD file or dummy file that reproduce the same issue. Thank you.

Best Regards,
Man

Hi @Man,

How to share the data? Please let me know. Those data will help you to verify the naming issue. Looking forward to your assistance.

Thank you,

Kokkilaa

Hello @kokkilaa,
I will send you a private message to guide you on how to share CAD data. Thank you.

Best Regards,
Man

Hi @Man,

Thanks for letting me know the procedure for uploading the files.

https://transfer.techsoft3d.com/link/j28rrlV6Ne6eYJZdPdIKmE

https://transfer.techsoft3d.com/link/MljBVbj0xOuCzSKhG22qxI

are the sample files’ links. Please check and reply for the query (naming issue) I have raised.

Regards,

Kokkilaa

Hi @Man,

I couldn’t send all the files together. So, sending another set by this mail.

https://transfer.techsoft3d.com/link/45nkEO6Hejz7Hn3nr0QyDv

https://transfer.techsoft3d.com/link/RPKeEM82ZB76mR2Ijpkd0q

Regards,

Kokkilaa

Hello @kokkilaa,
Thanks for the CAD files. I still can’t reproduce the issue above. See the comparison screenshots of SLDASM and X_T exported using HOOPS Demo Viewer 2025.4.0.

Attached is the export parameters used with the HOOPS Exchange sample ImportExport.

Could you reproduce the same issue using the default sample ImportExport? Could you provide more information, such as the HOOPS version, OS, and exported X_T in your environment? Thanks.

Best Regards,
Man