"Object reference not set to an instance of an object." error when uploading metadata with missing dimensions
When uploading ref. metadata with missing dimension column(s), instead of getting the expected error "The given key 'DIM_XXXX' was not present in the dictionary", an error "Object reference not set to an instance of an object." is received in QA.
example files
- data structures: SPC-DF_CIVIL_REGISTRATION-1.0-all.xml
- MSD structures: SPC-MSD_COM_GENERAL-1.0-all.xml
- data: SPC-DF_CIVIL_REGISTRATION-1.0-data.csv
- metadata with missing dimension columns: DF_CIVIL_REGISTRATION_-Metadataset__1.csv
original description
The given key 'FREQ' was not present in the dictionary error when uploading metadata (in some cases)
Having recently upgraded our STAGING environment with the "blueberry" version of the backend, the content attached gives the following error message when uploading the metadata file. Loading the same content in our PROD environment running the "almond" version of .STAT backend works fine. This error occurs for some dataflows when uploading reference metadata but not in all cases.
SPC-DF_CIVIL_REGISTRATION-1.0-all.xml
SPC-MSD_COM_GENERAL-1.0-all.xml
SPC-DF_CIVIL_REGISTRATION-1.0-data.csv
original incorrect metadata (missing quotes): DF_CIVIL_REGISTRATION_-_Metadataset.csv~~ corrected: DF_CIVIL_REGISTRATION_-Metadataset__1.csv
Analysis: This result is expected because the dimension column for ref. metadata are required since they are used to define the attachment level especially in DELETE operations where omitted dimensions columns serve for wildcard deletions.
However, since in qa we currently have a different error "Object reference not set to an instance of an object"**, this needs to be corrected. Full logs: response_1666948343827.json