Importing data from external file sources

Naming the FileControlSpec

The following fields allow you to define the name and categorisation of this FileControlSpec:

FileReference

Mandatory; a unique name you can use to reference this FileControlSpec in other jobs.

FileCategory

Category of the FileControlSpec (e.g. primary, auxiliary)

SFTP file retrieval parameters

If the integration retrieves files via SFTP, the following fields allow you to specify the source of the file to retrieve and how LUSID should transform it:

SftpServer

1-based index indicating which SFTP server to use (defined in system configuration).

SftpSourceFolder

The source folder path in the SFTP server (e.g. /acme/data/transactions).

DriveSubfolder

Mandatory; the LUSID Drive location to load files into. Supports {{COBDATE:format}} or {{FILEDATE:format}} patterns, for example COBDATE:yyyy-MM-dd

FileNameMask

Mandatory; a matching pattern to match files on (e.g. TRANSACTIONS_[COBDATE:yyyyMMdd_*.csv]). Uses COBDATE/FILEDATE substitution.

RenameAs

A name for the file once loaded into LUSID.

API file retrieval parameters

If the integration retrieves data from an API, the following fields allow you to specify details for the API LUSID should retrieve data from:

ApiRetrievalType

An enum value for the type of API retrieval out of the following:

• None

• Enfusion

ReportPath

The path to append to the API URL for retrieving reports, for example /api/holdings.

ReportFilter

A filter to apply to the report request URL, for example &valueDate=10/28/2026.

File import parameters

The following fields allow you to specify import configuration details:

DataReaderType

An enum value for the type of reader out of the following:

• CsvReader

MappingFile

The name of the mapping file for this integration in Drive.

ImportTypes

An array of any of the following data types the files in this integration can import:

• Instruments

• Holdings

• Portfolios (properties to existing portfolios)

• Transactions

• Quotes

• RelationalDatasets

MaxIngestionFailures

A limit for the number of ingestion failures that can occur for the file before LUSID stops the import.

Exception handling parameters

The following fields allow you to specify how LUSID should handle data quality check failures in runs of the integration:

WorkflowTaskScope and WorkflowTaskCode

The scope and code of a task definition in LUSID’s workflow service that LUSID should kick off a run of for DQ check failures.

LUSID data upsert parameters

The following fields allow you to specify how the integration should configure certain LUSID data points:

Scope

Specify a portfolio scope to only upsert holdings data to portfolios in the specified scope. This can be useful if you want to target a specific portfolio scope for holdings data imports, for example:

{
  "FileReference": "Holdings-Finbourne-Examples",
  "MappingFile": "holdings-mapping.json",
  "ImportTypes": ["Holdings"],
  "Scope": "Finbourne-Examples"
}

If no scope is specified, the integration processes all portfolios that match all other criteria, regardless of their scope.

CutLabel

Specify a LUSID cut label to use as the EffectiveAt datetime for all the data the integration upserts. Defaults to 00:00 UTC.

Third party integration parameters

The following fields allow you to specify fields required for certain third party integrations:

BloombergRefreshInstanceId

Optionally, specify an integration instance ID to populate the value of the Bloomberg Data Licence Per Security Instrument/LUSIDConfig-Bloomberg-DLPerSecurity/RefreshReferenceData property.

CsvSeparator

Specify one of the following options for the delimiter used in CSV import files:

• Comma: Comma-separated (,) values (default)

• Pipe: Pipe-separated (|) values

• None: Uses default behaviour

ColumnSpecs

Specify an array of the columns in your source file and how to reference them in this mapping file. Each list item should contain:

• ColumnHeader: The column name as it appears in the source file

• ColumnReference: A reference name ending in column to use throughout the mapping file

For example:

"ColumnSpecs": [
  {
    "ColumnHeader": "Instrument ID",
    "ColumnReference": "InstrumentIdColumn"
  },
  {
    "ColumnHeader": "Price",
    "ColumnReference": "PriceColumn"
  }
]

ValueSources

