Message from MS support regarding this issue:
Since there isn’t a destination column for this field to go to the data is not transferred. It is similar on how the COMMENT field functions on the line. Once posted the COMMENT field is gone since there is no historical/archive column for that field. You could create an extension to have that field retain the value while it moves to history. So I think the extension would need to be on the Gen Ledger Entries table to add a custom field and populate it based on what is in the Transaction information column. That is what I had another Partner do with the Comment field.
Comments
Agree. This is borderline insanity.
Category: Financial Management
I agree, because if we need to add information on a journal entry, there is no way to drill down to the transaction after the posting to see those comment field information and Transaction information.
Category: Financial Management
This is what I came looking for. This needs to be added to the Gen Ledger Entries table. It is crazy to me that you have fields in an unposted transaction that you can add data to, but you can't report on that data after posting.
Category: Financial Management
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future.
Best regards,
Business Central Team