I can not import the csv into Netbox

[newsharpstar]

Netbox Version 4.4.5
When I import the csv into the Netbox rack configuration ,the web display status is not availablity.
netbox.csv
Who can tel me how to import yuml or json file into Netbox?

[pheus]

Hi! 👋

Thanks for opening the discussion. Based on what you’ve shared, it looks like the file might not be valid CSV. NetBox expects a plain‑text CSV encoded as UTF‑8 (ideally without a BOM), with commas as separators, a header row, and the same number of columns on every line.

What NetBox expects

• Plain‑text CSV encoded as UTF‑8 (preferably without a BOM), with commas as separators.
• A single header row, then data rows. Every row must have the same number of columns.
• Choice fields must use the slug values (typically lowercase), not the human labels.
  For racks, for example, use active (not Active).
• Numbers should be numeric only (e.g., 42 not 42U), and booleans as true/false.

---

Rack import — minimal, known‑good header set

If you’re importing racks (what NetBox calls the rack objects themselves), this minimal header set works well in current releases:

name,site,status,role,u_height,width
RACK‑01,Example‑Site,active,network,42,19
RACK‑02,Example‑Site,active,server,48,19

Notes

• status must be a valid status slug (commonly active).
• u_height is just the number, no U suffix.
• width is usually 19 (or 23).

If you need more fields, add them exactly as shown under “CSV Field Options” on the import page (e.g., location, facility_id, serial, asset_tag, desc_units, comments). Keep all headers lowercase and match the names precisely.

Quick fixes that solve most “CSV not recognized” errors

• Remove any Markdown formatting (no |, #, or code‑block fences) and any leading sep=;/sep=, line.
• Save as UTF‑8 (without BOM if your editor offers the option); prefer Unix LF line endings.
• Quote only when needed—e.g., values containing commas: "Acme, Inc.".
• Verify there are no trailing commas or stray blank lines at the end of the file.