Skip to main content

Options

Required

importerKey: string

This can be found in the admin panel.

importerKey = "importer-key";

Optional

user: json object

Contains details of the user, so that they can be identified when your backend receives a webhook.

user={{ userId: "12345" }}

metadata: json object

If you have additional data which you want to associate with the import but isn't related to the user, you can use the metadata prop. This will also be included in the webhook your backend receives.

metadata={{ anotherId: "123" }}

onClose: function

A function that is triggered when the importer modal is closed.

import UseCSV from "@usecsv/react";
function App() {
return (
<div className="App">
<UseCSV
importerKey="your-importer-key"
onClose={() => {
console.log("Importer modal is closed");
}}
>
Import Data
</UseCSV>
</div>
);
}
export default App;

importerDisplay: inline | modal

Choose how to display your importer in frontend:

  • modal: the default display.
  • inline: displays the importer as an inline element to a parent element with id usecsv-importer-inline-wrapper and position: relative;. You can custom style the parent element and set width and height for the importer.
// example of using inline display
import UseCSV from "@usecsv/react";

function App() {
return (
<div className="App">
<h1>Start importing your data</h1>
<UseCSV
importerKey="your-importer-key"
user={{ userId: 12345 }}
importerDisplay="inline"
/>
{/* element with id usecsv-importer-inline-wrapper is required */}
<div
style={{
position: "relative",
border: "1px solid #027ad6",
width: "1200px",
height: "650px",
marginTop: "20px",
marginLeft: "auto",
marginRight: "auto",
}}
id="usecsv-importer-inline-wrapper"
/>
</div>
);
}

export default App;
Inline importer modal

onData: Function

onData: (data: {
uploadId: number;
fileName: string;
rows: Record<string, string | number | undefiend>[];
user?: {
userId: string;
};
metadata?: Record<string, string | number>;
}) => void | Promise<{ errors?: { row: Record<string, string | number | undefined>; error: string }[] } | void>

If you prefer to handle your data locally (and disable uploading csv data to UseCSV), you can set the onData callback option and the data will not be uploaded to UseCSV and sent to your callback function instead when the user finishes importing the CSV.

// example data
{
uploadId: 334,
fileName: "data.csv",
user: { userId: "12345" },
metadata: { anotherId: "1" },
rows:[
{
first_name:"Mari",
email:"mari@gmail.com"
},
{
first_name:"John",
email:"john@gmail.com"
}
]
}

Return errors

  • You can retrun from the onData function an array of rows with errors and the user will be provided with a downloadable .csv file containing the rows and thier error.
// example of onData error handeling
onData: async (data) => {
/*
* do your validation
*/

// if no errors
return;

// if you found rows with errors, save the correct rows, and retrun an array of rows with errors
return Promise.resolve({
errors: [
{
row: {
first_name: "Mari",
email: "mari@gmail.com",
},
error: "email already exists",
},
],
});
};

render: function component

render is a React funtion component with an openModal argument, allowing you to replace the default UseCSV button with your custom component. The openModal argument is a function that triggers the import modal when clicked.

render={(openModal) => <button onClick={openModal}>Import Data</button>}
Usage example with render and callback
import UseCSV from "@usecsv/react";

function App() {
const renderButton = (openModal) => {
return (
<button
onClick={openModal}
style={{
width: "170px",
height: "70px",
color: "#fff",
backgroundColor: "#027ad6",
boxShadow: "0 32px 64px rgba(0,0,0,0.07);",
font: "700 24px sans-serif",
textAlign: "center",
border: "none",
borderRadius: "3px",
}}
>
Import Data
</button>
);
};
return (
<div className="App">
<UseCSV
importerKey="your-importer-key"
user={{ userId: 12345 }}
render={(openModal) => renderButton(openModal)}
onData={(data) => {
console.log("uploadId:", data.uploadId);
console.log("rows:", data.rows);
}}
/>
</div>
);
}

export default App;
Usage example with render

Validation Hooks

Validation Hooks allow you to validate user uploads during the interactive import process, so that your users can address any invalid data before it's imported into your app. When configuring your importer in the UseCSV admin, you can choose which columns to enable Validation Hooks for.

To use Validation Hooks you'll need to implement two callbacks: onRecordsInitial and onRecordEdit. They will pass you the uploaded data (for the columns Validation Hooks is enabled for) and allow you to return errors, info messages or heal values to the user.

