Common¶
| Attribute | Description |
|---|---|
| id | The identifier of the core object (Guid) |
| joinScope | The join scope used by sync rules |
| anchor1 | Generic anchor useful for synchronizing objects |
| anchor2 | Generic anchor useful for synchronizing objects |
| anchor3 | Generic anchor useful for synchronizing objects |
| anchor4 | Generic anchor useful for synchronizing objects |
| anchor5 | Generic anchor useful for synchronizing objects |
| anchor6 | Generic anchor useful for synchronizing objects |
| anchor7 | Generic anchor useful for synchronizing objects |
| anchor8 | Generic anchor useful for synchronizing objects |
| anchor9 | Generic anchor useful for synchronizing objects |
Custom string values¶
It is possible to flow string data into any core attribute named custom/something. This means that if you want to store information that does not really belong in any standard attribute, let's say "License plate", you can name it something like custom/license_plate* and it will be stored.