---
title: "SetPropertyValueOptions"
slug: "api/basket/types/setpropertyvalueoptions"
sidebar:
  order: 384
---

<a id="ref-54eba3defcd3"></a>
<a id="ref-f9e432e6e592"></a>

```text
struct SetPropertyValueOptions (
    boolean computeVisibilityChangeFlags,
    boolean computeValueChangeFlags,
    boolean computeChoiceListChangeFlags,
    boolean? EnableBooleanPropType,
)
```

The fields control whether certain flags in the return value of operation [`setPropertyValue`](/pCon/configuratorOnline/specs/api/basket/operations/setpropertyvalue) are computed. Not computing them may have a positive impact on performance.

The flags controlled by these fields, and their potential performance impact, are as follows:

**`computeVisibilityChangeFlags`**

The default value is true. If false, flags `S` and `H` are not computed. Setting this flag to `false` won't improve performance unless all flags are set to false, and even then the time saved in operation [`setPropertyValue`](/pCon/configuratorOnline/specs/api/basket/operations/setpropertyvalue) will probably later be spent in operation [`getArticleData`](/pCon/configuratorOnline/specs/api/basket/operations/getarticledata) (which would otherwise reuse the information cached during `setPropertyValue`).

**`ComputeValueChangeFlags`**

The default value is true. If false, flags V, v, U, and A are not computed. As of now, the effects on performance should be the same as described for `computeVisibilityChangeFlags`.

**`computeChoiceListChangeFlags`**

The default value is true. If false, flags C and I are not computed. Setting this flag to `false` will always speed up operation [setPropertyValue](/pCon/configuratorOnline/specs/api/basket/operations/setpropertyvalue), and should not have a negative effect on operation setArticleData. However, client's that use operation [`getAllChoiceLists`](/pCon/configuratorOnline/specs/api/basket/operations/getallchoicelists) after each invocation of `setPropertyValue` should not see a difference in overall performance.

**`enableBooleanPropType`**

The optional boolean field `enableBooleanPropType` enables boolean properties. Its default value is false, resulting in no change of behavior. Previously, boolean properties have been treated as properties of type `Numeric` with values one and zero for `true` and `false` when returned by operations [`getArticleData`](/pCon/configuratorOnline/specs/api/basket/operations/getarticledata), [`getChoiceList`](/pCon/configuratorOnline/specs/api/basket/operations/getchoicelist) and [getAllChoiceLists](/pCon/configuratorOnline/specs/api/basket/operations/getallchoicelists), or zero and non-zero for `false` and `true` when set with operation [`setPropertyValue`](/pCon/configuratorOnline/specs/api/basket/operations/setpropertyvalue).

If `enableBooleanPropType` is set to true, the behavior for boolean properties changes as follows:

- Operation [`setPropertyValue`](/pCon/configuratorOnline/specs/api/basket/operations/setpropertyvalue) expects argument value to be `true` or `false` instead of a numeric value (usually but not necessarily 1 or 0). For consistency with the handling of numbers, leading and trailing whitespace are ignored.

If option `enableBooleanPropType` is effectively false, operation [`getChoiceList`](/pCon/configuratorOnline/specs/api/basket/operations/getchoicelist) returns the value of boolean properties as `1` and `0` instead of `1.` and `0.` in field `value` of type [`PropertyValue`](/pCon/configuratorOnline/specs/api/basket/types/propertyvalue).
