Assets for JSM: Importing Objects that use a Number in a Text Attribute to lookup an Object via AQL will fail.

Issue Summary

When importing Objects to Assets for JSM, if a Number is used from a Text Attribute to lookup an Object Attribute's value, it will fail to do so.

Steps to Reproduce

1. Create an Object Type in an Object Schema: Employees, for example.
2. Create an Object Attribute on Employees Object Type of Manager that is of other Employees.
3. Create a Text Attribute on Employees named Employee ID and make it the Label for Employees.
4. Create an Object with the following information in Employees (Manager left blank):

   Employee ID	Employee Name
   5001	Jane Doe

5. Import another Object with the following information via CSV:

   Employee ID	Manager	Employee Name
   AB02	5001	John Doe

   And the following AQL to lookup the Employee Object to set as Manager:

   Label = ${Manager}
   

Expected Results

The John Doe Object should have the Jane Doe Object set as their Manager.

Actual Results

The John Doe Object will not have a Manager Value set.

Workaround

Currently there is no known workaround for this behavior aside from not using Numbers in this way.
A workaround will be added here when available.