Lets get started with nuvo

Welcome! Our FAQ is here to assist you in integrating our nuvo importer into your existing application.

faq banner image

You can invite your coworkers relatively easy. Use the invitation form on the “Home”- or on the “Organization”-page, fill out the required fields and submit it. Now your coworker should have received a mail with which he/she can join your nuvo workspace.

If you want to delete a user from your workspace, you need to go to the “Organization”-page and press the deletion button of the user you want to delete from your workspace.

There are two ways to reset or change your password. If you are not logged in, you can press the “Forgot password?”-button, type in your email address, and you are going to receive a mail with which you can reset your password.

The other option would be if you are logged in to go to the “Settings”-page, click on the “Change”-button of the “Change Password”-section and fill out all fields.

For this, you have to go to the “Settings”-Page, press the “Change”-button of the “Account Details”-section and change the information you want to change.

When you can’t use our importer because of a “License Key is invalid”-error, you need to check two things:
First, if your license key equals the one defined in your account of the nuvo user platform. Second, if the developerMode property is set to true if you are testing the importer in your dev/staging environment and using the “Dev”-key or if the property equals false if you are using the importer in a production environment and therefore using the “Live”-key.

If you want to use the nuvo importer within your production environment and remove the “developer mode”-banner, then you need to change your license key with the “Live”-key, which you can find within your account of the nuvo user platform. You need to set the developerMode prop to false.

You can currently use our nuvo file importer with React, Angular, Vue.js or vanilla JavaScript. When using React, Vue.js or Angular, you can easily install our package via NPM or Yarn. You can load our software library from our CDN, if you prefer plain JavaScript.

We support all React 16.x, 17.x and 18.x versions. You can find more information about all supported versions here.

We support all Angular 12.x, 13.x and 14.x versions. You can find more information about all supported versions here.

We support all Vue.js 2.x & 3.x versions. You can find more information about all supported versions here.

Suppose you want to use our nuvo file importer with NextJS. In that case, you need to create a wrapper React component for the NuvoImporter component because NextJS is normally rendered server-side, and the nuvo importer is rendered client-side. To see how it is done, check out our NextJS documentation.

We recommend deactivating the strict mode to use our nuvo importer with React 18 and NextJS. To do this, please set reactStrictMode to false in next.config.js. Otherwise, complications may arise.

Once you are using the nuvo importer you can build as many target data models as you want. For example, you could create one model for customer data and one for product data. For more details and to get to know all possibilities, you can check out our target data model documentation.

Indeed, it is possible. You can dynamically insert the target data model into the nuvo importer. You need to write just a few lines of code to do that. If you need support, please feel free to reach out to our support team.

There are two solutions for this case: Firstly, you could use your internal wording for the key property and the generic wording for the label property. This results in your users seeing the label and your application working with the internal wording defined in key.

The second solution would be adding all generic words, which would match your internal term, to the alternativeMatches array. The alternativeMatches array contains strings or synonyms of the column from your side, which will also be checked against the imported columns.

Yes, you can. With the columnType property you can easily define whether the target data model column is supposed to be a boolean (“yes/no”-dropdown), a float (number with decimal point), an integer (number), a string (text) or a category column. Columns which are defined as boolean or category will be displayed as dropdowns within the data importing process. For category columns, you can determine the options within the dropdownOptions array.

Yes, there is. With the description property of each column object, you can define a free text which explains your column to your users. Your users can see this text when they hover over the info button of a column. Moreover, you have the option to add an example to each column by its key ​​of the same name. For this, you must also set the property enableExamples to true within the settings object.

With key you can define how your application calls a column, and with label you can determine which column name is shown to your users for each column.

The answer is both. The key, the label and all values of the alternativeMatches array are matched against the imported columns.

We recently launched our multiple file upload, which is limited to five files at a time. To try out the multiple file upload, you need to set the multipleFileUpload prop to true.

Yes, you can add regular expressions, set the column cells to be required or the column values to be unique, and create required dependencies between several columns. To implement that, you can use the validations array, which contains all verification rules. For more details and examples, you can check out our documentation.

Note: We also offer cleaning functions for validating imported data against external data sources, modifying data and creating column cross dependencies. You can find more details below within the “Data Cleaning”-section.

We currently support unlimited file sizes.

Note: Our importer is running entirely on client side. Therefore the performance of the importing process with large files can differ from device to device.

You can adjust every single part of the nuvo importer, and its steps so that our nuvo importer has the same styling as the rest of your application. For styling the importer, you use the style prop. You can receive more information about styling and how to control the style of each part of the application in our style documentation.

Your component can be implemented in different ways. The most common way is to use our button implementation, which after clicking, results in a popup where your users will be guided through our data importing workflow.

If you want to embed our component as a drag and drop area (dropzone) into your application, you can set the embedUploadArea to true, and then your user will see a drag and drop area instead of a button. If you don’t want to guide your users through our workflow within a popup, you can also implement our nuvo importer as a full-page view. For this, you need to set the modal property to false.

Of course, you are able to do that. You can use our column or entry function to fetch data from an external data source, validate it against the imported data and throw an error message if there is a duplicate entry. You could also display an info or a warning. For more information regarding the cleaning functions, visit our cleaning function documentation.

With our cleaning functions, you can edit imported data with ease. You can adjust specific data directly after the mapping or after each change of your user. Herby, you can differentiate if you want to access an entire column or multiple values within a row.

We have implemented some default error messages, but you can also adjust them. When an error occurs due to the rules defined inside the validations array, you can add an errorMessage key to each ValidationObject. If an error appears due to a cleaning function, you can add the specific error message text within the message key.

Yes, after mapping the imported columns to the target data model columns your users are able to press the “Export as Excel”-button to download the merged data as xlsx.-file.

No, your customer’s data is not saved on a nuvo server. Our nuvo importer is implemented within your frontend and runs on client side. Moreover, it only communicates twice with our backend – mainly for verification. Herby, no person-related data is transferred to our backend.

nuvo has no access to your user’s data from the beginning of the import process until its end.

As all your user’s data is processed on your side, we never see or gain access to the data imported with our nuvo importer. That’s why we do not need to sign a data processing agreement with our customers.

nuvo is based in Hamburg, Germany, our servers are hosted on AWS – based in Frankfurt, Germany, and of course, we are GDPR compliant. 

30 minutes video call

Book a chat with the nuvo team

or directly find a suitable timeslot here.