Export of attribute-type extensibleEnum and extensibleMultiEnum return ID and array in v2.0

Lennart · July 10, 2025, 12:44pm

If I make an export job the attribute of type extensibleEnum returns the ID, not the value.
And extensibleMultiEnum returns the value “Array”

What is wrong?

In the forum we hade before this I think I asked the same question, but now the answer is gone.

Lennart · July 11, 2025, 9:28am

If I filter products I can get some results, (one list is still showing “markForUnlinkedAttribute” instead of names from extensibleMultiEnum).
But if a change the filter to be more inclusive, it changes back to ID and “array” as values.
I know I had this problems long time ago, and it driving me crazy that I can´t find why.

I really don´t want to reinstall pim from scratch…

Lennart · July 11, 2025, 1:48pm

Found the last time I had this problem

github.com/atrocore/atrocore

Export sometimes return option ID instead of value

opened 11:23AM - 05 Jul 24 UTC

closed 11:13AM - 18 Jul 24 UTC

exeqtwasnotfree

I can´t find what is the issue. I have several exports, that since updating 202…4-07-02 to versions: - Upgrading atrocore/atrocore-legacy (1.0.7 => 1.0.8) - Upgrading atrocore/core (1.10.34 => 1.10.35) - Upgrading atrocore/export-feeds (1.8.14 => 1.8.15) - Upgrading atrocore/import-feeds (1.6.17 => 1.6.18) - Upgrading atrocore/pim (1.13.16 => 1.13.17) Some of the lists, exporting the ID instead of value. If I manual run the export on a specific product the export works. If I experiment with selecting 5-25 products a bit random and export, i sometime get the value, and sometime gets the ID, and I can´t figure out the cause. Both single-option and multi-option have the problem. Not all "columns" in an export have the problem at the same time, but some of the fields are more prone to fail than others. And I cant see the code for export, on github anymore, so I don´t know what's changed in export-feeds (1.8.14 => 1.8.15)

Is it a repeated problem?

Anna · July 11, 2025, 3:13pm

Hello Lenart,

After you upgrade the system to Core 2.0, you will need to reconfigure attribute import and export again. We informed about this in the release notes. Due to the extensive changes introduced, automatic migration of these feeds is not possible. Just remove attributes from the configurator and add them again.

Lennart · July 11, 2025, 5:10pm

I have made a new export from beginning, with only sku and 3 attribute, and have this problem.
I know I have to renew the exports, ( I will remake some of them from scratch do to the many attributes in it), but if I cant make a P.O.C. working, I may have to return to 1.11.10 until it get solved, ether if this is a bug, or if I have to install a new server and import all data.

Anna · July 15, 2025, 7:02am

You are right, there is indeed a bug with exporting attributes of the multi-value list type. Instead of values, “Marker for Unlinked Attribute” is exported. We will fix it. As for the export for the List type, everything is OK with it, there are option values in the exported file.

Anna · August 19, 2025, 4:33pm

Hello Lennart,
Was your issue resolved after the update, and if not, were you able to solve it in another way?

Lennart · August 20, 2025, 6:01am

Hello Anna,
After my tests in July, which didn’t go so well, I had to revert back to v1.11.10. Then I’ve been on vacation, and now I won’t have time to check this again for maybe 2-3 weeks.
I had the chance in July to upgrade, at worst the next chance will be around the turn of the year, just because so much has changed I don’t see that I can do small upgrades per week, but have to plan a big upgrade to a version that works, and where users are not allowed to use pim until I’m done with all the changes and updates to import/export.