Specify an array of how to extract and transform values from columns in import files. Each list item should contain a unique reference Name ending in Value to use throughout the mapping file, and either:

• Value: Hardcode a specific value, for example:

  {
    "Name": "InstrumentScopeValue",
    "Value": "default"
  }

• ColumnReferences: A list of the columns that the value should be sourced from

For ColumnReferences you can additionally specify the following:

ValueConversion

Specify one of the following options to tell LUSID how to combine multiple columns:

• None: Takes the value from the first ColumnReference

  {
    "Name": "SedolValue",
    "ColumnReferences": ["SedolColumn"],
    "ValueConversion": "None"
  }

• Concatenate: Joins multiple ColumnReference values together using the specified ConcatenationSeparator

  {
    "Name": "FullNameValue",
    "ColumnReferences": ["FirstNameColumn", "LastNameColumn"],
    "ValueConversion": "Concatenate",
    "ConcatenationSeparator": " "
  }

• FirstNonEmpty: Uses the first non-empty ColumnReference value

  {
    "Name": "PreferredIdValue",
    "ColumnReferences": ["IsinColumn", "SedolColumn", "ClientIdColumn"],
    "ValueConversion": "FirstNonEmpty"
  }

ConcatenationSeparator

The separator to use when ValueConversion is set to Concatenate; defaults to a space (“ “)

ValueMapName

Specify the name of a ValueMap to use for the value transformation, for example:

{
  "Name": "TransactionTypeValue",
  "ColumnReferences": ["TxnTypeColumn"],
  "ValueMapName": "TransactionTypeMap"
}

Note

If the column value is not a key in the specified ValueMap, the framework throws an error. You should specify a DQChecks check that validates InMapKeys before applying the map, or ensure your ValueMap includes all possible input values.

MultiplierValueSourceName

For numeric values, use this field to specify one of the defined ValueSources or ConditionalValueSources to multiply the numeric value by, for example:

{
  "Name": "ScaledQuantityValue",
  "ColumnReferences": ["QuantityColumn"],
  "MultiplierValueSourceName": "ContractSizeValue"
}

This can be useful for things such as:

• Converting contract quantities to actual units

• Scaling prices by exchange rates

• Calculating total consideration

• Applying percentage conversions

Note

• The base value and multiplier value must be parsaeable as decimals.

• LUSID returns the multiplied result as a string.

• LUSID throws an error if parsing fails, detailing which value failed.

IsCurrencyIdentifier

Set to true to add the prefix CCY_ to each value, for example:

{
  "Name": "CurrencyInstrumentIdValue",
  "ColumnReferences": ["CurrencyCodeColumn"],
  "IsCurrencyIdentifier": true
}

With the above example, LUSID might transform an original value of USD to CCY_USD.

RowIdentificationSourceName

Specify which ValueSources or ConditionalValueSources to use for identifying rows in logging and error messages.

ConditionalValueSources

Allows you to specify an array of complex logic for value transformations based on conditions.

Each list item should contain:

• A unique reference Name ending in Value to use throughout the mapping file

• A list of ordered LogicalExpressions containing:

  • Condition: A LUSID filtering syntax expression to evaluate the value source against. It must use the format <ValueSource/ConditionalValueSource> <Operator> <Specific value/ValueSource/ConditionalValueSource>.

    Supported operators

    The integration framework supports the following operators in addition to the standard LUSID filtering syntax supported operators:

    • InMapKeys: Value is a key in the defined ValueMaps, for example TypeValue InMapKeys ValidTypesMap

    • InMapValues: Value is a value in the defined ValueMaps, for example StatusValue InMapValues StatusMap

  • Result: The value to return if the condition is met; this can be any of the following:

    • A specific value

    • One of the defined ValueSources

    • One of the defined ConditionalValueSources

Always include an empty condition ("Condition": "",) as the last LogicalExpression; this ensures unexpected values are handled.

For example:

