---
title: "InsertArticleOptions"
slug: "api/basket/operations/insertarticleoptions"
sidebar:
  order: 428
---

<a id="ref-1fa83b0e9bd0"></a>
<a id="ref-f9308300ee96"></a>
<a id="ref-99583b0f05e9"></a>

## Synopsis

```text
struct InsertArticleOptions (
    boolean noComplexType,
    AttachmentMode attachmentMode,
    PlanningDirection planarPlanningDirection,
    SpatialPlanningDirection spatialPlanningDirection,
    boolean strictVarCode,
    boolean migrate,
    string attachPoint,
    string? preConfigurationActionId
)
```

See also: [`AttachmentMode`](/pCon/configuratorOnline/specs/api/basket/types/attachmentmode#ref-7491b1638a1b), [`PlanningDirection`](/pCon/configuratorOnline/specs/api/basket/operations/insertofmlarticle#ref-137879d7cbd8), [`SpatialPlanningDirection`](/pCon/configuratorOnline/specs/api/basket/operations/insertofmlarticle#ref-f20e9b1290f0)

The optional options parameter references an instance of the InsertArticleOptions structure with the following optional fields:

**`noComplexType`**

Basically, a single article can be inserted as an ordinary OFML article (item type Article) or as a complex article1 (item types Aggregate and PartialPlanning). The OFML data for a particular article may support insertion as an ordinary article or insertion as a complex article, or both. If both possibilities are supported, the noComplexType option, if set to true, causes the article to be inserted as an ordinary article. The default value is false (i.e., articles are inserted as complex articles whenever possible).

**preConfigurationActionId**

Optional OAP action ID of a pre-configuration dialog. A non-empty value must identify such a dialog. The server calls the OFML startPreConfiguration method; if it returns a non-zero value, the inserted main article enters pre-configuration. Automatic insertion of add-ons is suppressed when insertion enters this state. [ArticleData](/pCon/configuratorOnline/specs/api/basket/types/articledata) and [ArticleProperties](/pCon/configuratorOnline/specs/api/basket/types/articleproperties) return preConfigurationData while pre-configuration is active. The client must call [oapFinishPreConfiguration](/pCon/configuratorOnline/specs/api/basket/operations/oapfinishpreconfiguration) to apply the changes or cancel and delete the article. Pre-configuration survives session suspend/resume but is not stored in OBK/OBX files.