Check using Validation Hooks codesandbox example
Check examples of using Data Healing:

onRecordsInitial: Function

onRecordsInitial callback function is triggered after the user uploads a file and once the column matching is completed. Data from the columns with Validation Hook enabled will be sent to your frontend, so you can run your own validation and replace current value (Data Healing) or return rows with errors if any and custom error and info messages to be shown to the user. Data will be sent in batches of 1000 rows.

type onRecordsInitial = ({
uploadId,
fileName,
importerId,
batch,
user,
metadata,
rows,
}: {
uploadId: string;
fileName: string;
importerId: string;
batch: {
index: number;
count: number;
totalRows: number;
};
user?: Record<string, string | number> | null;
metadata?: Record<string, string | number> | null;
rows: Array<{
row: number;
data: {
[columnName: string]: {
value: string | number;
isValid: boolean;
};
};
}>;
}) =>
| Promise<Array<{
row: number;
[columnName: string]: Array<{
message: string;
level: "error" | "info" | "healing";
newValue?: string; // required for healing level
}>;
}> | void>
| Array<{
row: number;
data: {
[columnName: string]: Array<{
message: string;
level: "error" | "info" | "healing";
newValue?: string; // required for healing level
}>;
};
}>
| void;
Usage example

Assuming Validation Hooks are enabled for email and age columns only, where:

  • email column is configured with validation format of email in admin panel.
  • age column is configured with validation format of number in admin panel
<UseCSV
importerKey="your-importer-key"
user={{ userId: "12345" }}
metadata={{ anotherId: "1" }}
onRecordsInitial={({
uploadId,
fileName,
importerId,
batch,
user,
metadata,
rows,
}) => {
console.log({
uploadId,
fileName,
importerId,
batch,
user,
metadata,
rows,
}); // check below the console output

// run custom validation
// if no errors
return;

// or return an array of errors
return [
{
row: 1,
data: {
email: [
{
message: "Email already exists", // first error message
level: "error",
},
{
message: "Invalid email", // second error message (optional)
level: "error",
},
],
age: [
{
message: "Age must be 18 or above",
level: "info",
},
],
},
},
{
row: 2,
data: {
age: [
{
message: "Age must be a number",
level: "error",
},
],
},
},
{
row: 3,
data: {
email: [
{
message: "Typo has been corrected",
level: "healing",
newValue: "invalid@gmail.com", // (notice the original email was invalid@gmail@.com)
},
],
},
},
];
}}
>
Import Data
</UseCSV>
// console output
{
uploadId: 334,
fileName: "data.csv",
importerId: "123-456-789"
batch: {
index: 1;
count: 1;
totalRows: 3;
},
user: {
userId: "12345",
},
metadata: {
anotherId: "1",
},
rows: [{
row: 1,
data: {
email: {
value: "mari@gmail.com",
isValid: true
}
age: {
value: 5,
isValid: true
}
}
},
{
row: 2,
data: {
email: {
value: "john@gmail.com",
isValid: true
},
age: {
value: "not a number",
isValid: false
}
}
} {
row: 3,
data: {
email: {
value: "invalid@gmail@.com",
isValid: false
},
age: {
value: 35,
isValid: true
}
}
}
]
}
Data table with comments and errors
onRecordsInitial callback function parameters
type ParamsType = {
uploadId: string;
fileName: string;
importerId: string;
batch: {
index: number;
count: number;
totalRows: number;
};
user?: Record<string, string | number> | null;
metadata?: Record<string, string | number> | null;
rows: Array<{
row: number;
data: {
[columnName: string]: {
value: string | number;
isValid: boolean;
};
};
}>;
};
  • uploadId: upload ID.
  • fileName: uploaded file name.
  • importerId: importer key that can be found in the admin panel.
  • batch: json object of batch details, with keys of:
    • index: number of batch starting from 1.
    • count: number of total batches expected to be received.
    • totalRows: number of total rows per file.
  • user json object of user object if provided.
  • metadatajson object of metadata object if provided.
  • rows: array of json objects of rows, with keys of:
    • row: number of row in the uploaded file starting from 1.
    • data: json object of columns:
      • columnName: array of json objects of the configured columns, with keys of:
        • value: value of cell.
        • isValid: boolean validation result according to the validation format configured for each column in admin panel when the column was created.
