icon | description |
---|---|
react |
Using @impler/react package you can embed CSV Excel Importer into your application with just few lines of code. |
Let's do a quick review of how to use @impler/react
in your application.
You copy this snippet to your code before the closing body tag.
{% code overflow="wrap" %}
<script type="text/javascript" src="https://embed.impler.io/embed.umd.min.js" async></script>
{% endcode %}
It will add impler
variable in window
, so you can call its init
and show
method.
Add @impler/react
in your application by running the following command.
npm i @impler/react
# or
yarn add @impler/react
@impler/react
provides headless useImpler
hook that you can use to show an import widget in your application.
import { useImpler } from '@impler/react';
const { showWidget, isImplerInitiated } = useImpler({
projectId: "",
templateId: "",
accessToken: "",
});
<button disabled={!isImplerInitiated} onClick={showWidget}>
Import
</button>
{% hint style="info" %}
isImplerIntiated
becomes true when the import widget is ready to open and import data. It remains false when there are some errors with the provided values. Errors get logged in the console panel of the browser.
{% endhint %}
You can customize any text in the import widget, here is the sample. A full list of available texts is available at #available-texts.
import { useImpler } from '@impler/react';
const { showWidget, isImplerInitiated } = useImpler({
...
texts: {
STEPPER_TITLES: {
REVIEW_DATA: 'Check Data', // New Title
},
},
});
<button disabled={!isImplerInitiated} onClick={showWidget}>
Import
</button>
Prop | Type | Description |
---|---|---|
onUploadStart | (value) => void | Function that get's called when user starts upload |
onUploadTerminate | (value) => void | Function that get's called when user leaves spreadsheet import in between |
onUploadComplete | (value) => void | Function that gets called when user completes the import |
onWidgetClose | () => void | Function that gets called when widget is closed |
onDataImported | (data) => void | Function that gets called with all imported data. Read more at using-frontend-callback.md |
const { showWidget, isImplerInitiated } = useImpler({
projectId: "",
templateId: "",
accessToken: "",
onUploadStart: (uploadInfo) => {
console.log("User Started Importing", uploadInfo);
},
onUploadTerminate: (uploadInfo) => {
console.log("User left Import in middle", uploadInfo);
},
onUploadComplete: (uploadInfo) => {
console.log("User completed import", uploadInfo);
},
onWidgetClose: () => {
console.log("Import widget is closed");
},
onDataImported: (data) => {
console.log("Imported data:", data);
}
});
Your application may be developed by keeping dark and light modes in mind. So to let the Import widget show the widget overlay properly, you need to pass colorScheme
in showWidget
function.
Allowed values for colorScheme are light or dark.
showWidget({ colorScheme: 'light' })
Data Seeding in Sample File
You can provide default data to fill in the Sample file that gets generated from the Import widget. Default data act as a placeholder for the user to further add or update the data.
Here is an example of how to provide data to fill in the sample file,
showWidget({
data: [
{ country: 'ABC' },
{ country: 'DEF' },
{ country: 'GHE' },
]
});
Providing Runtime Schema
The schema and output provided in the web.impler.io portal for any import behave as default values for any Import. It's possible to override the default schema and output, to adapt dynamic nature of Import.
Here is an example of how to provide dynamic schema and output,
showWidget({
schema: [
{
key: 'country',
name: 'Country',
type: 'String'
}
],
output: {
"%data%": {
"country_id": "{{country}}"
},
"page": "{{page}}",
"chunkSize": "{{chunkSize}}",
"isInvalidRecords": "{{isInvalidRecords}}",
"template": "{{template}}",
"uploadId": "{{uploadId}}",
"fileName": "{{fileName}}",
"extra": "{{extra}}"
}
});
You can provide #advanced-validations in the column as validations
key,
showWidget({
schema: [
{
"key": "Department Code",
"name": "Department Code",
"type": "String",
"validations": [
{
"validate": "unique_with",
"uniqueKey": "Employee No"
}
]
},
{
"key": "Employee Id",
"name": "Employee Id",
"type": "Number",
"validations": [
{
"validate": "unique_with",
"uniqueKey": "Employee No"
}
]
}
]
});
If you're using typescript, you can leverage typescript types, like,
import { useImpler, ColumnTypes, ValidationTypes } from '@impler/react';
const { showWidget } = useImpler({ ... })
showWidget({
schema: [
{
key: 'country',
name: 'Country',
type: ColumnTypes.STRING,
"validations": [
{
"validate": ValidationTypes.LENGTH,
"min": 5,
"max": 100,
"errorMessage": "Country Name must be between 5 to 100 characters"
}
]
}
]
});
It's an obvious need that we want to pass userId
or orgId
representing who imported the data. In that case, you can pass that data in an extra parameter.
You can pass string
, object
, or array
in extra. Here is an example of how to do it,
const { showWidget, isImplerInitiated } = useImpler({
projectId: "",
templateId: "",
accessToken: "",
extra: {
userId: '4ddhodw3',
time: new Date().this string()
}
});
The extra parameters get sent to an application during the webhook call.
Impler's import widget provides closeWidget
a method that closes the import widget. Useful to close the import widget once data is imported.
const { showWidget, closeWidget, isImplerInitiated } = useImpler({
projectId: "",
templateId: "",
accessToken: "",
onDataImported: (data) => {
console.log("Imported data:", data);
closeWidget();
}
});
By default, the Import widget takes the name of the Import to show in the title. But it's possible to change the title
from the implementation side too. Helpful to keep the title separate from what the name is given in the web portal.
Here is how,
const { showWidget, isImplerInitiated } = useImpler({
projectId: "",
templateId: "",
accessToken: "",
title: "Employee Import"
});
You can pass a primary color to the import widget, which will update the colors of all buttons accordingly to match your app's theme color.
const { showWidget, isImplerInitiated } = useImpler({
projectId: "",
templateId: "",
accessToken: "",
primaryColor: '#5f45ff'
});
In case the backend endpoint is authenticated with the token, it's possible to provide token value from the implementation side. You can provide a string or async function that returns the token value.
const { showWidget, isImplerInitiated } = useImpler({
projectId: "",
templateId: "",
accessToken: "",
authHeaderValue: async () => {
return "..."
}
});
{% include "../.gitbook/includes/your-feedback-is-crucial-in....md" %}