- Getting Started
- Using Hevo
-
Pipelines
- Familiarizing with the Pipelines UI
- Pipeline Concepts
- Working with Pipelines
- Transformations
-
Schema Mapper
- Using Schema Mapper
- Mapping Statuses
- Mapping a Source Event Type with a Destination Table
- Mapping a Source Event Type Field with a Destination Table Column
- Resizing String Columns in the Destination
- Fixing Unmapped Fields
- Resolving Incompatible Schema Mappings
- Bulk Actions in Schema Mapper
- Auto Mapping Event Types
- Creating File Partitions for S3 Destination through Schema Mapper
- Schema Mapper Compatibility Table
- Sources
- Destinations
- Transform
- Activate
- Concepts and Reference
- Account Management
- About Hevo
- FAQs
-
Release Notes
- Release Version 1.57 (22-Feb-2021)
- Release Version 1.56 (09-Feb-2021)
- Release Version 1.55 (25-Jan-2021)
- Release Version 1.54 (12-Jan-2021)
- Release Version 1.53 (22-Dec-2020)
- Release Version 1.52 (03-Dec-2020)
- Release Version 1.51 (10-Nov-2020)
- Release Version 1.50 (19-Oct-2020)
- Release Version 1.49 (28-Sep-2020)
- Release Version 1.48 (01-Sep-2020)
- Release Version 1.47 (06-Aug-2020)
- Release Version 1.46 (21-Jul-2020)
- Release Version 1.45 (02-Jul-2020)
- Release Version 1.44 (11-Jun-2020)
- Release Version 1.43 (15-May-2020)
- Release Version 1.42 (30-Apr-2020)
- Release Version 1.41 (Apr-2020)
- Release Version 1.40 (Mar-2020)
- Release Version 1.39 (Feb-2020)
- Release Version 1.38 (Jan-2020)
Fixing Unmapped Fields
Hevo displays a warning icon next to any Event Type that has the status of Mapped but contains one or more unmapped fields. During the Pipeline run, the Events related to these fields are marked as Failed until you map the fields to appropriate Destination table fields or skip them.
Follow these steps to fix an unmapped field:
- In the Schema Mapper Overview page, click on the Event Type having the warning icon to access the Mapping Summary page.
- Click Edit Mapping.
- For the unmapped Source field (marked with an orange warning icon), do one of the following:
- Map the source field with a Destination table column. Read more about how to do that here.
- Skip the field. By deselecting the check box adjacent to the Source field name, you can skip mapping it. If skipped, the data for the field is not replicated to the Destination table.
Note: Hevo does not retain the data for skipped fields anywhere.
- Click APPLY CHANGES.
See Also
Schema Mapper Compatibility Table
Last updated on 09 Nov 2020
Was this page helpful?
Thank you for helping improve Hevo's documentation. If you need help or have any questions, please consider contacting support.