For example, upload a CSV file in FE NXT web-view, map fields to columns, then click import.
Our company currently oversees six different FE NXT databases and is looking to implement more. We are heavily dependent on spreadsheet imports and built our processes around database-view's import functionality before migrating to FE NXT. The Excel add-ins are good in theory, but we found them inefficient and ineffective in a multi-database and high-variable environment. For example, we must log out and log back into the Excel add-in every time we perform an import (i.e., even within the same company), completely remap the spreadsheet to the add-in table, wait for the spreadsheet to connect to FE NXT, delete blank table rows or add new table rows (i.e., if the Journal Entry exceeds 999 rows), add a batch description, click submit, and hope there are no errors. Errors usually have nothing to do with data entry. Rather, errors occur in the add-in's ability to connect to the FE database. The only way we've found to resolve these connection issues is to sign out of the Excel add-in, delete the "New Journal Entry Batch" worksheet, save the file, and start the mapping process over. After four months of trying to use the Excel add-in, we are returning to solely using the database-view import function.