Skip to main content

Data Loader - AFM data not picking update data descrepancies

Feature Request

AFM data files were used for loading to Fundanalyser, FUM and transaction files were manipulated to include the following.

Data file manipulated to include the following discrepancies.

  • negative net asset values

  • special characters

  • incorrect month

  • blank cells

  • missing investor resident cells

  • duplicate ISIN codes

  • blank wrapper

  • insertion of blank columns

  • adding additional rows within within the data

Noticed the data completion checks did not pickup any of the data discrepancies, as the file loaded without errors. After discussion with Tek it appears completeness validation did not pickup any of the data errors below and only picked up validation on threshold being over £100k only. The validation checks need to be in place for FUM and Transaction data files to ensure users are prompted to check their data files for consistency and accuracy. Fundipedia need to use ECHOweb to understand the error messages which validates rows line by line.

Status: Completed2 comments

Log in to comment and vote

Comments2

  • Tek Chung

    Team•

    Sep 17, 2024

    Regarding duplicate ISIN codes:

    We’re seeing a lot of duplicates in the July files. Do we expect these, or do these get rejected by Echo currently?

  • Tek Chung

    Team•

    Sep 17, 2024

    Summary of changes needed (mostly configuration, not development):

    negative net asset values – configuration change - we will add a range check (no development needed)

    1. special characters – non-issue - £/$ signs would already be flagged as errors if imported into a decimal field.

    2. incorrect month -

    3. blank cells – configuration change – we will add a missing value check

    4. missing investor resident cells – configuration change – we will add a missing value check

    5. duplicate ISIN codes – configuration change – using import identifiers. We will need to consider the error messaging here.

    6. blank wrapper - configuration change – we will add a missing value check

    7. insertion of blank columns – development likely needed - as discussed, this is currently incompatible with the current way of mapping data using column numbers. We can consider additional development.

    8. adding additional rows within the data file. – non-issue – blank rows will be ignored by the system.