We're updating the issue view to help you get more done. 

Data importer doesn't evaluate dynamically set types

Description

Type for an imported record is currently evaluated using the last-found rule, ignoring dynamic options such as skipIfExpression. This means that import mappings that use logic to set type don't work; the type is generally whatever the last type-targeting rule declares.

We need to allow dynamic setting of type.

We also need to ensure that the dynamic evaluation is performed early in the import cycle such that the evaluate type can be used when testing restrictToTypes and existing record policy settings. This will require significant refactoring of the importer which may not happen until v1.8.

Environment

None

Assignee

User known

Reporter

User known

Labels

None

Components

Fix versions

Affects versions

Priority

Major
Configure