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.

Performing native import to assets will cause the "Not Mapped" value will be carried over to Assets , and new objects will have this value. As for existing object , currently we do have the option as per this documentation : Bring Data Manager objects into a schema in Assets

Steps to Reproduce

1. Make sure objects in Data manager have (not Mapped) value
2. Then , create a filter.
3. In Assets , create import from Data Manager.
4. Execute the import.

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 for new objects ;
• Offer to the user the possibility to ignore the NotMapped when importing from Data Manager to Assets for the new objects

Actual Results

If we try to import this directly to Assets (through native feature), this what will happen:

• If updating attributes that require one specific format (such as IP address), an error is shown;
• New objects will be imported with Not Mapped strings in the attributes.

Workaround

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