{
  "Name": "InstrumentTypeSelectorValue",
  "LogicalExpressions": [
    {
      "Condition": "AssetClassValue eq \"Equity\"",
      "Result": "Equity"
    },
    {
      "Condition": "AssetClassValue eq \"Cash\"",
      "Result": "SimpleInstrument"
    },
    {
      "Condition": "",
      "Result": "SimpleInstrument"
    }
  ]
}

ValueMaps

Allows you to specify an array of key-value pairs for mapping specific values. Each list item should contain:

• A unique reference Name ending in Map

• A dictionary of Map key-value pairs

For example:

"ValueMaps": [
  {
    "Name": "TransactionTypeMap",
    "Map": {
      "BUY": "Buy",
      "SELL": "Sell",
      "DIVIDEND": "StockDividend"
    }
  },
  {
    "Name": "FrequencyMap",
    "Map": {
      "Monthly": "1M",
      "Quarterly": "3M",
      "Semi-Annual": "6M",
      "Annual": "1Y"
    }
  }
]

Note

If the column value is not a key in the specified value map, the integration throws an error. Use a DQCheck with an InMapKeys operator to validate before applying the map, or ensure your value map includes all possible input values.

You can set up a ConditionalValueSource to check a value exists in a value map using the InMapKeys or InMapValues operators, for example:

{
  "Condition": "RawTypeValue InMapKeys TransactionTypeMap",
  "Result": "Pass"
}

DQChecks

Allows you to specify how the integration should validate data before processing in LUSID. You can define filters for how to present the result of a DQ check on a row in the logs. Each list item should contain:

• A unique reference Name

• A list of ordered LogicalExpressions to evaluate for each row of data containing:

  • Condition: A LUSID filtering syntax expression to evaluate the value source against, as with ConditionalValueSources

    Note

    If no condition matches, the integration sets the Result value to Fail.

  • Result: The value to return in the logs if the Condition is met; this can be any of the following:

    • Pass: No error recorded in the logs

    • Fail: Logged as error and row marked as failed

    • SkipWithMessage: Row is skipped and recorded in the logs as skipped

    • SkipSilently: Row is skipped but nothing is recorded in the logs

    Note

    If a check hits a SkipWithMessage or SkipSilently result, the integration stops any further DQ checking for that row of data.

• Optionally, a Message to log if a check fails

For example:

"DQChecks": [
  {
    "Name": "RequireInstrumentId",
    "Message": "Instrument ID is required",
    "LogicalExpressions": [
      {
        "Condition": "InstrumentIdValue neq \"\"",
        "Result": "Pass"
      },
      {
        "Condition": "",
        "Result": "Fail"
      }
    ]
  },
  {
  "Name": "SkipClosedPositions",
  "Message": "Skipping closed positions",
  "LogicalExpressions": [
    {
      "Condition": "QuantityValue eq \"0\" AND StatusValue eq \"Closed\"",
      "Result": "SkipWithMessage"
    },
    {
      "Condition": "",
      "Result": "Pass"
    }
  ]
}
]

Load controls

Each entity type has its own load control section defining how the entity should be processed. You only need to include sections for the entity types you specified in your control file ImportTypes list.

InstrumentsLoadControl

Required when ImportTypes includes Instruments.

For example:

"InstrumentsLoadControl": {
  "InstrumentTypeSelectorSourceName": "InstrumentTypeSelectorValue",
  "UnderlyingInstrumentHandlingSourceName": "UnderlyingHandlerValue",
  "BloombergDataRefreshSourceName": "BloombergDataRefreshValue",
  "CreateMissingInstruments": true,
  "Identifiers": [
    {
      "IdentifierType": "Isin",
      "IdentifierValueSourceName": "IsinValue",
      "IsUnique": true
    },
    {
      "IdentifierType": "Sedol",
      "IdentifierValueSourceName": "SedolValue",
      "IsUnique": false
    },
    {
      "IdentifierType": "ClientInternal",
      "IdentifierValueSourceName": "ClientIdValue",
      "IsUnique": false
    }
  ],
  "InstrumentDefControls": [
    {
      "InstrumentType": "SimpleInstrument",
      "InstrumentNameSourceName": "InstrumentNameValue",
      "DomesticCurrencySourceName": "CurrencyValue",
      "ForeignCurrencySourceName": "ForeignCcyValue",
      "SimpleInstrumentTypeSourceName": "SimpleTypeValue",
      "Properties": []
    },
    {
      "InstrumentType": "Equity",
      "InstrumentNameSourceName": "InstrumentNameValue",
      "DomesticCurrencySourceName": "CurrencyValue",
      "Properties": [
        {
          "LusidPropertyName": "Instrument/default/Sector",
          "ValueSourceName": "SectorValue"
        }
      ]
    }
  ],
  "CommonProperties": [
    {
      "LusidPropertyName": "Instrument/default/AssetClass",
      "ValueSourceName": "AssetClassValue"
    }
  ]
}

