---
title: "getMultiArticleFeatures"
slug: "api/basket/operations/getmultiarticlefeatures"
sidebar:
  order: 450
---

<a id="ref-ce79f813453b"></a>
<a id="ref-a48bd848690c"></a>
<a id="ref-eac6767f7859"></a>

## Synopsis

```text
ArticleFeatures[] getMultiArticleFeatures
(SessionId sessionId,
    UUID[] itemIds,                                                 GetMultiArticleFeaturesOptions? Options)
throws BasketServiceFault;
```

See also: [ArticleFeatures](/pCon/configuratorOnline/specs/api/basket/types/articlefeatures#ref-42257ac6b399), [SessionId](/pCon/configuratorOnline/specs/api/session/types/sessionid#ref-02e397c8fdb4), [GetMultiArticleFeaturesOptions](/pCon/configuratorOnline/specs/api/basket/types/getmultiarticlefeaturesoptions#ref-5fa969afc639), [BasketServiceFault](/pCon/configuratorOnline/specs/api/basket/faults/basketservicefault#ref-d5adb74faa1b), [`UUID`](/pCon/configuratorOnline/specs/guide/web-service-interfaces/common-type-definitions/uuid)

Operation `getMultiArticleFeatures` is a more powerful variant of operation `getArticleFeatures` (§[getArticleFeatures](/pCon/configuratorOnline/specs/api/basket/operations/getarticlefeatures#ref-df1c952ed3e9)). It allows the client

- to query features of multiple articles in one go, and

- to use view item IDs instead of basket item IDs (if field `viewId` of parameter `options` is set accordingly).

The selection of items whose article features are to be returned is performed as usual using the basket or view item IDs specified with parameter `itemIds` and the subset of [`ItemSelectionOptions`](/pCon/configuratorOnline/specs/api/basket/types/itemselectionoptions) passed with parameter `options`. Once the initial set of selected items has been determined, non-article items are removed from the set (user- and set-article items are retained even though they always report an empty list of article features (at least with the current implementation)).

It is not an error to explicitly specify the ID of a non-article item, regardless of the set of item selection options being used. In particular, specification of the top folder ID in combination with item selection option `subItems` set to `true` may be used to fetch the features of all article items.

Once the set of article items has been determined, the operation fetches the article features of each article item and returns them using one element of type `ArticleFeatures` (§[ArticleFeatures](/pCon/configuratorOnline/specs/api/basket/types/articlefeatures#ref-42257ac6b399)) for each article item, with field `itemId` holding the basket or view item ID of the corresponding article item, and field `features` holding the list of individual article features as they would be returned by operation [`getArticleFeatures`](/pCon/configuratorOnline/specs/api/basket/operations/getarticlefeatures).

The order of [`ArticleFeatures`](/pCon/configuratorOnline/specs/api/basket/types/articlefeatures) elements in the return value is unspecified.

Note: Fields `description` and `noInternal` of type `GetMultiArticleFeaturesOptions` (§[GetMultiArticleFeaturesOptions](/pCon/configuratorOnline/specs/api/basket/types/getmultiarticlefeaturesoptions#ref-5fa969afc639)) are encoded as attributes, even though the same fields of type `GetArticleFeaturesOptions` (§[GetArticleFeaturesOptions](/pCon/configuratorOnline/specs/api/basket/types/getarticlefeaturesoptions#ref-c9c4ae45ca97)) are encoded as elements.
