Posts in Best Practices · All posts
Developers are asking how to trigger imports from scripts and feed CSV data through APIs. Here's how to design import flows that work for both humans and machines.
Six lifecycle hooks let you inject custom logic at every stage of an import -- from preparing caches to setting owners to sending notifications.
The spectrum from silent failure to inline correction. Here's how to store, display, and resolve import errors without losing data.
Three behaviors for handling CSV references to existing data: match only, match or create, and always create. Here's when to use each.
500 rows reference 'Acme Corp'. Without deduplication, you get 500 company records. Here's the normalized-key cache pattern that prevents it.
That two-day CSV import task? It always becomes two months. Here's the iceberg of complexity hiding beneath the upload button.
Every user's CSV is different. Smart column mapping -- with auto-detection, preview values, and entity link mapping -- keeps imports flowing without support tickets.
Stop rejecting, logging, or silently skipping bad CSV rows. The validate-and-correct pattern lets users fix errors inline before import.