Does Import CSV to Database v6 work for csv file with null values?

The best approach is definitely to verify the database schema, as Srinivas mentioned. If the columns are defined as NOT NULL, then inserting null or empty values will cause SQL errors — which seems to be exactly what's happening in your case.

If modifying the database to allow nulls is not an option, there is a workaround:

You can use the readcsvlog() function to read the CSV file into a CDT. Once the data is loaded, you can loop through the CDT in Appian, check for null or empty values, and replace them with default values (e.g., "N/A" for text, 0 for numbers). After that, you can insert the cleaned data into the database using Write to Data Store Entity.

However, this workaround is significantly more complex and less efficient than simply updating the database schema to allow nulls in the appropriate columns. If possible, adjusting the DB structure is the cleaner and more maintainable solution

readcsvlog() function only allows to read from log files. We won't be able to read from csv document.

You're absolutely right — I responded too quickly without thinking it through.

The readcsvlog() function is specifically designed to read log files, not general CSV documents. It only works with the application server log files, not with user-uploaded CSV files stored as Appian documents.

Thanks for pointing that out! I appreciate the clarification.

As an alternative, you could try using the previewCSVForImport() function from the Excel Tools plugin. It allows you to read CSV documents uploaded to Appian. Example:

previewCSVForImport(
  document: todocument(ri!csvFile),
  delimiter: ";",
  charset: "UTF-8",
  numberOfRows: 1000
)

As an alternative, you could try using the previewCSVForImport() function from the Excel Tools plugin. It allows you to read CSV documents uploaded to Appian. Example:

previewCSVForImport(
  document: todocument(ri!csvFile),
  delimiter: ";",
  charset: "UTF-8",
  numberOfRows: 1000
)