topic Importing STEP with Creo API in Customization

Importing STEP with Creo API

TL_12988429 — Tue, 23 Dec 2025 22:50:39 GMT

Creo VB API Type Library for Creo Parametric 8.0.0.0 Version 1.0

Creo Parametric 9.0.0.2

The Creo API call to

IpfcBaseSession m_session; m_session.ImportNewModel(filePath, (int)EpfcNewModelImportType.EpfcIMPORT_NEW_STEP, (int)EpfcModelType.EpfcMDL_ASSEMBLY, "temp", null);

does not match the importing that I did by hand. I get the following error message (repeated for each feature as it tries to import the file, there are 155 features/bodies in the step file) which doesn't happen when I import the step by hand.

"Warning: Design intent is unclear in FEATURE_155. Use Geometry Checks command on the Tools Tab in Part mode for more information."

Why does this method check design intent when opening the file through the UI doesn't?

Full use case:

I'd like to use Creo to apply boolean operations to STEP bodies. I've added all of these bodies to a single STEP file and would like to import it into Creo via the COM API using C#.

Before getting into the code, I've confirmed my use case works using Creo with the following steps.
1. Use the "File Open" dialog to select my step file.

2. Import my step file as an assembly with automatic import type using the "Import New Model" dialog.
3. Creo now processes each feature in the step file and creates an assembly with each body in the step being a separate part.

4. Model > Component > Component Operations > Boolean Operations.

5. Select the "Cut" operation and set "Modified Models" to the part I want to subtract from.

6. Set "Modifying Components" to the parts I want to subtract with and accept.

7. Creo now applies the cuts

8. Delete or hide the parts that were used for the cut. Leaving me with a single final part.

These are the steps I want to recreate with the COM API. I am new to the Creo and its API but used to C#. I'd like to know why it doesn't match my operations when done through the UI.

This is my code so far

using System; using pfcls; string m_exePath = @"C:\Program Files\PTC\Creo 9.0.2.0\Parametric\bin\parametric.exe"; IpfcAsyncConnection m_asyncConnection; IpfcBaseSession m_session; string filePath = ""; // Hidden for privacy try { CCpfcAsyncConnection cAC = new CCpfcAsyncConnection(); m_asyncConnection = cAC.Start(m_exePath, null); m_session = (IpfcBaseSession)m_asyncConnection.Session; IpfcModel model = m_session.ImportNewModel(filePath, (int)EpfcNewModelImportType.EpfcIMPORT_NEW_STEP, (int)EpfcModelType.EpfcMDL_ASSEMBLY, "tmp2115", null); } catch (Exception e) { throw e; }

I'd appreciate any insight. Is there a different way to import that would match the way I did it in the UI? Or do I need to set something else up different or change settings before the import in the code?

Thank you and happy holidays!

Tristan | Software Developer

Re: Importing STEP with Creo API

anursingh — Mon, 29 Dec 2025 16:29:09 GMT

Hi @TL_12988429,

Thank you for your question.

Your post appears well documented but has not yet received any response. I am replying to raise awareness. Hopefully, another community member will be able to help.

Also, feel free to add any additional information you think might be relevant. It sometimes helps to have screenshots to better understand what you are trying to do.

Regards,

Anurag

Re: Importing STEP with Creo API

TL_12988429 — Mon, 05 Jan 2026 18:08:00 GMT

Thank you for the bump Anurag, I appreciate it.

Unfortunately I still haven't figured out exactly how to get everything working. Though I now understand that though I get the error messages, the import is actually completed, I just needed to display the model. I still need to figure out how to select the features, and apply the boolean operation.

I have also created a mapkey to automate the UI commands, hopefully this can help guide anyone willing to help.

