Skip to content
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

Fix issue causing attribute not loading when using getList #19620

Conversation

teganbold
Copy link
Contributor

Description (*)

As specified in issue #17759, CustomerRepository::getList() is unexpectedly returning NULL, when CustomerRepository::get() is correctly returning the value. Specifying the attribute as billing_company instead of company removes the conflict.

Fixed Issues (if relevant)

  1. M2.2.5 : CustomerRepository::getList() does not load custom attribute if the name is "company" #17759: M2.2.5 : CustomerRepository::getList() does not load custom attribute if the name is "company"

Manual testing scenarios (*)

  1. Create/Install two custom varchar customer attributes, one with the code company.
  2. Log the data when loading with getbyId():
    $customerById = $customerRepository->getbyId(x);
  3. Log the data when loading with getList():
    $customerByList = $customerRepository->getList($searchCriteria->addFilter('x, y')->create());

Previously, under custom attributes, both attributes were loading correctly for getbyId(), but company would pull NULL when using getList()

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds on Travis CI are green)

@magento-cicd2
Copy link
Contributor

magento-cicd2 commented Dec 7, 2018

CLA assistant check
All committers have signed the CLA.

@magento-engcom-team
Copy link
Contributor

Hi @MiliTree. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento-engcom-team give me test instance - deploy test instance based on PR changes
  • @magento-engcom-team give me 2.3-develop instance - deploy vanilla Magento instance

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

@teganbold teganbold force-pushed the fix/17759-load-company-as-custom-customer-attribute branch 2 times, most recently from 547fa1c to 81a212b Compare December 7, 2018 19:32
As specified in issue magento#17759, CustomerRepository::getList() is
unexpectedly returning NULL, when CustomerRepository::get() is correctly
returning the value. Specifying the attribute as billing_company instead
of company removes the conflict.
@teganbold teganbold force-pushed the fix/17759-load-company-as-custom-customer-attribute branch from 81a212b to d600179 Compare December 7, 2018 19:34
@teganbold
Copy link
Contributor Author

@magento-engcom-team give me test instance

@magento-engcom-team
Copy link
Contributor

Hi @MiliTree. Thank you for your request. I'm working on Magento instance for you

@magento-engcom-team
Copy link
Contributor

Hi @MiliTree, here is your new Magento instance.
Admin access: https://pr-19620.instances.magento-community.engineering/admin
Login: admin Password: 123123q

@magento-engcom-team
Copy link
Contributor

Hi @sidolov, thank you for the review.
ENGCOM-3655 has been created to process this Pull Request

@magento-engcom-team
Copy link
Contributor

@MiliTree thank you for contributing. Please accept Community Contributors team invitation here to gain extended permissions for this repository.

@ghost
Copy link

ghost commented Jan 4, 2019

Hi @MiliTree, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

@magento-engcom-team
Copy link
Contributor

Hi @MiliTree. Thank you for your contribution.
We will aim to release these changes as part of 2.3.1.
Please check the release notes for final confirmation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants