Type | Read/write | Author | Availability |
Read | Finbourne | Provided with LUSID |
Providing you have sufficient access control permissions, the Lusid.Portfolio.Constituent
provider enables you to write a Luminesce SQL query that retrieves constituents from one or more LUSID reference portfolios.
Note: By default,
Lusid.Portfolio.Constituent
cannot retrieve reference holding properties. To do this, you must first configureLusid.Portfolio.Constituent
to 'inline' properties. See how to do this.
See also: Lusid.Portfolio.Constituent.Writer
Basic usage
Query parameters
Lusid.Portfolio.Constituent
has parameters that enable you to filter or refine a query.
To list available parameters, their data types, default values, and an explanation for each, run the following query using a suitable tool:
Data fields
By default, Lusid.Portfolio.Constituent
returns a table of data populated with particular fields (columns). You can return a subset of these fields.
To list fields available to return, their data types, whether fields are considered 'main', and an explanation for each, run the following query using a suitable tool:
Note: Fields marked 'main' are returned by queries that start
select ^ from Lusid.Portfolio.Constituent...
Examples
Note: For more example Luminesce SQL queries, visit our Github repo.
Example 1: Retrieve constituents in every portfolio
Example 2: Retrieve constituents in a particular portfolio
Example 3: Retrieve constituents whose floating weight is greater than initial weight on a particular day
Example 4: Show the friendly name of underlying instruments for constituents
It's typically useful to join to the Lusid.Instrument
provider in order to retrieve the friendly name of underlying instruments. Note that since both providers have a DisplayName
field, only that of Lusid.Instrument
is returned in order to avoid a duplicate column clash: