Asset Import Failure - Error: At least one value must be set. [Object (Label: xxxxxxxxxxx, Id: Unknown)].
Platform Notice: Cloud Only - This article only applies to Atlassian apps on the cloud platform.
Summary
When importing objects in Assets, the import fails with the error: "At least one value must be set." [Object (Label: xxxxxxxxxxx, Id: Unknown)].
2 error(s) found in source data
Error: At least one value must be set. [Object (Label: xxxxxxxxxxx, Id: Unknown)].
Error: At least one value must be set. [Object (Label: xxxxxxxxxxx, Id: Unknown)].Cause
The import can fail for either of these reasons:
The import file does not contain a value for an attribute with a minimum cardinality of 1 or higher.
The value in the import file does not match one of the values available for a mandatory Select (drop-down) attribute.
These causes require different checks: review the attribute's minimum cardinality for the first case, and review the imported value against the mandatory Select (drop-down) attribute values for the second case.
Solution
For an attribute with no value in the import file, set the attribute's minimum cardinality to
0, or add a value for that attribute in the import file.For a mandatory Select (drop-down) attribute, make sure the value in the import file matches the attribute's Select (drop-down) value.
Use the error details to identify the check: the message “At least one value must be set” indicates that a required value is missing or that the imported value does not match a mandatory Select (drop-down) value. Apply the corresponding correction above before running the import again.
To change an attribute's cardinality:
Select Assets in the top navigation bar.
Select Object schemas.
Select the relevant object schema.
Select the relevant object type.
Select Attributes.
Select the gear icon next to the attribute, then select Configure in the dropdown.
Under the Cardinality tab, enter the maximum or minimum number of values that can be added to the attribute.
Set the minimum cardinality to 0 when the import file intentionally does not provide a value for that attribute.
Was this helpful?