"is_subscribed" extension attribute not populating in customer GET /V1/customers/search?searchCriteria API

[lenlorijn]

It looks like internal bug MAGETWO-71829 was not fully solved. It made the "is_subscribed" field available in the API.
However this was not done for results of the search?searchCriteria API method.

More information: magento/devdocs#1384

Preconditions (*)

1. Magento is at version 2.3.2 & 2.3-develop

Steps to reproduce (*)

1. Install Magento
2. Add one or more customers
3. Request a list of customers through the /V1/customers/search?searchCriteria API method
4. Notice there are no extension attributes

Expected result (*)

1. Expected behavior: have a extension_attribute section that includes "is_subscribed" field. Just like when /V1/customers/:id: is requested.
   

Actual result (*)

1. no extension_attribute is present, no "is_subscribed" field is present.
   

[m2-assistant]

Hi @lenlorijn. 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 give me 2.3-develop instance - upcoming 2.3.x release

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

@lenlorijn 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 @engcom-Charlie. 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 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. Add label Issue: Confirmed once verification is complete.

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

[magento-engcom-team]

✅ Confirmed by @engcom-Charlie
Thank you for verifying the issue. Based on the provided information internal tickets MC-22735 were created

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

[dmanners]

Seems that the original fix only covered the only newsletter subscription information on the getById method. I wonder if the problem is that the Customer model does not actually use the class Magento\Customer\Model\Data\Customer but builds it's data model via Magento\Customer\Model\Customer::getDataModel which does not deal with the extension attributes methods.

8f3a4ed#diff-8b13fe3225a8e5f17fa52fa6c5b74edaR151

[koenner01]

Duplicate of my issue from 2018
#13252

[m2-assistant]

Hi @edenduong. 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.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.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. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

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

[VladimirZaets]

This issue is fixed in scope of #13252