Order of Assets attribute values in request form(portal) is not consistent.

Issue Summary

If multiple attributes are configured to be displayed for an asset field in a request form(portal), the sequence in which those attribute values are displayed in portal is not consistent. The attributes to display can be configured in section Allow search filtering by these attributes of the Asset field configuration.

Attached a GIF file to have a better understanding of the problem

Check the below example:

• There are 3 asset fields that are supposed to display 2 attributes - Name, Brand
• The field names:
  • Application 1(Document)
  • Application 2(Headphone)
  • Application 3(Printers
• Attribute names and values:
  Name: Doc 1, Headphone 1, Printer 1
  Brand: Neo, JBL, Canon
• Once the values are selected for these fields in portal, it will look like below:
  Application 1(Document): Neo Doc 1
  Application 2(Headphone): Headphone 1 JBL
  Application 3(Printers): Printer 1 Canon

Steps to Reproduce

1. Create an object schema and 3 object types in it.
2. Add an attribute for each of those object types. Let's call it Brand
3. Create 3 Asset fields and map one object type for each of those fields. So it will be like Field 1 ---> Object type 1, Field 2 ---> Object type 2, Field 2 ---> Object type 3
4. Select Name and Brand in this order in the section Allow search filtering by these attributes for the Asset field configurations
5. Add the asset fields in request form screens and open the form for request creation
6. Select the values in those asset fields. No need to create a request.
7. The asset fields will display values fine but not in the sequence as selected in Step 4

Expected Results

The attribute values should be displayed as set in the section Allow search filtering by these attributes for the Asset field configurations

Actual Results

The sequence in which attribute values is inconsistent

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available