CSV imports: which checks still need custom work in your current app?

Questions
1

We’re working on Tidygrain and checking whether a small CSV validation component is actually needed before developing it further.

We reviewed examples where Bubble’s Modify function or a change to text/number conversion already solved the problem. Other requests involved database lookups or complete import workflows, which a simple validator would not solve. We don’t want to build another plugin for a problem existing tools already handle.

If you maintain an app that imported a CSV recently, what happened on your last import?

• What were you importing, and roughly how many rows?
• Which built-in feature or plugin did you use?
• What still needed manual correction or custom work, and how often does that happen?

“Our current tool handles it fine” is useful feedback too. Please avoid sharing customer data; a description or a small invented example is enough.

We have an early local-file prototype for required fields, allowed values, numbers and duplicate keys. It does not perform database lookups or write records. If your example fits, we can compare it with an existing option and report the limitations. This is a research question, not a product launch.

2

Conversion of address components as well as dates prior to updating the DB so there is no need to run workflows to save those values to fields as the actual geographic address or date object.

Ability to clean CSV data prior to import for spaces at beginning or end of value like a trimmed function.