Custom data models

You can create custom data models (CDM) for certain LUSID entity types in order to:

• Control which identifiers and/or properties can be added to entities of these types.

• Mandate that users must enter values for these identifiers and properties, rather than leaving them blank.

• Set display preferences when entities are listed in LUSID web app dashboards.

CDMs are currently available for the following entity types:

• Instrument

• Order

• Transaction (this and other entity types coming soon)

For example, you could create a CDM for instruments that mandates users must enter a FIGI identifier and a ‘country code’  property value. No other identifiers or properties are allowed.

You could go further and create multiple, nested CDMs for particular instruments in order to create a hierarchy that helps classify your data universe. For example, you could designate the CDM described above as the ‘parent’ applicable to all instruments, and then create two ‘child’ CDMs applicable to:

1. Instruments of type Bond that further mandates users must enter an ISIN identifier.

2. Instruments of type Equity that further mandates users must enter an ‘exchange code’ property value.

See how to set this scenario up.