-
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
Magento 2 REST API / UPDATE CUSTOMER (The %fieldName value is invalid. Set the correct value and try again. / fieldName": "default_billing") #38878
Comments
Hi @dariovranjkovic. Thank you for your report.
Join Magento Community Engineering Slack and ask your questions in #github channel. |
Hi @engcom-Dash. Thank you for working on this issue.
|
We are having the same issue on 2.4.6-p5, we figured we were pushing data incorrectly, but it may be a bug with Magento itself? |
Hi @engcom-Delta. Thank you for working on this issue.
|
Hi @dariovranjkovic , Verified the issue on 2.4.7 and it is reproducible. Steps to reproduce:- 1.Send request for update customer to rest API |
Hi @dariovranjkovic , Verified this issue on 2.4.3 and 2.4.7 and it is reproducible on 2.4.7. Hence confirming this issue. Steps to reproduce:- 1.Send request for update customer to rest API 2.4.3 ,working fine 2.4.7, error |
✅ Jira issue https://jira.corp.adobe.com/browse/AC-12318 is successfully created for this GitHub issue. |
✅ Confirmed by @engcom-Delta. Thank you for verifying the issue. |
❌ Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.adobe.com/browse/AC-12318 |
@magento I am working on this |
This issue was introduced in 0b600de. It breaks the backwards compatibility of the customer api. Following Version is affected too: 2.4.5-p9 |
Worth mentioning, that this B/C break seems to have slipped into the security-upgrade from 2.4.5-p8 -> 2.4.5-p9 with the commit 6fedf5c The question is, if this was by mistake and if we can revert it after the security update - or if this patch actually fixes a security problem. |
Preconditions and environment
Steps to reproduce
URL: https://shop.com/rest/V1/customers/3420
Body:
{
"customer": {
"firstname": "Company Name AB",
"lastname": "Location",
"addresses": [
{
"defaultShipping": "false",
"defaultBilling": "false",
"firstname": "Company Name AB",
"lastname": "-",
"postcode": "XXXXX",
"street": [
"Street Address"
],
"city": "CITY",
"telephone": "+XX XXX XXX XXX",
"countryId": "XX"
},
{
"defaultShipping": "true",
"defaultBilling": "true",
"firstname": "Company Name AB",
"lastname": "-",
"postcode": "XXXXX",
"street": [
"Street Address"
],
"city": "CITY",
"telephone": "+XX XXX XXX XXX",
"countryId": "XX"
}
]
}
}
or
{
"customer": {
"firstname": "Company Name AB",
"lastname": "Location",
"addresses": [
{
"default_shipping": "false",
"default_billing": "false",
"firstname": "Company Name AB",
"lastname": "-",
"postcode": "XXXXX",
"street": [
"Street Address"
],
"city": "CITY",
"telephone": "+XX XXX XXX XXX",
"countryId": "XX"
},
{
"default_shipping": "true",
"default_billing": "true",
"firstname": "Company Name AB",
"lastname": "-",
"postcode": "XXXXX",
"street": [
"Street Address"
],
"city": "CITY",
"telephone": "+XX XXX XXX XXX",
"countryId": "XX"
}
]
}
}
Expected result
Updated customer
Actual result
{
"message": "The %fieldName value is invalid. Set the correct value and try again.",
"parameters": {
"fieldName": "default_billing"
}
}
Additional information
It was working before upgrade on version 2.4.3 but now is not working on version 2.4.7
Release note
No response
Triage and priority
The text was updated successfully, but these errors were encountered: