Image field doesn't export as a header in CSV

[waqasakramdot]

Parent Issue

No response

Problem Statement

If a content type has an Image field, regardless of whether it is required or not, while exporting content for that content type the resulting CSV file doesn't contain an Image field header.

If an image field is required while importing, all those contents show an error (Field: "image" is required and was not found in the header) because the image field doesn't exist. The temporary solution is to read the image field in a CSV file and add all those image assets against it works, but It is not feasible if the contents are more.

Steps to Reproduce

1. Create a content type with an Image and text field
2. Add some contentlets for it
3. Export contents
4. The Image field will be absent

Acceptance Criteria

The Image field with values should be exported as other fields export in CSV file

dotCMS Version

23.1.5 -23.08.16

Proposed Objective

Customer Support

Proposed Priority

Priority 3 - Average

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

[github-actions[bot]]

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[erickgonzalez]

Working as it should! Now the images field is exported:

Identifier,languageCode,countryCode,title,images
a9136bae947d86bd1113385ff478ba67,en,US,t1,/images/gallery/beach/resort-cottage.jpg

[josemejias11]

Approved: Tested on master_270ac3c, Docker, macOS 13.0, FF v121.0.1