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

[kanduvisla]

I have custom EAV attributes named "company" for customers, but this is not loaded if I use the CustomerRepository::getList()-method. Other custom attributes seem to be loaded properly.

Preconditions

1. Magento 2.2.5

Steps to reproduce

1. Create customer EAV attribute named "company" (varchar)
2. Populate it with some data
3. Load it with CustomerRepository::get() / getById()
4. Load it with CustomerRepository::getList()

Expected result

In both the situations, $customer->getCustomAttribute('company')->getValue() should return the value defined for this attribute.

Actual result

The get() / getById()-method loads the proper value, getList() returns NULL.

Possible cause

My best guess is that it has something to do with the fact that getList() joins the customer address that also has a company-column:

$collection->joinAttribute('billing_postcode', 'customer_address/postcode', 'default_billing', null, 'left')
    ->joinAttribute('billing_city', 'customer_address/city', 'default_billing', null, 'left')
    ->joinAttribute('billing_telephone', 'customer_address/telephone', 'default_billing', null, 'left')
    ->joinAttribute('billing_region', 'customer_address/region', 'default_billing', null, 'left')
    ->joinAttribute('billing_country_id', 'customer_address/country_id', 'default_billing', null, 'left')
    ->joinAttribute('company', 'customer_address/company', 'default_billing', null, 'left');

Possible solution

I can think of 2 solutions:

• Throw an exception that company (or whatever other joined attributed) is a reserved keyword.
• Allow the customer model to override the address attributes (order of loading)

Workaround

I currently have to do the following workaround (in my situation, my search criteria always returns 1 customer):

$customers = $customerSearchResult->getItems();
return $this->customerRepository->getById($customers[0]->getId());

[magento-engcom-team]

Hi @kanduvisla. 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 {$VERSION} instance

where {$VERSION} is version tags (starting from 2.2.0+) or develop branches (2.2-develop +).
For more details, please, review the Magento Contributor Assistant documentation.

@kanduvisla do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

@kanduvisla, thank you for your report.
We've acknowledged the issue and added to our backlog.

[irving0mar]

#mm18mx

[magento-engcom-team]

@irving0mar thank you for joining. Please accept team invitation here and self-assign the issue.