Keep the rule in the workbook and review the CSV as data
A CSV retains cell text and values, not the dropdown rule that controlled entry in Excel. Keep the original XLSX as the editable source and make a separate CSV for the receiving system. Saving the CSV back as XLSX will not reconstruct the missing rule.
Microsoft distinguishes workbook and text formats and documents what is retained in the CSV format. The practical consequence is that a status reading Active proves only that the value is present. It does not prove that the file will reject Paused next time someone edits it.
This walkthrough uses Windows desktop Excel for Microsoft 365, Excel 2024, or Excel 2021. The general export documentation also lists Excel 2019 and 2016, but the currently cited invalid-data-circle page lists only Microsoft 365, 2024, and 2021. Mac and web interfaces differ; the circle check below is a desktop feature and may not appear in Excel for the web. Use the documented desktop workflow or review every status against the approved list before exporting.
Build a small control example before using production products
Use a fictional two-product sheet to test both the values and the rule. The following is an illustrative procedure with expected outcomes, not a claim that an installed Excel application was tested during this article's preparation.
Create catalog-control.xlsx with a worksheet called Products. Put SKU in A1 and Status in B1. Enter P101 in A2 and P102 in A3. In E1 and E2, put the two allowed values, Active and Retired.
Select B2:B3 and open Data > Data Validation. Set Allow to List, use =$E$1:$E$2 as the source, and enable In-cell dropdown. On Error Alert, enable the alert and select Stop. The Microsoft dropdown instructions describe these controls. Using a cell range avoids guessing which separator your regional settings expect in a manually typed list.
Choose Active for P101 and Retired for P102. As a deliberate negative check, type Paused directly into B2. Expect a Stop alert; cancel that edit and confirm B2 still reads Active. Save the workbook. If no alert appears, verify the selected cell's validation settings before proceeding.
This small test checks direct entry only. It is not evidence that every route into a production workbook enforces the rule.
Inspect existing values before creating the exchange copy
An existing dropdown does not establish that every stored value is valid. Microsoft notes that copying, filling, formulas, or macros can introduce invalid values without the normal direct-entry alert. On the desktop editions scoped above, use Data > Data Validation > Circle Invalid Data to inspect values against their existing rules. See Microsoft's invalid-data-circle guidance.
For a reproducible second negative check, use a separate practice copy of the workbook. Temporarily turn off the error alert for B3 while keeping its List criterion, enter Paused, then restore the Stop alert. Run Circle Invalid Data: B3 should be circled because its stored value is outside the two-item list. Change it back to Retired and repeat the check. Do not make this experiment in the production control file.
No circles is meaningful only where the intended validation rules are actually applied. Check the rule range as well as the values, especially when new product rows have been appended. An unrestricted cell can hold a bad status without violating a rule it never had.
Export just the approved product columns
Create a separate export workbook containing only A1:B3 from the corrected source, pasted as values into a blank worksheet. Confirm that its first row is SKU and Status, and that it has exactly the two product rows. Do not copy the E-column helper list into the exchange file.
Follow File > Save As and select the CSV format required by your receiving system. Use a new name, such as catalog-status-review.csv. Microsoft's text import and export instructions explain the active-worksheet export and format warnings. Keep catalog-control.xlsx separately; it remains the place to inspect and maintain the rule.
For a comma-delimited output, the expected records are SKU,Status, then P101,Active, then P102,Retired, each on its own line. The locale's export settings can affect the delimiter, so inspect the actual text before choosing an import option. Neither a dropdown arrow nor a validation definition should be expected in these records.
Verify the exported values without mistaking a preview for validation
Open the fictional CSV in CSV / Excel Online Preview. With Search empty, this example should show two data rows and two columns. Search for P101 and confirm its status is Active; repeat for P102 and Retired. Clear Search and recheck both rows before handing off the file.
For this two-row example, reading every Status cell is a complete value check against the two allowed words. Searching only for Paused would be weaker: it would miss other invalid spellings. For a large catalog, use an approved full-file check against the receiving system's exact allowed values rather than treating a few searches as complete validation.
ToolboxHub previews parsed cells. It does not inspect Excel's validation rules, edit the workbook, or reject statuses according to your product schema. The first row becomes the header; only the first 500 matching data rows are rendered. Its Search matches text in any cell, and its Export CSV button downloads the entire parsed current sheet, not only search matches. Preserve Excel's export for this review instead of introducing another conversion.
The parser loads from jsDelivr before reading the selected file locally. If that dependency is blocked, use an approved local viewer. Parsed numbers and dates may differ from spreadsheet display formatting, so this example deliberately uses alphanumeric SKUs and plain status text.
Diagnose the symptom at the right stage
A missing arrow in the CSV is expected; a missing arrow in the retained XLSX needs investigation. In the XLSX, select the cell, check that List validation and In-cell dropdown are enabled, and verify that the intended range includes it. In a CSV, return to the source workbook instead of trying to repair the rule in the exchange file.
If Paused appears in the export, stop the handoff. Inspect that row in the source, confirm its rule, and check how the value arrived. Correct it with the product owner's approval, then recreate the export. Replacing only the CSV value leaves the next export vulnerable to the same source error.
If extra columns or helper values appear, the export range was too wide. Rebuild the exchange workbook from A1:B3 for this example and verify two columns again. If the two fields appear in one column in the destination, check the actual delimiter and that system's import setting.
Finally, a destination can reject Active even when the workbook accepts it, because its schema may require a different vocabulary or case. Confirm that contract separately and use a safe import preview when available. The spreadsheet rule, exported text, and destination acceptance are three separate checks.
Frequently asked questions
Can CSV preserve an Excel dropdown if I rename it to XLSX?
No. Renaming does not convert the contents or recreate validation. Recover the original workbook or deliberately rebuild the rule in a proper workbook.
Does a valid-looking Status column prove validation survived?
No. The text can survive while the entry restriction disappears. Inspect the retained workbook's settings separately.
Can I use Circle Invalid Data in Excel for the web?
The cited Microsoft page describes a desktop feature and warns that it may not appear on the web. Use the scoped desktop editions or another complete value-review method.
Can ToolboxHub fix the CSV or restore the source rule?
No. It previews extracted data and can create a separate CSV download, but it cannot edit cells or write validation rules back into your XLSX.