Blackbaud personnel---take note! This is not the only idea on this topic. Danielle Pride created the same Idea in 2024, and it has 66 votes as of this morning. Combined with this Idea, that's over 100 votes on this topic.

Yes, the absence of this function is certainly a step back. Some RE uploads into FE can have hundreds of lines. The loss of this function adds not only additional effort to make changes to the journal entry fields, but increases the possibility of errors since the uploaded entry is now having to be manually manipulated.

Karen's comment is spot on.

Karen Raybuck's comment of: "Not having this in the Journal Entry screen is a step back in functionality. Having to create an import file is creating extra work."

Similar to the proposed Smart Import Hub, where you can make corrections on the fly (which also occurs in processing automated batches in RE NXT)-what used to be called the Global Change Function has gone away. Now we have to use the import function. That requires to upload a batch from RE into FE, copy that batch into Excel and make the changes needed, import the batch back into FE as a journal entry, and finally delete the original uploaded journal entry in FE. In database view, we could have chosen to globally change a field such as Journal Reference, type my changes in, and apply those changes to the entire field with one click.

Should I choose not to export the journal entry to Excel, I need to copy whatever changes I make to each cell of the journal entry and paste it into each. Our imported batches from RE can have over 400 lines, so I only do this on entries up to 60 or so lines, but this is time consuming and ripe for errors.

I would like to see the global change feature from database view incorporated into NXT. We used to have global change, and it needs to return.

Before seeing the existence of this, I created a similar idea, just with more detail, under Receivables. I created that idea today, 11/20/2025. Whether my idea with more detail, or this idea, let's see if we can get more votes generated for this. The current import method is very cumbersome.

I use this feature after Allocations generates a journal batch. Allocations is very limited and when custom fields need to be entered, I now have to go to each individual line item in the batch. Before the switch, this was much more efficient using the global change feature in database.

Not having this in the Journal Entry screen is a step back in functionality. Having to create an import file is creating extra work.

I came here to say the same thing. I use global change frequently in ways that an update won't address. It saves a lot of time.

This is a very time saving function.