A specific value from list is not always exported

[exeqtwasnotfree]

Hello
I have an unusual and strange problem.
I have an export job of products that exports, among other things, a self-created product field of the list type.
The list has 7 choices, one of which has a value in the form of two words with a space between them.
("Quote", "Prototype", "New part", "Normal", "Obsolete" ...)
When the export job has filters on a given classification, only this two-word choice becomes empty in the export file, the other choices are included. (ca 1600 products)
But if I add a classification to the filter to get more products in the export (ca4700 products), the selection is included in the export file even on the products that previously did not receive the value.

It seems the export cant handle the two word value until I have more or less products to export, but the job is suppose to export the given classification.

I can reproduce the error in new export job.
I have the same error both in PROD and TEST environment.
I can't reproduce it on your demo.
I updated to the latest version last morning.
The bug has been with us since the 22nd of February, it worked on the 21st.
Have you ever heard of anything like this?

[exeqtwasnotfree]

Eureka !
I have found a clue, I have some products missing the selection, if these come first in the export sort-order, the value is empty. but if I sort them last, it works. Somehow if the value is null in the beginning of the export job, it have problem with two-word-variant later.

[AnnZast]

Hello,
Did you manage to reproduce the bug on the demo? Because I have no problems with exporting options consist of multiple words, even if the export starts with products with a null field value.
Here is an example of my export

[AnnZast]

On February 21 we added relation many-to-many between Classification Attribute and List Option entities. This allows to choose options for an attribute that can only be used in a particular classification.
This change should not affect the export of list type fields, but there may be a bug related to it and the reason is in the product classification. You have a problem when exporting fields, not attributes, right?

[exeqtwasnotfree]

I can´t recreate the problem in demo.
It is a specific product-field that have this problem, (not attribute), I have not seen this on any other field.
I can recreate the problem in a new product-export-job, and only export SKU, NAME and the field, order by the field ASC. This will return empty value on all products that have the two word value, and return null for them missing a value.
If I order by field DESC, the two word value shows, and all the null-values is last in exported file.

[atrolex]

is it solved? Do the problem exists within the last versions of our software?

[exeqtwasnotfree]

Hi, the problem still exist in 1.9.13. But the workaround is to sort the export by the field DESC, or exclude the products that have null as the value.
So we are running as usual with these settings set, but I can recreate the problem by only adjusting the filter.