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

"Type" setting is not acting as default/fallback when "type_id" is not set from data

Description

According to the data importer documentation, the general setting for "type" is supposed to act as the default setting for cases where there is no source value for the mapping to ca_objects.type_id.

In other words, the mapping to type_id is privileged over the general setting, but in cases where type_id cannot be set from source data, the type setting is supposed to be the default.

However, on the latest code it appears that if the type_id is not set from data, the importer just chokes on it and gives you the "no type specified" error, rather than fall back to generic type set in Settings.

Environment

None

Assignee

User known

Reporter

Jonathan Byerley

Labels

Priority

Blocker
Configure