|
| | InlineValuationRequest (ResourceId recipeId=default(ResourceId), DateTimeOffset? asAt=default(DateTimeOffset?), List< AggregateSpec > metrics=default(List< AggregateSpec >), List< string > groupBy=default(List< string >), List< PropertyFilter > filters=default(List< PropertyFilter >), List< OrderBySpec > sort=default(List< OrderBySpec >), string reportCurrency=default(string), bool equipWithSubtotals=default(bool), bool returnResultAsExpandedTypes=default(bool), ValuationSchedule valuationSchedule=default(ValuationSchedule), List< WeightedInstrument > instruments=default(List< WeightedInstrument >), MarketDataOverrides marketDataOverrides=default(MarketDataOverrides), ResourceId corporateActionSourceId=default(ResourceId)) |
| | Initializes a new instance of the InlineValuationRequest class. More...
|
| |
| override string | ToString () |
| | Returns the string presentation of the object More...
|
| |
| virtual string | ToJson () |
| | Returns the JSON string presentation of the object More...
|
| |
| override bool | Equals (object input) |
| | Returns true if objects are equal More...
|
| |
| bool | Equals (InlineValuationRequest input) |
| | Returns true if InlineValuationRequest instances are equal More...
|
| |
| override int | GetHashCode () |
| | Gets the hash code More...
|
| |
|
| ResourceId | RecipeId [get, set] |
| | Gets or Sets RecipeId More...
|
| |
| DateTimeOffset? | AsAt [get, set] |
| | The asAt date to use More...
|
| |
| List< AggregateSpec > | Metrics [get, set] |
| | The set of specifications to calculate or retrieve during the valuation and present in the results. For example: AggregateSpec('Valuation/PV','Sum') for returning the PV (present value) of holdings AggregateSpec('Holding/default/Units','Sum') for returning the units of holidays AggregateSpec('Instrument/default/LusidInstrumentId','Value') for returning the Lusid Instrument identifier More...
|
| |
| List< string > | GroupBy [get, set] |
| | The set of items by which to perform grouping. This primarily matters when one or more of the metric operators is a mapping that reduces set size, e.g. sum or proportion. The group-by statement determines the set of keys by which to break the results out. More...
|
| |
| List< PropertyFilter > | Filters [get, set] |
| | A set of filters to use to reduce the data found in a request. Equivalent to the 'where ...' part of a Sql select statement. For example, filter a set of values within a given range or matching a particular value. More...
|
| |
| List< OrderBySpec > | Sort [get, set] |
| | A (possibly empty/null) set of specifications for how to order the results. More...
|
| |
| string | ReportCurrency [get, set] |
| | Three letter ISO currency string indicating what currency to report in for ReportCurrency denominated queries. If not present, then the currency of the relevant portfolio will be used in its place. More...
|
| |
| bool | EquipWithSubtotals [get, set] |
| | Flag directing the Valuation call to populate the results with subtotals of aggregates. More...
|
| |
| bool | ReturnResultAsExpandedTypes [get, set] |
| | Financially meaningful results can be presented as either simple flat types or more complex expanded types. For example, the present value (PV) of a holding could be represented either as a simple decimal (with currency implied) or as a decimal-currency pair. This flag allows either representation to be returned. In the PV example, the returned value would be the decimal-currency pair if this flag is true, or the decimal only if this flag is false. More...
|
| |
| ValuationSchedule | ValuationSchedule [get, set] |
| | Gets or Sets ValuationSchedule More...
|
| |
| List< WeightedInstrument > | Instruments [get, set] |
| | The set of instruments, weighted by the quantities held that are required. It is identified by an identifier tag that can be used to identify it externally. For a single, unique trade or transaction this can be thought of as equivalent to the transaction identifier, or a composite of the sub-holding keys for a regular sub-holding. When there are multiple transactions sharing the same underlying instrument such as purchase of shares on multiple dates where tax implications are different this would not be the case. More...
|
| |
| MarketDataOverrides | MarketDataOverrides [get, set] |
| | Gets or Sets MarketDataOverrides More...
|
| |
| ResourceId | CorporateActionSourceId [get, set] |
| | Gets or Sets CorporateActionSourceId More...
|
| |
Specification object for the parameters of an inline valuation
| List<string> Lusid.Sdk.Model.InlineValuationRequest.GroupBy |
|
getset |
The set of items by which to perform grouping. This primarily matters when one or more of the metric operators is a mapping that reduces set size, e.g. sum or proportion. The group-by statement determines the set of keys by which to break the results out.
The set of items by which to perform grouping. This primarily matters when one or more of the metric operators is a mapping that reduces set size, e.g. sum or proportion. The group-by statement determines the set of keys by which to break the results out.
The set of instruments, weighted by the quantities held that are required. It is identified by an identifier tag that can be used to identify it externally. For a single, unique trade or transaction this can be thought of as equivalent to the transaction identifier, or a composite of the sub-holding keys for a regular sub-holding. When there are multiple transactions sharing the same underlying instrument such as purchase of shares on multiple dates where tax implications are different this would not be the case.
The set of instruments, weighted by the quantities held that are required. It is identified by an identifier tag that can be used to identify it externally. For a single, unique trade or transaction this can be thought of as equivalent to the transaction identifier, or a composite of the sub-holding keys for a regular sub-holding. When there are multiple transactions sharing the same underlying instrument such as purchase of shares on multiple dates where tax implications are different this would not be the case.
| List<AggregateSpec> Lusid.Sdk.Model.InlineValuationRequest.Metrics |
|
getset |
The set of specifications to calculate or retrieve during the valuation and present in the results. For example: AggregateSpec('Valuation/PV','Sum') for returning the PV (present value) of holdings AggregateSpec('Holding/default/Units','Sum') for returning the units of holidays AggregateSpec('Instrument/default/LusidInstrumentId','Value') for returning the Lusid Instrument identifier
The set of specifications to calculate or retrieve during the valuation and present in the results. For example: AggregateSpec('Valuation/PV','Sum') for returning the PV (present value) of holdings AggregateSpec('Holding/default/Units','Sum') for returning the units of holidays AggregateSpec('Instrument/default/LusidInstrumentId','Value') for returning the Lusid Instrument identifier
| bool Lusid.Sdk.Model.InlineValuationRequest.ReturnResultAsExpandedTypes |
|
getset |
Financially meaningful results can be presented as either simple flat types or more complex expanded types. For example, the present value (PV) of a holding could be represented either as a simple decimal (with currency implied) or as a decimal-currency pair. This flag allows either representation to be returned. In the PV example, the returned value would be the decimal-currency pair if this flag is true, or the decimal only if this flag is false.
Financially meaningful results can be presented as either simple flat types or more complex expanded types. For example, the present value (PV) of a holding could be represented either as a simple decimal (with currency implied) or as a decimal-currency pair. This flag allows either representation to be returned. In the PV example, the returned value would be the decimal-currency pair if this flag is true, or the decimal only if this flag is false.
