Troubleshooting CSV Reports That Generate Without Expected Data

Use this article when a CSV report completes but contains scripts, technical content, or no expected selected data.

Use this guidance when the symptoms described above match what you are experiencing. The steps are intentionally limited to customer-safe actions supported by the ticket history; they do not assume backend access.

1. Confirm you are running the intended report and have selected the expected criteria or records.

2. Run the report again and note whether the issue affects CSV output only or other output formats as well.

3. If another report-delivery option is available, test it and record whether the output differs.

4. Do not repeatedly alter source data to work around the issue. If the CSV still lacks expected data, submit a support ticket.

If the issue is resolved, confirm the expected record, report, document, batch, or access behavior is now available before continuing normal processing. If the issue remains, use the escalation guidance below.

Submit a new support ticket when the steps above do not resolve the issue, when the behavior affects multiple users or time-sensitive processing, or when the article directs you to stop rather than make additional changes.

• Report name
• Date/time attempted
• Selected criteria or record range
• Output format (CSV)
• Screenshot or sample of the unexpected output