Root / Assembly / ARCCore / AREnumType / OrdinaryEnum / Cardinality / _Member / WholeCollection

EnumMemberAttribute

WholeCollection

KeyValue
DescriptionValues are always set as a whole (there is no need or no meaning in setting or deleting individual items)
Typical example could be PizzaOrder/Extra
The PropertyStream / API-calls should look something like this:
PizzaOrder/42/Extra = Pepperoni, Cheese, Sauce // Set whole collection
PizzaOrder/42/Extra.Invalid = 2020-03-20 // 'Delete' all items.

Note that you can use WholeCollection as a simple mechanism for supporting ManyToManyRelations.
EnumMemberWholeCollection
EnumTypeARCCore.Cardinality
LongDescriptionThe internal representation in IP would probably be a List<PValue<T>> (this would be more memory-efficient than IndividualItems)

Note that in principle all data that can be stored as WholeCollection can also be stored as IndividualItems but the client interaction is probably easier to implement with the former. You should also consider how you want historical representations of changes in the data to look when choosing between these two.

4 items


Generated 2020-10-13 11:11:01.341 UTC