Issue Summary

If a multivalue attribute is set as an identifier in the import mapping, errors are thrown during the import run as it is not supported. This was supported in a monolithic arch.

Steps to Reproduce

1. Create an import configuration and configure a multi-value attribute as an identifier. 
2. Perform an Assets import.
3. You will encounter UI errors in the import history saying xx error(s) found in source data.

Expected Results

When a multivalue attribute is set as an identifier in the import mapping, there shouldn't be any errors in the import history.

Actual Results

It throws xx error(s) found in source data in the import history.

Workaround

Functionality remains works. The fix is coming soon.