|
| ValuationRequest (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), OrderFlowConfiguration includeOrderFlow=default(OrderFlowConfiguration), List< PortfolioEntityId > portfolioEntityIds=default(List< PortfolioEntityId >), ValuationSchedule valuationSchedule=default(ValuationSchedule), MarketDataOverrides marketDataOverrides=default(MarketDataOverrides), ResourceId corporateActionSourceId=default(ResourceId)) |
| Initializes a new instance of the ValuationRequest 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 (ValuationRequest input) |
| Returns true if ValuationRequest 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...
|
|
OrderFlowConfiguration | IncludeOrderFlow [get, set] |
| Gets or Sets IncludeOrderFlow More...
|
|
List< PortfolioEntityId > | PortfolioEntityIds [get, set] |
| The set of portfolio or portfolio group identifier(s) that is to be valued. More...
|
|
ValuationSchedule | ValuationSchedule [get, set] |
| Gets or Sets ValuationSchedule 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 a valuation
List<string> Lusid.Sdk.Model.ValuationRequest.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 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.ValuationRequest.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.