Return errors, info messages or heal values
type ResponseType = Array<{
row: number;
data: {
[columnName: string]: Array<{
message: string;
level: "error" | "info" | "healing";
newValue?: string; // required for healing level
}>;
};
}>;
  • row: required row number already included in the recieved data.
  • data: json object of columns:
    • columnName: array of json objects with keys of: message and level. At lease one column should be included in the response.
      • message: custom error message shown to user.
      • level: error | info:
        • error is used to define error messages.
        • info is used to define info messages.
        • healing is used to overwrite user's data.
      • newValue: required string for healing level to replace current value in a cell.

onRecordEdit: Function

onRecordEdit callback function is triggered after any of the cells is edited in the Match Columns step. The edited row will be sent to your frontend, so you can run your own validation and replace current value (Data Healing) or return errors if any and custom error and info messages to be shown to the user.

type onRecordEdit = ({
uploadId,
fileName,
importerId,
user,
metadata,
row,
}: {
uploadId: string;
fileName: string;
importerId: string;
user?: Record<string, string | number> | null;
metadata?: Record<string, string | number> | null;
row: {
row: number;
data: {
[columnName: string]: {
value: string | number;
isValid: boolean;
}
}
};
}) =>
| Promise<{
row: number;
data:{
[columnName: string]: Array<{
message: string;
level: "error" | "info" | "healing";
newValue?: string; // required for healing level
}
};
}> | void>
| {
row: number;
data: {
[columnName: string]: Array<{
message: string;
level: "error" | "info" | "healing";
newValue?: string; // required for healing level
}>
};
}
| void;
Usage example

Assuming Validation Hooks are enabled for email and age columns only, where:

  • email column is configured with validation format of email in admin panel.
  • age column is configured with validation format of number in admin panel
<UseCSV
importerKey="your-importer-key"
user={{ userId: "12345" }}
metadata={{ anotherId: "1" }}
onRecordEdit={({ uploadId, fileName, importerId, user, metadata, row }) => {
console.log({
uploadId,
fileName,
importerId,
user,
metadata,
row,
}); // check below the console output

// run custom validation
// if no errors
return;

// or return a json object
return Promise.resolve({
row: 2,
data: {
email: [
{
message: "Invalid email", // first error message
level: "error",
},
{
message: "Email does not exist", // second error message (optional)
level: "error",
},
{
message: "invalid@email.com", // optional suggestion (notice below in console output the original email was invalid@gmail@.com)
level: "info",
},
],
},
});
}}
>
Import Data
</UseCSV>
// console output
{
uploadId: 334,
fileName: "data.csv",
importerId: "123-456-789"
user: {
userId: "12345",
},
metadata: {
anotherId: "1",
},
row: {
row: 2,
data: {
email: {
value: "invalid@gmail@.com",
isValid: false
},
age: {
value: 35,
isValid: true
}
}
}
}
onRecordEdit callback function parameters
type ParamsType = {
uploadId: string;
fileName: string;
importerId: string;
user?: Record<string, string | number> | null;
metadata?: Record<string, string | number> | null;
row: {
row: number;
data: {
[columnName: string]: {
value: string | number;
isValid: boolean;
};
};
};
};
  • uploadId: upload ID.
  • fileName: uploaded file name.
  • importerId: importer key that can be found in the admin panel.
  • user json object of user object if provided.
  • metadatajson object of metadata object if provided.
  • row: json object of edited row, with keys of:
    • row: number of row in the uploaded file.
    • data: json object of columns:
      • columnName: array of json objects of the configured columns, with keys of:
        • value: value of cell.
        • isValid: boolean validation result according to the validation format configured for each column in admin panel when the column was created.
Return errors, info messages or heal values
type ResponseType = {
row: number;
data: {
[columnName: string]: Array<{
message: string;
level: "error" | "info" | "healing";
newValue?: string; // required for healing level
}>;
};
};
  • row: required row number already included in the recieved data.
  • data: json object of columns:
    • columnName: json object with keys of: message and level. At lease one column should be included in the response.
      • message: custom error message shown to user.
      • level: error | info:
        • error is used to define error messages.
        • info is used to define info messages.
        • healing is used to overwrite user's data.
      • newValue: required string for healing level to replace current value in a cell.