Issue Summary

When exporting from Data Manager, values that are not mapped for a data source exports as "(NotMapped)". This can happen, for example, when merging data from multiple sources and only one of them have one specific attribute.

Steps to Reproduce

Expected Results

Native import from Data manager to Assets should better handle this situations. Alternatives are:

• Offer to the user the possibility to import this as empty cells;
• Offer to the user the possibility to ignore the NotMapped when importing from Data Manager to Assets

Actual Results

If we try to import this directly to Assets (through native feature), two things can happen:

• If updating attributes that require one specific format (such as IP address), an error is shown;
• If updating other attributes, there is a risk of (NotMapped) replace a valid existing values on objects.

Workaround

The only workaround is to export data to CSV, adjust the values and manually import this to Assets, what means you cannot use native import in this situation.