dotCMS / dotCMS/core

File field doesn't export as a header in CSV

Open
#33,944 1 comment 0 reactions 1 assignee View on GitHub

@Neehakethi is already working on this.

Since Nov 28, 2025.

OKR : Customer Support Priority : 3 Average Team : Maintenance Type : Defect
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Parent Issue

No response

Problem Statement

If a content type has an File 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 File field is required while importing, all those contents show an error (Field: "file" is required and was not found in the header) because the File field doesn't exist.

Steps to Reproduce
  1. Create a content type with an File and text field
  2. Add some contentlets for it
  3. Export contents
  4. The File field will be absent
Acceptance Criteria

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

dotCMS Version

Latest, Evergreen

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.