Lusid.AborConfiguration

Providing you have sufficient access control permissions, the Lusid.AborConfiguration provider enables you to write a Luminesce SQL query that retrieves ABOR configuration modules stored in LUSID.

Note: By default, Lusid.AborConfiguration cannot retrieve properties for modules. To do this, you must first configure Lusid.AborConfiguration to 'inline' properties. See how to do this.

See also: Lusid.AborConfiguration.Writer

Basic usage

select * from Lusid.AborConfiguration where <filter-expression>;

Query parameters

Lusid.AborConfiguration 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:

select FieldName, DataType, ParamDefaultValue, Description from Sys.Field where TableName = 'Lusid.AborConfiguration' and FieldType = 'Parameter';

Data fields

By default, Lusid.AborConfiguration 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:

select FieldName, DataType, IsMain, IsPrimaryKey, SampleValues, Description from Sys.Field where TableName = 'Lusid.AborConfiguration' and FieldType = 'Column';

Note: Fields marked 'main' are returned by queries that select a caret character, for example select ^ from Lusid.AborConfiguration.

Examples

Note: For more example Luminesce SQL queries, visit our Github repo.

Example 1: Retrieve every module

select * from Lusid.AborConfiguration;

Example 2: Retrieve modules that do not use a particular CoA

select * from Lusid.AborConfiguration where ChartOfAccountsCode != 'default';

Example 3: Retrieve modules that use a particular recipe

select * from Lusid.AborConfiguration where RecipeScope = 'FBNUniversity' and RecipeCode = 'StandardValuation';