PortfoliosLoadControl

Required when ImportTypes includes Portfolios.

Note

All portfolios you wish to include in integration runs must be decorated with the following properties:

• Portfolio/rcf-config/LinkedFundCode matching the FundCode value in your source data

• Portfolio/rcf-config/IsIncluded set to true

For example:

"PortfoliosLoadControl": {
  "FundCodeSourceName": "FundCodeValue",
  "Properties": [
    {
      "LusidPropertyName": "Portfolio/default/Strategy",
      "ValueSourceName": "StrategyValue"
    },
    {
      "LusidPropertyName": "Portfolio/default/Manager",
      "ValueSourceName": "ManagerValue"
    }
  ]
}

HoldingsLoadControl

Required when ImportTypes includes Holdings.

Note

All portfolios you wish to include in holdings integration runs must be decorated with the following properties:

• Portfolio/rcf-config/LinkedFundCode matching the FundCode value in your source data

• Portfolio/rcf-config/IsIncluded set to true

• Portfolio/rcf-config/LoadPositions set to true

For example:

"HoldingsLoadControl": {
  "FundCodeSourceName": "FundCodeValue",
  "EffectiveDateSourceName": "EffectiveDateValue",
  "CurrencySourceName": "CurrencyValue",
  "CostSourceName": "CostValue",
  "QuantitySourceName": "UnitsValue",
  "TaxlotPriceSourceName": "PriceValue",
  "SubHoldingKeys": [
    {
      "LusidPropertyName": "Transaction/default/Strategy",
      "ValueSourceName": "StrategyValue"
    }
  ],
  "Properties": [
    {
      "LusidPropertyName": "Holding/default/MarketValue",
      "LusidPropertyDataType": "number",
      "ValueSourceName": "MarketValueUSDValue"
    }
  ],
  "Filter": [
  {
    "Name": "ExcludeZeroQuantity",
    "LogicalExpressions": [
      {
        "Condition": "QuantityValue eq \"0\"",
        "Result": "SkipSilently"
      },
      {
        "Condition": "",
        "Result": "Pass"
      }
    ]
  }
]
  "Aggregator": {
    "KeyValueSources": ["FundCodeValue", "InstrumentIdValue", "StrategyValue"],
    "SumColumns": ["QuantityColumn", "CostColumn"]
  }
}

TransactionsLoadControl

Required when ImportTypes includes Transactions.

Note

All portfolios you wish to include in transactions integration runs must be decorated with the following properties:

• Portfolio/rcf-config/LinkedFundCode matching the FundCode value in your source data

• Portfolio/rcf-config/IsIncluded set to true

• Portfolio/rcf-config/LoadTransactions set to true

For example:

