Adding new field in GL tables and upating data while financial transactions posting

Hi Team,

We have below requirement:

We need to add new field Customer posting layer (CustSpecificPostingLayer) in GeneralJournalEntry and GeneralJournalAccountEntry table for reporting purpose.

This needs to updated while posting all financial transactions such as sales invoice, purchase invoice, GL journals, fixed asset..etc.

We are using UDE for development purpose as our project using Power platform admin center.

I’ve modified LedgerVoucherObject and LedgerVoucheroTransObject classes and added x++ code. while debugging looks like data coming but it not reflecting in tables at the end. believe something here missing.

Also written coc for insert,update methods of GeneralJournalEntry and GeneralJournalAccountEntry tables but debugger is not hitting.

Really appreciate if someone assist on this. explained requirement in detail below.

Detail explanation as below:

Custom field data mapping: Created new setup map which will have mapping of standard posting layer with customer specific posting layer. find below screenshot for example

We have aleady PostingLayer in GeneralJournalEntry table. While inserting data in same table we need to update the custom field CustSpecificPostingLayer with relevant data based on setup for both GeneralJournalEntry and GeneralJournalAccountEntry tables.

For example: If GeneralJournalEntry table having standard field ‘Posting Layer (CurrentOperationTax is the Table field name)’ has value customer layer1. then custom field ‘CustSpecificPostingLayer’ will have Cus_FR as per the setup form shown above in GeneralJournalEntry table.

Also for same in GeneralJournalAccountEntry table comparing data in GeneralJournalEntry table.

I will really appreciate on this if anyone came across this complex requirement and guide here on this.. Many thanks.

To add a new field to Journal and you want the data to be in posted tables. (Entry tables). First thing to do is to create or include in an Extension for for all Related Entry tables the field for the information you needed. The logic is that you should maintain the same field no. Throughout in all related Entry tables. So that anywhere the in the process where transfixed function is called all your addition info will be transfer along.

I hope this is clear.