Both tables are always written, never just the findings. A short findings
table can mean clean data, or it can mean many rules were skipped, and
those two situations look identical if the skipped table is dropped:
Excel (.xlsx) - four sheets laid out for a person to read:
Problems: one row per problem, definite errors first, then the ones
touching most records. What is wrong and the rule's number, the
variables it names (or the missing ones), and how many records it
affects, or whole dataset.
Records: one row per affected record and problem, in the order of
Problems, with USUBJID, SEQ and the values, such as
AESTDTC = "2024-02-30". A dataset with no subject gives the row
instead.
Not checked: the checks that could not run, grouped by reason, with
what to do about each, then when and how the check was run.
Rules: every rule, and whether it found problems, found none or could
not run. A rule that found nothing appears nowhere else.
CSV (.csv) - the tables as they are in R, for reading back into a
program. Findings go to path; the others go to sibling files with a
suffix before the extension, so issues.csv gives
issues_skipped.csv, issues_about.csv and issues_summary.csv (one
row per problem).
An existing file at path, or at a sibling path, is replaced.
In CSV files, a text value that begins with =, +, - or @ and is not
a plain number is written with a leading '. Findings quote the submission
data, and a spreadsheet program opening the CSV would otherwise run such a
value as a formula. Excel files store every value as text and need no such
change. CSV files are written as UTF-8 with a byte order mark, which Excel
needs to show non-English text correctly.
Excel output needs the writexl package. It is a Suggests, so if it
isn't installed you get a clear message telling you to install it or use
.csv instead, rather than a failure part-way through writing.