"TransactionsLoadControl": {
  "FundCodeSourceName": "FundCodeValue",
  "TransactionIdSourceName": "TransactionIdValue",
  "TransactionTypeSourceName": "TransactionTypeValue",
  "TransactionDateSourceName": "TradeDateValue",
  "SettlementDateSourceName": "SettlementDateValue",
  "UnitsSourceName": "UnitsValue",
  "TotalConsiderationCurrencySourceName": "CurrencyValue",
  "TotalConsiderationAmountSourceName": "ConsiderationValue",
  "TransactionPriceSourceName": "PriceValue",
  "Properties": [
    {
      "LusidPropertyName": "Transaction/default/Broker",
      "ValueSourceName": "BrokerValue"
    }
  ],
  "Filter": [
  {
    "Name": "OnlyEquities",
    "LogicalExpressions": [
      {
        "Condition": "AssetClassValue eq \"Equity\"",
        "Result": "Pass"
      },
      {
        "Condition": "",
        "Result": "SkipSilently"
      }
    ]
  }
  ],
  "Aggregator": {
    "KeyValueSources": ["FundCodeValue", "InstrumentIdValue", "StrategyValue"],
    "SumColumns": ["QuantityColumn", "CostColumn"]
  }
}

QuotesLoadControl

Required when ImportTypes includes Quotes.

For example:

"QuotesLoadControl": {
  "ScopeSourceName": "QuoteScopeValue",
  "EffectiveDateSourceName": "QuoteDateValue",
  "ProviderSourceName": "ProviderValue",
  "InstrumentIdTypeSourceName": "IdTypeValue",
  "InstrumentIdSourceName": "InstrumentIdValue",
  "QuoteTypeSourceName": "QuoteTypeValue",
  "FieldSourceName": "FieldValue",
  "PriceValueSourceName": "PriceValue",
  "CurrencySourceName": "CurrencyValue",
  "Filter": []
}

RelationalDatasetsLoadControl

Required when ImportTypes includes RelationalDatasets.

For example:

"RelationalDatasetsLoadControl": {
  "RelationalDatasetDefinitionScope": "my-scope",
  "RelationalDatasetDefinitionCode": "my-dataset-code",
  "SeriesScopeSourceName": "SeriesScopeValue",
  "EntityTypeSourceName": "EntityTypeValue",
  "EntityIdentifierScopeSourceName": "EntityIdScopeValue",
  "Identifiers": [
    {
      "IdentifierType": "ClientInternal",
      "IdentifierValueSourceName": "RecordIdValue",
      "IsUnique": true
    }
  ],
  "EffectiveAtSourceName": "EffectiveDateValue",
  "ValueFieldsMap": {
    "Amount": "AmountValue",
    "Price": "PriceValue"
  },
  "MetaDataFieldsMap": {
    "Description": "DescriptionValue",
    "Category": "CategoryValue"
  },
  "Filter": []
}

Let’s imagine you want to load the following equity holdings from a CSV file:

ISIN,Name,Quantity,Price,Currency,Fund,Date
GB0002374006,Tesco PLC,1000,2.50,GBP,FUND001,2025-03-10
US0378331005,Apple Inc,500,150.00,USD,FUND001,2025-03-10

You might create the following mapping file:

