How does the manifest help you understand your aggregation results?
The manifest in LUSID is a verbose object that can be painted onto an aggregation request.
The manifest contains details of how the configuration recipe or recipes that instructed the aggregation request were implemented within the aggregation logic at runtime. This is helpful in showing how the logic was applied; it details the instruments within the request as well as the market data key rules and quotes used for each instrument, and the values within the quotes.
To activate the manifest, simply set the manifest level of detail to be ‘Full’ within the configuration recipe market context options. If not specified, the level of detail defaults to ‘None’. The manifest will then be accessible within the request response body at the root level.
This feature is computationally quite intensive and clients may wish to activate it for specific purposes (e.g. debugging).
The structure of the manifest output is such that it will shortly be possible to tweak it and upsert it back into LUSID as a corrected or new set of transactions - particularly useful for reconciliation, trade amendment and scenario or what-if based modelling.