Issue Summary

When using the /mapping endpoint to create or update the schema and mapping during the flow of importing data into Assets, attempting to update an existing object type with an already defined label attribute may lead to the label attribute being changed if one is not specified in the payload.

This is reproducible on Data Center: (yes) / (no)

Steps to Reproduce

1. In Assets create an object type called "Laptop" with an attribute called "Name" and set that attribute to be the label.
2. Using the external imports APIs submit a schema mapping payload where the "Laptop" object type is referenced and adds a new text attribute called "Version". Make sure that none of the attributes are specified as the label attribute

Expected Results

A new attribute called "Version" is created on the "Laptop" object type with "Name" still being the label attribute

Actual Results

A new attribute called "Version" is created on the "Laptop" object type with "Version" now being the label attribute

Workaround

Always include all the attributes that should belong on an object type in the payload