REST: Updating a customer without store_id sets the store_id to default

[808brinks]

Preconditions (*)

Magento 2.2.7 and Magento 2.3-develop provided by the bot.

Steps to reproduce (*)

1. Create multiple store views
2. Create a customer and set his store view to one that is not the default
3. Use the rest api to change the first name of the customer (put to PUT rest/V1/customers/8)

I used the following body. (note the missing store_id)

{ "customer":         {
            "id": 1,
            "group_id": 1,
            "default_billing": "0",
            "default_shipping": "0",
            "created_at": "2019-05-13 14:33:11",
            "updated_at": "2019-05-13 14:33:11",
            "created_in": "alternate store view",
            "email": "xxx@redacted.com",
            "firstname": "firstname alternate",
            "lastname": "lastname",
            "gender": 0,
            "website_id": 1,
            "addresses": [],
            "disable_auto_group_change": 0
        }
}

Expected result (*)

1. The first name is changed.
2. All fields not passed in the PUT call are not changed. (Including store_id).

{
    "items": [
        {
            "id": 1,
            "group_id": 1,
            "default_billing": "0",
            "default_shipping": "0",
            "created_at": "2019-05-13 14:33:11",
            "updated_at": "2019-05-13 14:40:56",
            "created_in": "alternate store view",
            "email": "bob.brinks@nl.spotler.com",
            "firstname": "firstname alternate",
            "lastname": "lastname",
            "gender": 0,
            "store_id": 2,
            "website_id": 1,
            "addresses": [],
            "disable_auto_group_change": 0
        }
    ],
    "search_criteria": {
        "filter_groups": [],
        "page_size": 10
    },
    "total_count": 1
}

Actual result (*)

1. The store_id is changed to the default store_id

{
    "items": [
        {
            "id": 1,
            "group_id": 1,
            "default_billing": "0",
            "default_shipping": "0",
            "created_at": "2019-05-13 14:33:11",
            "updated_at": "2019-05-13 14:40:56",
            "created_in": "alternate store view",
            "email": "bob.brinks@nl.spotler.com",
            "firstname": "firstname alternate",
            "lastname": "lastname",
            "gender": 0,
            "store_id": 1,
            "website_id": 1,
            "addresses": [],
            "disable_auto_group_change": 0
        }
    ],
    "search_criteria": {
        "filter_groups": [],
        "page_size": 10
    },
    "total_count": 1
}

[m2-assistant]

Hi @808brinks. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@808brinks do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @AlexWorking. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

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

• 4. 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!

• 5. 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

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

[808brinks]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

Hi @808brinks. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @808brinks, here is your Magento instance.
Admin access: https://i-22869-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[808brinks]

@m2-assistant I was able to reproduce the issue on the provided magento 2 instance.

[magento-engcom-team]

✅ Confirmed by @AlexWorking
Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-99688, MAGETWO-99689 were created

Issue Available: @AlexWorking, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.