Problem adding attribute options that start with a number via REST Api

[johnhird]

Steps to reproduce

1. Via REST API make a POST request to: /V1/products/attributes/{attributeCode}/options
2. send up new data with label and value that begins with a number e.g. "123 test"

Expected result

1. new attribute option should be added the same as when label and value begin with a letter.
2. API result is "StatusCode: OK, Content-Type: application/json; charset=utf-8, Content-Length: 4)"

Actual result

1. response from API call is: {"message":"Cannot save attribute %1","parameters":["size"]}

This only happens when the attribute options starts with a number.

[jakobfdev]

+1: I can confirm.
Below the 'Cannot save attribute %s' I get the Exception

[Zend_Db_Statement_Exception]) SQLSTATE[23000]: Integrity constraint violation: 1452 Cannot add or update a child row: a foreign key constraint fails (db_name.eav_attribute_option_value, CONSTRAINTEAV_ATTR_OPT_VAL_OPT_ID_EAV_ATTR_OPT_OPT_IDFOREIGN KEY (option_id) REFERENCESeav_attribute_option(option_id) ON DELETE ), query was: INSERT INTOeav_attribute_option_value(option_id,store_id,value) VALUES (?, ?, ?)))

from the Magento\Eav\Model\ResourceModel\Entity\Attribute class.

This problem is not restricted to API calls!

I was using the function add from the Magento\Eav\Model\Entity\Attribute\OptionManagement class.
Meanwhile no problems using value-strings starting with alpha characters.

[SerhiyShkolyarenko]

@johnhird @jboka thank you for reporting!
We reproduced the issue and created internal MAGETWO-58338.

[SerhiyShkolyarenko]

Fix of MAGETWO-58338 is delivered to develop branch. Closing the issue.

[jakobfdev]

Hi, as far as can see the issue still exists in 2.1.2
How do we know, when the fix is delivered to the composer packages?

[SerhiyShkolyarenko]

In 2.2.0 release, IMHO.

[worldpac]

Was there a fix here? I see an update to a unit test in MAGETWO-58338, but not to the code that would fix the problem.

[SerhiyShkolyarenko]

@worldpac fix was delivered to develop branch in commits 4f6281d and 21d58ef.

[orozcodiaz]

2.1.6 still experiencing