[Classification Store] wrong headers in excel download

[heigpa]

Steps to reproduce

• Login as admin
• Open the Accessory Parts
• Add some Classification Store attributes to the column configuration
• Perform an excel export

Actual behaviour

• Headers in excel are not correct

Expected behaviour

• Correct headers should be used in excel file

Environment

• Studio Nightly
• Windows
• Google Chrome

[vin0401]

This seems to use the group, that is delivered by the backend.
But I guess it should use the name from the field definition instead for classification store fields.

I think this should be handled on the backend side.

[github-actions]

Thanks a lot for reporting the issue. We did not consider the issue as "Pimcore:Priority", "Pimcore:ToDo" or "Pimcore:Backlog", so we're not going to work on that anytime soon. Please create a pull request to fix the issue if this is a bug report. We'll then review it as quickly as possible. If you're interested in contributing a feature, please contact us first here before creating a pull request. We'll then decide whether we'd accept it or not. Thanks for your understanding.

[mcop1]

This seems to use the group, that is delivered by the backend. But I guess it should use the name from the field definition instead for classification store fields.

I think this should be handled on the backend side.

@vin0401 I agree, that it should use some sort of translated value, preferably the same values as in the grid column headers. But, as far as I know, the translation for those values happens in the front end. If we want to stay with that approach, front end needs to pass translated values to the endpoint, maybe somewhere inside the column configuration:

...
"columns": [
    {
      "key": "id",
      "locale": "en",
      "type": "system.id",    
      "group": [
        "system"
      ],
      "config": {
        "key": "value",
        "label": "<translated value>"
      }
    }
  ],
...

Otherwise we could end up with 2 different implementations for the same thing.

What do you think?

[vin0401]

Hey hey @mcop1

Sure we can enrich the data for that. :)
For the label option we should have everything in the frontend.
But we do not have the real system key for all cases. For example for the classification store fields.