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

EnumMemberAttribute

IndividualItems

KeyValue
DescriptionValues are supposed to be set and 'deleted' individually.
Typical example could be Customer/PhoneNumber
The PropertyStream / API-calls should look something like this:
Customer/42/PhoneNumber/90534333 // Add number
Customer/42/PhoneNumber/40178178 // Add number
Customer/42/PhoneNumber/90534333.Invalid = 2020-03-20 // 'Delete' individual number
Customer/42/PhoneNumber/Invalid = 2020-03-21 // 'Delete' all numbers

Because of IdLooseStorage the actual values must be used as identifisers.
The collection of items is stored in a IPII instance (typical PII).
(specially recognized by TryParse and TryStore.
)
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.

Note that you can use IndividualItems as a simple mechanism for supporting ManyToManyRelations.
EnumMemberIndividualItems
EnumTypeARCCore.Cardinality

3 items


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