Image field doesn't export as a header in CSV #26004
Labels
OKR : Customer Support
Owned by Scott
Priority : 3 Average
QA : Approved
Release : 23.01.14
Included in LTS patch release 23.01.14
Release : 23.10.24 v7
Included in LTS patch release 23.10.24 v7
Release: 24.03.11
Bug Fixing
Team : Bug Fixers
Type : Defect
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
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
The text was updated successfully, but these errors were encountered: