Updating Customer through rest/all/V1/customers/:id resets group_id if group_id not passed in payload

[abancroft0]

Preconditions

1. Magento Version 2.2.3 using rest API
2. Passing a JSON payload with minimum required data (email, first/last name, website_id, id)

Steps to reproduce

1. Update any customer who's group_id isn't the first group_id in the source list
2. Pass the customer payload with email, firstname, lastname, website_id, id

Expected result

1. I expect that only the data passed in the payload would be modified
2. Example: {"customer":{"email":"[email protected]","firstname":"magento","lastname":"user","website_id":1,"id":77486}} should leave the customer's full data structure unchanged.

Actual result

1. If the above customer had a group_id of 5, and our full group_id consisted of [1,2,3,4,5], the customer's group_id after passing the above payload would be set to 1:

Before:

PUT:

Results:

[bydrei]

@magento-engcom-team was able to replicate this. Ok if I self assign?

[magento-engcom-team]

Hi @ferrazzuk
Sure, feel free to assign it to yourself if you feel like trying and fixing this

Thanks!

[bydrei]

@magento-engcom-team pull request created.

[magento-engcom-team]

Hi @abancroft0. Thank you for your report.
The issue has been fixed in #14757 by @ferrazzuk in 2.1-develop branch
Related commit(s):

• 51f2f076a8fddbeb7b29914a1994236c29bdc369

The fix will be available with the upcoming 2.1.15 release.

[magento-engcom-team]

Hi @jignesh-baldha. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if your want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 3. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

[magento-engcom-team]

Hi @milindsingh. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if your want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 3. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

[m2-assistant]

Hi @KishorkumarKar. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 3. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

[KishorkumarKar]

@magento-engcom-team I have fixed this issue. Creating the PR #22700.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!