/ doc / toc / ARCCore / Enum / Cardinality / IndividualItems / __TOCDet / Attribute / Description

Description

Edit keys at this level only

= Values are supposed to be set and 'deleted' individually.0x000D0x000A0x000D0x000ATypical example could be Customer/PhoneNumber0x000D0x000AThe -PropertyStream- / API-calls should look something like this:0x000D0x000ACustomer/42/PhoneNumber/90534333  // Add number0x000D0x000ACustomer/42/PhoneNumber/40178178  // Add number0x000D0x000ACustomer/42/PhoneNumber/90534333.Invalid = 2020-03-20  // 'Delete' individual number0x000D0x000ACustomer/42/PhoneNumber/Invalid = 2020-03-21  // 'Delete' all numbers0x000D0x000A0x000D0x000ANote how the actual values are used as identifisers (keys).0x000D0x000A0x000D0x000AThe collection of items is stored in a -IPII- instance (typical -PII-).0x000D0x000A(specially recognized by -TryParse- and -TryStore-.0x000D0x000A)0x000D0x000ANote 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.0x000D0x000A0x000D0x000ANote that you can use -IndividualItems- as a simple mechanism for supporting -ManyToManyRelations-.0x000D0x000A

Edit keys at all sub levels.
NOTE: Edits are always additive. Use 'Invalid' in order to delete keys.

Generated 2026-09-11 08:51:55.050 UTC