When converting IFC objects to native Tekla Structures objects, a new profile is added to the existing profile catalog although there already is an equivalent one. Why this is happening?
Environment
Not environment-specific
Question:
When converting beams from an imported IFC reference model to native Tekla Structures beams, the conversion insists on creating a new profile, e.g. MET-232Z18-1, although the Tekla Structures profile cross-section database contains a MET-232Z18. Is it possible to stop this from happening and to get the profiles mapped?
Image
Answer:
Although the cross-section dimensions are equal, in some cases this happens because the rotation of the profile in the reference IFC file does not match the orientation (rotation) to the profile in the Tekla Structures profile catalog. This is why a new profile cross-section is created in the profile catalog.
If you selected the converted profile and changed its profile from, e.g. MET-232Z18-1 to MET-232Z18, the element would probably be rotated.
Image
| If you are not satisfied with the fact that a new profile definition name is created, then the easiest way to solve this issue is to create a selection filter based on the part profile and change it. |