mapkey 4 @MAPKEY_LABELCut;~ Command `ProCmdModelOpen` ;\ mapkey(continued) ~ Trail `UI Desktop` `UI Desktop` `DLG_PREVIEW_POST` `file_open`;\ mapkey(continued) ~ Activate `file_open` `SAB_C:path\\hidden\\for\\privacy>`;\ mapkey(continued) ~ Select `file_open` `Ph_list.Filelist` 1 `tmp`;\ mapkey(continued) ~ Activate `file_open` `Ph_list.Filelist` 1 `tmp`;\ mapkey(continued) ~ Trail `UI Desktop` `UI Desktop` `PREVIEW_POPUP_TIMER` \ mapkey(continued) `file_open:Ph_list.Filelist:<NULL>`;~ Open `file_open` `Type`;\ mapkey(continued) ~ Close `file_open` `Type`;\ mapkey(continued) ~ Select `file_open` `Type` 1 `filter_.stp,.step,`;\ mapkey(continued) ~ Select `file_open` `Ph_list.Filelist` 1 `tmpB953.stp`;\ mapkey(continued) ~ Activate `file_open` `Ph_list.Filelist` 1 `tmpB953.stp`;\ mapkey(continued) ~ Activate `impt_new_model` `PushButton3`;\ mapkey(continued) ~ Expand `main_dlg_cur` `PHTLeft.AssyTree` `T1 2`;\ mapkey(continued) ~ Trail `UI Desktop` `UI Desktop` `PREVIEW_POPUP_TIMER` \ mapkey(continued) `main_dlg_w1:PHTLeft.AssyTree:<NULL>`;~ Command `ProCmdMmCompOper` ;\ mapkey(continued) #BOOLEAN OPERATIONS;\ mapkey(continued) ~ Trigger `boolean_op_dlg` `BoolOpTargetComponentsLst` `0`;\ mapkey(continued) ~ Trigger `boolean_op_dlg` `BoolOpTargetComponentsLst` ``;\ mapkey(continued) ~ Trigger `boolean_op_dlg` `BoolOpSourceModelsLst` `0`;\ mapkey(continued) ~ Trigger `boolean_op_dlg` `BoolOpSourceModelsLst` ``;\ mapkey(continued) ~ Open `boolean_op_dlg` `BoolOpOperationOpt`;\ mapkey(continued) ~ Close `boolean_op_dlg` `BoolOpOperationOpt`;\ mapkey(continued) ~ Select `boolean_op_dlg` `BoolOpOperationOpt` 1 `BoolOpCutSelectOpt`;\ mapkey(continued) ~ Trigger `boolean_op_dlg` `BoolOpSourceModelsLst` `0`;\ mapkey(continued) ~ Trigger `boolean_op_dlg` `BoolOpSourceModelsLst` ``;\ mapkey(continued) ~ Select `main_dlg_cur` `PHTLeft.AssyTree` 1 `T2 2 2`;\ mapkey(continued) ~ Trigger `boolean_op_dlg` `BoolOpTargetComponentsLst` `0`;\ mapkey(continued) ~ Trigger `boolean_op_dlg` `BoolOpTargetComponentsLst` ``;\ mapkey(continued) ~ Focus `boolean_op_dlg` `BoolOpTargetComponentsLst`;\ mapkey(continued) ~ Select `boolean_op_dlg` `BoolOpTargetComponentsLst` 0;\ mapkey(continued) ~ Timer `UI Desktop` `UI Desktop` `CollectorWdg_FocusTimer`;\ mapkey(continued) ~ Select `main_dlg_cur` `PHTLeft.AssyTree` 1 `T2 2 3`;\ mapkey(continued) ~ Select `main_dlg_cur` `PHTLeft.AssyTree` 2 `T2 2 3` `T2 2 4` 1;\ mapkey(continued) ~ Activate `boolean_op_dlg` `BoolOpOkBtn`;#DONE/RETURN;\ mapkey(continued) ~ Select `main_dlg_cur` `PHTLeft.AssyTree` 1 `T2 2 3`;\ mapkey(continued) ~ Command `ProCmdViewHide@PopupMenuTree` ;\ mapkey(continued) ~ Select `main_dlg_cur` `PHTLeft.AssyTree` 1 `T2 2 4`;\ mapkey(continued) ~ Command `ProCmdViewHide@PopupMenuTree` ;\ mapkey(continued) ~ Command `ProCmdEnvShadedEdges` 1;

Along with an example step file with which I am testing this command.