sdk.lusid.models.data_mapping.DataMapping

class DataMapping(**data)

When importing data from an external source there are essentially three levels of interaction with LUSID. (1) The data is a raw document that LUSID does not understand. You can store and retrieve it but it does not full interact with other documents inside LUSID (2) The data has a map from fields and paths to ‘properties’ in LUSID. In essence, LUSID can then treat the data as weakly typed (decimal, string) data that can be returned through queries and where various aggregation requests will then work. (3) The data is fully translatable into LUSID and understood, in some sense, natively. This means that it can be used for context sensitive calculations such as pricing or risk calculations. The data map object is designed to allow data to transition from step 1 to 2 and in some cases as an alternative for step 2 to 3. # noqa: E501

Create a new model by parsing and validating input data from keyword arguments.

Raises ValidationError if the input data cannot be parsed to form a valid model.

Attributes

This is a Pydantic class. For now, click on the green [source] link in the class signature above to see descriptions/allowed values for these attributes.

data_definitions

class Config

Pydantic configuration

classmethod from_dict(obj)

Create an instance of DataMapping from a dict

Return type:

DataMapping

classmethod from_json(json_str)

Create an instance of DataMapping from a JSON string

Return type:

DataMapping

to_dict()

Returns the dictionary representation of the model using alias

to_json()

Returns the JSON representation of the model using alias

Return type:

str

to_str()

Returns the string representation of the model using alias

Return type:

str