Issue Summary

When importing Assets Objects via CSV, if you have a string in the CSV such as \n or backslash n, it is treated as a newline. It also causes the import to take much longer than it should.

Steps to Reproduce

1. Create a CSV Import for an Assets Schema
   • The Import Mapping & such do not matter, aside from being correct for Text Attributes.
2. Upload a CSV containing a field that has \n (backslash n) in it
3. Initiate the Import

Expected Results

The \n is interpreted as it is written, so the Attribute receives the correct value, as shown in the CSV. The Import should take the normal amount of time.

Actual Results

The \n is interpreted as a newline. This is evident from the UI showing it as such.
The Import also takes substantially longer than normal. In my case, 10 minutes for a single record in a brand new, otherwise empty Schema.

Workaround

None at this time. If one is found, it will be added here.