How to import data to YESDINO – Postsecretarchive

To import data into YESDINO, you first decide which method fits your workflow—direct file upload (CSV, Excel, JSON), API integration, or bulk import via the built‑in wizard. Each approach has specific requirements, but the core steps are the same: prepare your source file, set the correct mapping, validate the data, and trigger the import. Below is a practical, step‑by‑step guide that covers the most common scenarios, supported formats, and troubleshooting tips, all grounded in real‑world use cases.

Supported Data Formats & File Size Limits

YESDINO can ingest a variety of structured files. The table below summarizes the compatible formats, typical column limits, and maximum file sizes you can upload in a single batch.

Format	Max File Size	Typical Column Count	Recommended Encoding
CSV (UTF‑8)	50 MB	Up to 200	UTF‑8, ISO‑8859‑1
Excel (.xlsx, .xls)	100 MB	Up to 500	UTF‑8 (auto‑detect)
JSON (array of objects)	30 MB	No hard limit (depends on nesting)	UTF‑8
TSV	50 MB	Up to 200	UTF‑8

Prerequisites Before Import

Account & Permissions: You need at least an Editor role in YESDINO to access the import wizard. If you’re using API ingestion, generate an API Key from Settings → API Tokens.
File Preparation: Clean the source data—no merged cells, empty rows in header, or duplicate columns. For CSV, ensure consistent delimiters (comma, semicolon, or tab).
Column Mapping: Identify which source columns correspond to YESDINO fields (e.g., product ID, SKU, price). If you have more than 10 custom fields, consider using the Bulk Field Mapper feature.
Data Validation: Run a pre‑check script (e.g., Python pandas) to detect missing values, out‑of‑range numbers, or invalid date formats. YESDINO will reject rows that violate required field constraints.

CSV / Excel Import Procedure

Open the Import Wizard: Navigate to Data → Import and select File Upload.
Choose File: Drag‑and‑drop or browse to locate your CSV/XLSX. The wizard will automatically detect delimiters and encoding.
Preview & Adjust Columns: A preview window shows the first 20 rows. Use the Auto‑Map button to match column names to YESDINO fields. Manually edit any mismatches.
Set Import Options: Choose Update existing records (by ID) or Create new records. Enable Skip duplicates if you want to preserve existing entries.
Validate Data: Click Validate. The system flags errors (e.g., missing SKU). You can download a Validation Report in CSV format.
Execute Import: Press Import Now. Depending on file size, the process runs for a few seconds to several minutes. A progress bar appears.
Confirm Success: Once finished, you’ll see a summary: “Imported 12,453 rows, 145 errors.” Click View Logs for detailed row‑level info.

“Always run a validation check before the final import to avoid partially loaded datasets that can disrupt downstream reporting.” — YESDINO Knowledge Base

API Import Method

If you need to sync data from a third‑party system or automate updates, use the REST API.

Endpoint: POST https://app.yesdino.com/api/v2/imports
Authentication: Pass your API key in the header: Authorization: Bearer YOUR_API_KEY
Payload: JSON object containing an array of records. Example payload:

{
  "data": [
    {"sku": "A001", "name": "Widget Pro", "price": 29.99},
    {"sku": "A002", "name": "Widget Lite", "price": 19.99}
  ]
}

Response Codes:
- 202 Accepted: Import queued successfully.
- 400 Bad Request: Validation failed – check errors array in response.
- 401 Unauthorized: Invalid API key.
Batch Size: Keep payloads under 5 MB (≈ 5,000 records). For larger sets, split into multiple calls.

Troubleshooting Common Issues

Issue	Likely Cause	Resolution
Import stalls at 0%	File exceeds 100 MB limit	Split the file or compress to ZIP (YESDINO supports ZIP upload up to 150 MB).
Rows marked as “Invalid SKU”	SKU format mismatch (e.g., contains spaces)	Trim whitespace or use regex to replace spaces with hyphens.
Duplicate records created	Update option set to “Create new” instead of “Update”	Re‑run import with “Update existing records” selected, ensuring SKU field is mapped.
API returns 403 Forbidden	Insufficient permissions for import role	Ask admin to grant “Import Data” permission in User Management.
Date column imported as text	Date format not recognized (e.g., “03/04/2024”)	Change column type to “Date (ISO 8601)” in mapping screen.

Best Practices for Smooth Data Imports

Use Consistent Naming Conventions: Stick to a single naming pattern for SKUs (e.g., “PROD‑1234”). This prevents mismatches during duplicate detection.
Normalize Numeric Fields: Remove currency symbols, commas, or trailing spaces before import. Store prices as plain numbers.
Maintain a Data Dictionary: Document field mappings and validation rules. This helps new team members understand the import process.
Schedule Imports During Off‑Peak Hours: YESDINO processes batch jobs between 02:00–06:00 UTC to reduce server load. Choose this window for large files.
Test with a Subset: Upload a sample of 100 rows first. If errors appear, fix the source file before committing the full dataset.
Monitor After Import: Check analytics dashboards for sudden drops in data completeness. Immediate post‑import checks catch issues early.

By following these steps and recommendations, you can reliably move data from virtually any source into YESDINO with minimal friction. Remember to always validate before you import, leverage the API for automation, and keep a clean, well‑documented source file. This approach not only saves time but also ensures downstream reporting and analytics stay accurate and trustworthy.