Skip to main content

Troubleshooting Guide: Resolving Null MIC (Market Identifier Code) Data Validation Errors

Distributor troubleshooting for null or missing MIC (Market Identifier Code) validation errors in Encompass imports: check ETL/batch mappings, vendor API data and merge updates. Requires v26.01+.

B
Written by Bailey Naas-Thornton

Minimum Version Required: 26.01

Pre-Conditions

  • Must have administrative or developer access to the ETL transform tools, batch import pipelines, or database management systems.

  • Must have permissions to view and edit field mappings and upstream business validation logic.

  • Requires access to upstream vendor API logs and response payloads (if applicable).

Steps

  1. Identify the Failure Point: Determine exactly where the missing field error occurred to isolate the root cause.

  2. Verify ETL and Batch Import Mappings: Check the ETL transform or batch import pipeline to ensure the field mapping for the MIC did not fail completely.

  3. Inspect Upstream API Responses: If data is sourced externally, review the upstream vendor API response structure to verify if it omitted the mandatory MIC field.

  4. Review Business Validation Logic: Check your upstream business validation logic to ensure it is not strictly treating an optional database field as a required field.

  5. Audit Database Updates: Investigate recent database activities to determine if a null value was introduced via an unintended database overwrite or merge update process.

  6. Contact Support: If the issue persists after attempting the above steps, please contact support for further assistance. To ensure efficient troubleshooting, gather and provide the following specific information:

    • Exact error messages or codes encountered.

    • Screenshots or video recordings of the issue.

    • Log files (specifically ETL execution logs, API response payloads, or database transaction logs).

    • The exact steps taken by the customer that led to the issue.

    • The date and time the issue was first observed and any recurrence.

    • Any changes made to the system before the issue appeared (e.g., recent merges, ETL updates, or API changes).

Fields And Definitions

  • MIC (Market Identifier Code): A required field in the source record that is triggering the missing field validation error.

  • ETL Transform / Batch Import Pipeline: The data integration processes where field mapping failures can completely omit required data.

  • Upstream Vendor API: An external data source that may omit the mandatory MIC field from its response structure.

  • Null Value: An empty or missing data state that can be unintentionally introduced via database overwrites or merge update processes.

Best Practices

  • Implement Pre-Import Validation: Always validate source files and API payloads for required fields like the MIC before initiating an ETL transform or batch import.

  • Audit Merge Processes: Regularly review database merge and update routines in a test environment to ensure they do not introduce unintended null values into mandatory fields.

  • Align Business Logic: Periodically audit upstream business validation logic to guarantee it accurately reflects the current database schema, ensuring optional fields are not mistakenly enforced as required.

  • Monitor API Changes: Maintain communication with upstream vendors to anticipate changes in their API response structures that might omit critical data.

Did this answer your question?