{
  "CsvSeparator": "Comma",
  "ColumnSpecs": [
    { "ColumnHeader": "ISIN", "ColumnReference": "IsinColumn" },
    { "ColumnHeader": "Name", "ColumnReference": "NameColumn" },
    { "ColumnHeader": "Quantity", "ColumnReference": "QtyColumn" },
    { "ColumnHeader": "Price", "ColumnReference": "PriceColumn" },
    { "ColumnHeader": "Currency", "ColumnReference": "CcyColumn" },
    { "ColumnHeader": "Fund", "ColumnReference": "FundColumn" },
    { "ColumnHeader": "Date", "ColumnReference": "DateColumn" }
  ],
  "RowIdentificationSourceName": "RowIdValue",
  "ValueSources": [
    {
      "Name": "RowIdValue",
      "ColumnReferences": ["IsinColumn", "FundColumn"],
      "ValueConversion": "Concatenate",
      "ConcatenationSeparator": "_"
    },
    {
      "Name": "IsinValue",
      "ColumnReferences": ["IsinColumn"]
    },
    {
      "Name": "InstrumentNameValue",
      "ColumnReferences": ["NameColumn"]
    },
    {
      "Name": "UnitsValue",
      "ColumnReferences": ["QtyColumn"]
    },
    {
      "Name": "PriceValue",
      "ColumnReferences": ["PriceColumn"]
    },
    {
      "Name": "CurrencyValue",
      "ColumnReferences": ["CcyColumn"]
    },
    {
      "Name": "FundCodeValue",
      "ColumnReferences": ["FundColumn"]
    },
    {
      "Name": "DateValue",
      "ColumnReferences": ["DateColumn"]
    },
    {
      "Name": "CostValue",
      "ColumnReferences": ["PriceColumn"],
      "MultiplierValueSourceName": "UnitsValue"
    }
  ],
  "DQChecks": [
    {
      "Name": "RequireIsin",
      "Message": "ISIN is required",
      "LogicalExpressions": [
        { "Condition": "IsinValue neq \"\"", "Result": "Pass" },
        { "Condition": "", "Result": "Fail" }
      ]
    },
    {
      "Name": "RequireQuantity",
      "Message": "Quantity must be greater than zero",
      "LogicalExpressions": [
        { "Condition": "UnitsValue gt \"0\"", "Result": "Pass" },
        { "Condition": "", "Result": "Fail" }
      ]
    }
  ],
  "InstrumentsLoadControl": {
    "CreateMissingInstruments": true,
    "Identifiers": [
      {
        "IdentifierType": "Isin",
        "IdentifierValueSourceName": "IsinValue",
        "IsUnique": true
      }
    ],
    "InstrumentDefControls": [
      {
        "InstrumentType": "Equity",
        "InstrumentNameSourceName": "InstrumentNameValue",
        "DomesticCurrencySourceName": "CurrencyValue",
        "Properties": []
      }
    ],
    "CommonProperties": []
  },
  "HoldingsLoadControl": {
    "FundCodeSourceName": "FundCodeValue",
    "EffectiveDateSourceName": "DateValue",
    "CurrencySourceName": "CurrencyValue",
    "CostSourceName": "CostValue",
    "QuantitySourceName": "UnitsValue",
    "TaxlotPriceSourceName": "PriceValue",
    "SubHoldingKeys": [],
    "Properties": []
  }
}

