Overview
Data overrides allow you to temporarily correct position data while you permanently resolve the underlying issues in your positions file. Because overrides alter data directly within the system, careful management is essential for maintaining accurate results.
This troubleshooting guide explains how data overrides operate, why override overpopulation occurs, how to perform bulk edits using a CSV file, and best practices for ongoing override management.
What This Means
Using overrides as a permanent solution can lead to an excess of overrides, making internal audits difficult because users can easily lose track of them. Additionally, having too many overrides can alter the input file so much that it is hard to recognise. This article lists methods and best practices to mitigate this.
Why Overpopulation Happens
Override overpopulation typically occurs when team members treat overrides as permanent fixes rather than temporary measures. Without regular reviews, set expiry dates, or documented reasons, overrides accumulate over time. This accumulation degrades data transparency and makes it challenging to track affected assets or instruments during audits.
Best Practices for Override Management
Implement the following best practices to prevent override accumulation and maintain a clean audit trail.
Creating an Expiry Date for each override ensures that the overrides are used as a temporary measure. And if the data issue is not resolved, the user will be prompted to investigate when the expiry date is reached.
Filling in the Notes section of overrides is highly useful because it allows you to track your audit trail as well as affected assets/instruments. The reason for setting up the override should always be entered in the Notes section. Furthermore, filling in this section will allow you to filter overrides on the main override page.
Using the Last NAV Date shows the latest NAV date when the override was applied and can also be used to keep track of overrides and prevent them from piling up. Filtering by Last NAV Date is also possible and makes it easy to get a quick overview of which overrides should potentially be deleted, as they might not have been used for a period of time.
Monthly Reviews of all your overrides is highly recommended can minimize the chances of accumulating them unnecessarily. The above recommendations can be used as guidelines for action points during a review.
Bulk Editing Overrides
In addition to manually adding and removing overrides within the UI, users can also edit them in bulk via a CSV file.
Navigate to Admin and settings (Gear icon) > Setup > Data Overrides.
Select the appropriate filter view (for example, Active or Deactivated) to display the overrides you want to edit.
Click Download in the upper right corner to export the existing overrides as a CSV file.
Open the CSV file and make the necessary edits:
To create new overrides, leave the BundleId column blank. (Populating BundleId updates an existing override instead of creating a new one).
To deactivate an existing override, change the IsActive column value to "false." (Setting this column to "true" keeps the override active).
Columns with dates need to be reformatted to yyyy-mm-dd format. This can be done by highlighting the entire column, right-clicking, selecting Format Cells, and choosing Date from the Number tab.
Save the amended CSV file.
Click Upload in the upper-right corner to upload the amended file to the system.