LUSID system settings available to override

Set to True to reject any transaction in a batch that fails to resolve to an instrument mastered in LUSID. Note True also causes a manual holdings adjustment made using either the LUSID SetHoldings or AdjustHoldings APIs to fail in the same circumstances. Rejected transactions are listed in the failed section of the API response.

When ValidateInstruments is False (the default), an unresolved transaction is upserted but mapped to the unknown instrument. You should take steps to manually resolve these transactions.

Set to True to reject any transaction in a batch that fails to resolve to a known transaction type. Rejected transactions are listed in the failed section of the API response.

When ValidateTransactionTypes is False (the default), an unresolved transaction is upserted but omitted when LUSID generates holdings. You should take steps to manually resolve these transactions.

Set to True to add the TradeToPortfolioRate system property to every transaction in a batch with an exchange rate from the transaction to the portfolio currency sourced using the recipe identified by the TradeToPortfolioRateRecipe system setting (below).

Note the system property is applied at the moment a transaction is upserted; it is not a live quote and therefore not subsequently updated. If a transaction has the TradeToPortfolioRate system property added already, the latter is preferred.

When SetTradeToPortfolioRate is False (the default), you must explicitly add the TradeToPortfolioRate system property to the properties collection of a foreign currency transaction in order to maintain the cost basis of a portfolio.