{
  "CsvSeparator": "Pipe",
  "ColumnSpecs": [
    { "ColumnHeader": "TxnId", "ColumnReference": "TxnIdColumn" },
    { "ColumnHeader": "AssetType", "ColumnReference": "AssetTypeColumn" },
    { "ColumnHeader": "Identifier", "ColumnReference": "IdColumn" },
    { "ColumnHeader": "TxnType", "ColumnReference": "TxnTypeColumn" },
    { "ColumnHeader": "TradeDate", "ColumnReference": "TradeDateColumn" },
    { "ColumnHeader": "SettleDate", "ColumnReference": "SettleDateColumn" },
    { "ColumnHeader": "Units", "ColumnReference": "UnitsColumn" },
    { "ColumnHeader": "Price", "ColumnReference": "PriceColumn" },
    { "ColumnHeader": "CCY", "ColumnReference": "CcyColumn" },
    { "ColumnHeader": "Portfolio", "ColumnReference": "PortColumn" }
  ],
  "RowIdentificationSourceName": "TxnIdentifierValue",
  "ValueSources": [
    {
      "Name": "TxnIdentifierValue",
      "ColumnReferences": ["TxnIdColumn"]
    },
    {
      "Name": "AssetTypeValue",
      "ColumnReferences": ["AssetTypeColumn"]
    },
    {
      "Name": "IdValue",
      "ColumnReferences": ["IdColumn"]
    },
    {
      "Name": "TxnTypeRawValue",
      "ColumnReferences": ["TxnTypeColumn"]
    },
    {
      "Name": "TradeDateValue",
      "ColumnReferences": ["TradeDateColumn"]
    },
    {
      "Name": "SettleDateValue",
      "ColumnReferences": ["SettleDateColumn"]
    },
    {
      "Name": "UnitsValue",
      "ColumnReferences": ["UnitsColumn"]
    },
    {
      "Name": "PriceValue",
      "ColumnReferences": ["PriceColumn"]
    },
    {
      "Name": "CcyValue",
      "ColumnReferences": ["CcyColumn"]
    },
    {
      "Name": "PortValue",
      "ColumnReferences": ["PortColumn"]
    },
    {
      "Name": "StandardTxnTypeValue",
      "ColumnReferences": ["TxnTypeColumn"],
      "ValueMapName": "TxnTypeMap"
    },
    {
      "Name": "TotalConsiderationValue",
      "ColumnReferences": ["PriceColumn"],
      "MultiplierValueSourceName": "UnitsValue"
    }
  ],
  "ConditionalValueSources": [
    {
      "Name": "InstrumentTypeSelectorValue",
      "LogicalExpressions": [
        {
          "Condition": "AssetTypeValue eq \"EQ\"",
          "Result": "Equity"
        },
        {
          "Condition": "AssetTypeValue eq \"CASH\"",
          "Result": "SimpleInstrument"
        },
        {
          "Condition": "",
          "Result": "SimpleInstrument"
        }
      ]
    }
  ],
  "ValueMaps": [
    {
      "Name": "TxnTypeMap",
      "Map": {
        "B": "Buy",
        "S": "Sell",
        "DIV": "StockDividend"
      }
    }
  ],
  "DQChecks": [
    {
      "Name": "ValidTxnType",
      "Message": "Transaction type must be valid",
      "LogicalExpressions": [
        { "Condition": "TxnTypeRawValue InMapKeys TxnTypeMap", "Result": "Pass" },
        { "Condition": "", "Result": "Fail" }
      ]
    },
    {
      "Name": "RequirePrice",
      "Message": "Price must be greater than zero",
      "LogicalExpressions": [
        { "Condition": "PriceValue gt \"0\"", "Result": "Pass" },
        { "Condition": "", "Result": "Fail" }
      ]
    }
  ],
  "InstrumentsLoadControl": {
    "InstrumentTypeSelectorSourceName": "InstrumentTypeSelectorValue",
    "CreateMissingInstruments": true,
    "Identifiers": [
      {
        "IdentifierType": "ClientInternal",
        "IdentifierValueSourceName": "IdValue",
        "IsUnique": true
      }
    ],
    "InstrumentDefControls": [
      {
        "InstrumentType": "SimpleInstrument",
        "InstrumentNameSourceName": "IdValue",
        "DomesticCurrencySourceName": "CcyValue",
        "SimpleInstrumentTypeSourceName": "AssetTypeValue",
        "Properties": []
      },
      {
        "InstrumentType": "Equity",
        "InstrumentNameSourceName": "IdValue",
        "DomesticCurrencySourceName": "CcyValue",
        "Properties": []
      }
    ],
    "CommonProperties": []
  },
  "TransactionsLoadControl": {
    "FundCodeSourceName": "PortValue",
    "TransactionIdSourceName": "TxnIdentifierValue",
    "TransactionTypeSourceName": "StandardTxnTypeValue",
    "TransactionDateSourceName": "TradeDateValue",
    "SettlementDateSourceName": "SettleDateValue",
    "UnitsSourceName": "UnitsValue",
    "TotalConsiderationCurrencySourceName": "CcyValue",
    "TotalConsiderationAmountSourceName": "TotalConsiderationValue",
    "TransactionPriceSourceName": "PriceValue",
    "Properties": []
  }
}

• Check the order of LogicalExpressions - first match wins

• Verify ValueSource names are spelled correctly (case-sensitive)

• Check for empty string vs missing value handling

• Verify at least one Identifier has IsUnique: true

• Check identifier values are being extracted correctly

• Confirm instrument exists in LUSID with that identifier

• Cannot mix AND/OR in single condition

• Verify ValueSource names exist and are spelled correctly

• Check quotes around absolute values in conditions

• Verify property key format is correct (Domain/Scope/Code)

• Check LusidPropertyDataType for numeric properties (use number)

• For date properties, use date and provide DateFormats array

• Confirm ValueSource returns non-empty value

• Validate value is in map keys before applying with DQChecks

• Verify key spelling matches exactly (case-sensitive)

• Ensure all possible source values are mapped