Data Overrides - Examples and Validation Rules

Examples for Data Overrides - Common Cases

Please note the below are recommendations. Please keep in mind that it is the sole responsibility of the client to ensure the accuracy of the data sent to the service and data overrides.

Target Property 
Property requiring change 

Recommended Condition Property 

Property Class

TotalSharesOutstanding

IssuerId

Issuer 

TotalVotesOutstanding

IssuerId

Issuer 

TotalVotingRightsInTreasury

IssuerId

Issuer 

TotalSharesInTreasury

IssuerId

Issuer 

Delta

InstrumentId *

Instrument 

ParValue

InstrumentId

Instrument 

Price

InstrumentId

Instrument 

AssetClass

InstrumentId

Instrument 

ClassSharesOutstanding

InstrumentId

Instrument 

TotalIssuedNominalCapital

InstrumentId

Instrument 

VotesPerShare

InstrumentId

Instrument 

MarketValue

AssetId

Asset

SFT-Type

AssetId

Asset

Quantity

AssetId

Asset

*Why not ISIN? ISIN would work as well as it is an instrument property, but ISINs can change over time (for instance with a spac merger). InstrumentId is a constant variable. 

For more info on creating Data Overrides please see Creating Data Overrides. 


Validation Rules for Data Overrides  

We have enforced validation rules on data overrides to ensure data consistency. 

Here are some validations to be aware of: 

Condition & Target Property

The "Condition Property" type must match the "Target Property". For example, you can only override TotalSharesOutstanding with IssuerId/IssuerName. If you try to override TotalSharesOutstanding with InstrumentId or ISIN, that would fail validation since one is an Issuer property and the other is an Instrument property. This makes sense as TotalSharesOutstanding will be identical across all share classes held in a specific issuer. 

Target Property & Target Source

Our data overrides are advanced enough to allow you to override the value from another property. For example, if IssuerId=X, you can override TotalSharesOutstanding with a value in TotalVotingRights. Just like earlier scenarios, the property classifications need to match. 

Case Sensitive

If you are creating data overrides in the UI, it will have a drop-down menu once you start typing the property name to make it easy to use. If you are, however, bulk editing/creating data overrides using the CSV import, the Property names must be in the correct format. For example, IssuerId instead of IssuerID, or issuerid. 

Edge Cases

AssetId

When creating a data override for an asset id, it has to be the asset id provided in the positions file.

For example, if 5 shares of Google Class A has AssetId= 545 and it belongs to Fund A with PortfolioId=FdA -> In the UI, the AssetId will be displayed as FdA_545.

Correct data override: AssetId=545

Incorrect data override: AssetId=FdA_545

Inheritable properties

Properties that are inheritable (IsInheritable = true) are only applicable to the most granular underlying asset classes such as Equity, Preferred Equity, and Units as per the data spec. If you are trying to override an inheritable property such as ClassSharesOutstanding, TotalSharesOutstanding, IssuerName, TotalVotingRights, VotesPerShare etc you must override the data point on the underlying instrument (asset class for which the property is valid) as the value will get copied up from this instrument. For additional information on inheritable properties please read this article.

Was this article helpful?
1 out of 1 found this helpful
Share article