#ZOHO CREATOR ERROR WHEN IMPORTING DATA HOW TO#

Perhaps the subsidiary field values reference “Internal ID”, but the CSV import mapping instead references “Name”.

if a vendor record has External ID “EXTID_1234” (which would be a poor choice for an External ID value) then a corresponding customer record in the same NetSuite environment cannot have the same reference.Īnother common use case is where the format of the field values in the CSV import file does not match those expected by NetSuite. Entity records, transaction records and others must have unique External ID field values within those record types, i.e. This is another common CSV import error, especially in NetSuite environments that make use of the External ID field. The External ID must be unique for transaction records in the system so that NetSuite will group transaction lines with the same External ID when imported. when creating sales order records with multiple lines). Use the External ID field to group lines in CSV imports that belong to the same record (e.g. That said, it is still a useful system validation feature that helps avoid the inadvertent creation of duplicate records in the system. This error will typically occur when NetSuite thinks the user is trying to create duplicate records (even when that is not the user’s intention). Ensure that the entity record reference matches the NetSuite format. Review currency values to ensure they are appropriate for the entity records selected.

Prior to completing any CSV import, perform a spot check of entity records to ensure they are active in the system. If importing a transaction via CSV import, any corresponding entity records (customer/vendor/employee) that do not have access to the currency referenced in the CSV import file will receive a similar error message: “Invalid currency reference key…”. Another example is that of missing currency values set on a given entity record. For example, if a user attempts to create a journal entry via CSV import but does not have access to all subsidiaries referenced in the CSV import file, they will receive this error message. This error often relates to permission deficiencies-not NetSuite role permission deficiencies, but user/record access ones. Salto Suite Tip: Users need the role permission “Import CSV File” in order to process their own CSV imports (for records they have access to).

#ZOHO CREATOR ERROR WHEN IMPORTING DATA HOW TO#

While the scope of NetSuite CSV import errors is very broad, we will look at 7 specific error examples and how to solve them. In fact, there are many use cases where errors “stack up” and can therefore only be resolved sequentially, one after the other. This could result from data being formatted incorrectly in the CSV file itself or could perhaps stem from an inactive record in the system that is referenced in the CSV file.Īnother challenge faced by NetSuite professionals is that resolving one CSV import error will not necessarily solve the root cause of the problem. However, it is inevitable that CSV import errors will occur.

“0 of X records imported successfully” is not something a NetSuite administrator or developer wants to see when working with the system. For example, when performing a NetSuite sandbox refresh, you can perform a quick CSV import to re-upload the users/roles and grant them access in a matter of minutes. NetSuite CSV imports are essential for processing large volumes of new records and updating existing records.

Zoho creator error when importing data