- Introduction & common operations
- Pipeline jobs
- Introduction to Schema Mapper
- How to Use Schema Mapper
- How to Map a Source Event Type with a Destination Table Using Schema Mapper
- How to Map a Source Event Type Field with a Destination Table Column
- How to Fix Unmapped Fields for an Event Type
- How to Resolve Incompatible Schema Mappings
- Bulk Actions in Schema Mapper
- How to Resize String Columns in the Destination
- Auto Mapping Event Types
- Creating File Partitions for S3 Destination through Schema Mapper
- Mapping Statuses
- Schema Mapper Compatibility Table
- Advanced concepts
- Batching & throughput
- Cloud Applications
- File Storage
- Marketing & Email
- Sdk & Streaming
- Data Warehouses
- File storage
Model And Workflows
- Personal settings
- Team settings
- Release Version 1.38 (Jan-2020)
- Release Version 1.39 (Feb-2020)
- Release Version 1.40 (Mar-2020)
- Release Version 1.41 (Apr-2020)
- Release Version 1.42 (30-Apr-2020)
- Release Version 1.43 (15-May-2020)
- Release Version 1.44 (11-Jun-2020)
- Release Version 1.45 (02-Jul-2020)
- Release Version 1.46 (21-Jul-2020)
Modifying Schema Mapping for Auto Mapped Event Types
To delete or modify the schema mapping for an Event Type:
- In the Schema Mapper, click on the required Event Type.
- Disable Auto Mapping for it.
- Click on EDIT MAPPING, modify the mapping as required, and click APPLY CHANGES. Alternatively, click DELETE MAPPING to remove the schema mapping for the complete Event Type.
If you enable Auto Mapping again, all fields except the ones you modified are again automatically mapped. If you had deleted the mapping, it is generated again. For example, in the image below, the field emp_no is unmapped manually and remains ignored even after re-enabling Auto Mapping.
Was this page helpful?
Thank you for helping improve Hevo's documentation. If you need help or have any questions, please consider contacting support.