Magento 2.3 catalogsearch_fulltext no dropdown attribute labels but numbers

[onepack]

Preconditions (*)

1. Magento 2.3
2. PHP 7.2
3. Demo content

Steps to reproduce (*)

1. Use a standard of Create a custom dropdown attribute and make it available in the search.
2. Assign the attribute to an attribute group
3. Set the value of the attribute in a product
4. Reindex all indexes via cli command

Expected result (*)

1. Expected is that the product can than be searched via the dropdown value set in the product.
2. So search on a manufacturer and all products where that manufacturer is set will be shown in the result.

Actual result (*)

1. No results on any search with this value.
2. I found that in the catalogsearch_fulltext table in the database that value was not saved with the dropdown option label but with the option value number.
   This is the case for all dropdown attribute values that were set.
3. Searching with the actual stored dropdown option number returns the product in Magento.

[magento-engcom-team]

Hi @onepack. 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.

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

• yes
• no

[onepack]

Hi @magento-engcom-team
I can confirm that the first steps are made.

I have an other fresh install with demo content for an other project and there the same issue is present.

Not the selected option value label is stored in the fulltext table but the option value number.

No need to mention this has a high impact on the search functionality for the magento shops.
Manufacturer, color or any other dorpdown attribute values cannot be used in the search.

[onepack]

Searching on the frontend with pictures.
I should get the joust duffle bag but I get suggestions.

Searching with the number 213 that stands for BrandA in the Manufacturer attribute dropdown options gives me the product.

This is currently an issue in at least 3 projects that I run with magento2.3

[onepack]

It seems to be a bigger problem. Today I worked with the REST for customers to see if custom attributes were also available.
They are but here the dropdown values also show up as the corresponding numbers instead of the label values.

"custom_attributes": [
{
"attribute_code": "debtor_number",
"value": "115245"
},
{
"attribute_code": "segment",
"value": "239" (dropdown value)
},
{
"attribute_code": "segment_alt",
"value": "Different"
},
{
"attribute_code": "customer_erp",
"value": "245" (dropdown value)
},
{
"attribute_code": "erp_alt",
"value": "Different"
},
{
"attribute_code": "howdidyoufind",
"value": "260" (dropdown value)
}
]

[magento-engcom-team]

Hi @engcom-backlog-nazar. 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

• Next steps are available in case you are a member of Community Maintainers.

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

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

[onepack]

@engcom-backlog-nazar Do you need more information from my side?

[ghost]

HI @onepack thank you for you report, this issue has already fixed in 2.3-develop branch and will be available on 2.3.1 release.

[onepack]

@engcom-backlog-nazar
Sorry to ask but do you have a related issue in Github or any information on the fix so I can apply the fix in my current installations that are almost going live?

[onepack]

Any info on the release date?
Files included for the fix?
Issue Id?

[liltbrockie]

Hello .. we are on 2.3.3 and this issue is not fixed.. should it be?