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.
This functionality is absolutely critical to make FE NXT viable.
We must have this function available in FE NXT before we are made to completely transition away from the database.
If this functionality is not added to FE NXT, we would switch SW providers.
We must have this function available in FE NXT before we are made to completely transition away from the database. We use the CSV file import function in the database daily. The Excel add-in function does meet our needs. It is too time consuming and requires too much hands-on manipulation to get financial data into the FE NXT system.
Need this ASAP
We must have this function available in FE NXT before we are made to completely transition away from the database. We use the CSV file import function in the database daily. The Excel add-in function does meet our needs. It is too time consuming and requires too much hands-on manipulation to get financial data into the FE NXT system.
**Update for those following or new to this thread**
I received an automated email from "Blackbaud Financial Edge NXT Ideas" yesterday evening (05/07/2024 at 7:17pm MST) stating the status of this idea has been changed to "Planned."
Here's to hoping this issue is moved to "In Progress" or "Implemented" sooner than later.
100% agree and new Webview is not working with import functions. Blackbaud cannot force customer to transition to Webview without a solution on Webview import GL posting functions.
FYI, in looking at the time stamps, the original poster submitted their idea on 10/26/2018.
The comments prior to me date back to 02/14/2023, 10/30/2023, and 03/13/2024.
I see that 57 votes as of today (05/07/2024) have been submitted under this thread and the status of this comment has been labeled for "Future Consideration."
It is concerning that this has issue has remained present for almost 6 years and still no solution has been provided. At the very least, this issue should be escalated and the status updated to "Planned" or "In Progress."
Our concerns should not be held from further review any longer.
I completely agree with everything stated by the original poster and others in the comments section; the "Journal Entry Batch Creator Excel Add-In" is extremely limiting. The connectivity issues create a huge obstacle that hinders efficiency within our operation and increases the risk for accounting discrepancies.
In addition to the original poster's concerns, I would like to add that I find it a troublesome problem that the JEBC Excel Add-In will only import data into a new batch. There is no feature within the JEBC Excel Add-In to designate the data to be imported to an already existing batch in FENXT.
I spoke with a chat agent from Blackbaud Support today (05/07/2024 Case #: 019715647) who confirmed that this capability is not available with the JEBC Excel Add-In. When I inquired about alternative options for when the Database view is phased out, the representative stated, "Currently the Excel add-in is the only way to import in FENXT. I would continue to import in database view if importing into existing batches for now, and I would assume this functionality would be brought to FENXT at a later date when everything is moved over. I'm afraid I don't have an official ETA to provide for that but lots of changes are still yet to be implemented in NXT."
It would be much more efficient to have a built-in import feature within the web-based FENXT interface that also allows the import of data into an existing journal entry batch.
It is very obvious from the comments here in the Support Ideas Bank and from viewers' comments during the Live Webinars that proper solutions for import functions be prioritized by the development team and implemented in the near future if customers are to be forced to transition to the web-based FENXT.
This is No. 1 priority. without the import function, we will not be able to do our accounting posting. i.e. payroll, grant reporting and many others. Current webview didn't work.
This is a crucial functionality. The Excel add in does not meet the requirements needed for me to import large CSV files. I was advised to continue to use the database view. This needs to be resolved before it is is no longer accessibly in the database view.
Agree with everything noted here, but in addition, in database view I can assign different ledgers to identify what type of entry the data is for, i.e. payroll, investments, contributions and need similar functionality here. In the current version it only allows "journall entry as the type. Also, in database-view I can add to existing entries via import by identifying the journal entry # in a separate column.