This is due to the FieldMap dictionary using the content field identifier as the key instead of the search field identifier. This seems backwards to me as we should guarantee uniqueness of custom mappings for the destination opposed to the source.
See FieldProcessorSettings.SetFieldMap (line 60) for the issue.
This is due to the FieldMap dictionary using the content field identifier as the key instead of the search field identifier. This seems backwards to me as we should guarantee uniqueness of custom mappings for the destination opposed to the source.
See FieldProcessorSettings.SetFieldMap (line 60) for the issue.