Overview
In FundApps, users can create, edit, and manage multiple property overrides efficiently using a CSV file. This workflow lets you perform bulk updates to Data Overrides without manually modifying each entry in the platform interface.
By exporting your existing overrides, you can make large-scale changes to properties. This article covers the export process, how to format your CSV file for bundled properties, and the critical requirements for a successful re-import.
What This Means
The CSV override workflow provides a scalable way to maintain data integrity. It supports "bundled" overrides, where multiple properties are grouped into a single row and linked by a unique BundleId. This ensures that complex data corrections involving several properties remain organised and are processed in a single instance.
How to Edit Existing Overrides
Navigate to Admin and settings > Setup > Data Overrides.
Select Download to export your current overrides as a CSV file.
Open the file and edit the necessary columns. For example, to deactivate an override, change the IsEnabled column from "TRUE" to "FALSE."
Ensure all dates use the YYYY-MM-DD format for columns such as ActiveFrom, ActiveTo, and LastNavDate.
Save the amended file before re-importing it into FundApps.
How to Create Bundled Overrides
Create a new row in the CSV file.
Tip: It may be easier to create your first bundled override in the FundApps UI first, then export it to use as a template.
Leave the BundleId column blank for new entries. FundApps will generate a unique identifier upon import.
If the BundleId is empty, we treat it as a new entry and create a new group.
If the BundleId matches an existing record in FundApps, that bundle will be updated.
FundApps matches all defined BundleIds in the CSV with ones already present. This determines how we update the Data Overrides.
Identify the properties in the TargetPropertyX columns. Each property within the bundle needs an assigned numerical value, starting at zero (e.g., TargetProperty0, TargetProperty1).
The TargetPropertyX columns define which property will be overridden.
If TargetPropertyX is empty, it'll be treated as a new entry, and a new override will be created. If it already exists, FundApps will match it to an existing record.
Enter the TargetSource (the overridden value) and the TargetCondition if the override should only apply under specific circumstances.
Additional Notes
BundleId Management: Do not change the BundleId for existing overrides. This is the unique identifier used to match your CSV rows to records already in the system.
System Validation: Do not attempt to edit overrides created by FundApps. These cannot be deleted or edited via CSV, and attempting to do so will cause validation failures.
Empty Environments: If you are copying overrides from one environment to an empty one, ensure the BundleId and TargetPropertyIDX columns are blank.