-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
REST API - Attribute option creation -> no ID returned #8810
Comments
Same results for SOAP API, returning option id is better than returning string value. |
@radosdesign Hi, thanks for your issue, internal ticket was created MAGETWO-70363 |
@radosdesign, thank you for your report. |
I am taking this issue. Please assign this ticket to me. |
Any chance on fixing this on 2.2.6? |
Hi @engcom-backlog-nazar. Thank you for working on this issue.
|
Hi @radosdesign thank you for you report, I'm closing this one, because we have anothe here -> #18392, and have a Created PR. |
Preconditions
Steps to reproduce
with following Body:
Expected result
One of following:
The reason is that external systems will usually remember the ID so that it can be later referenced (for example when the external system needs to delete that option later).
Actual result
true
The text was updated successfully, but these errors were encountered: