Journal Posting Customization

(0) Share

Report

Posted on by Tony zhong

903

Hi guys,

May I know when we posting journal, either it is General Journal / Payment / Project Journal, what is the preferred customization if I want to extend the process ?

The idea is I customized one of it's related table: LedgerJournalTrans_Project with some additional field, and I need to update this custom field to have some info whenever the LedgerJournalTable is Posted.

Should I have an extension class for the table's ModifiedFields method ? or there is already a certain class for posting that it is better for me to extend from it ?

And can I ask which class or something for my reference in regards to my previous question ?

Thanks in advance.

All responses (6)

Answers (1)

Sort by

André Arnaud de Cal... 307,271 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

Hi Tony,

Can you explain the exact business requirement? In what table(s) do you need to copy the additional information at time of posting?
Tony zhong 903 on at

Like (0)

Report
Copy link

Link copied!

Hi Andre,

It is to LedgerJournalTrans_Project. So the requirement is to update my custom field in that table, which is same info, Posted. I need this info for Dual-Write procedure in my Dataverse, as the table over there is the lines only. So when LedgerJournalTable in F&O posted (field Posted changed to "Yes"), Dual-write will synchronize this LedgerJournalTrans_Project's Posted field (custom) to Dataverse.

So basically it will also need to loop for how many records related to the same Journal with Type:Project.

Thanks
Verified answer

André Arnaud de Cal... 307,271 Super User 2026 Season 2 on at

Like (1)

Report
Copy link

Link copied!

Hi Tony,

I wonder if you are looking at the correct integration strategy here. Posted journals can be deleted with a cleanup job. If so, dual write will also delete the information in Dataverse. Is this the intention?

If you are using a data entity now for the Dataverse integration, then probably you don't need to duplicate the Posted field to the table LedgerJournalTrans_Posted as you can also include a calculated field.
Tony zhong 903 on at

Like (0)

Report
Copy link

Link copied!
Hi Andre,

Thanks for your advices. I believe I so caught up with the Dual-Write mapping and updating each other and forget that this is all about Data Entity as well. Yes, I think you're right, there is no need to have custom field and some update classes. I should only need to create calculated field for the Posted field from LedgerJournalTable. I could even just drag the Posted field from its datasource since it is already being there all this time.

But for broaden my knowledge, what's the different between create calculated field and just drag the field from the Datasource ? since I noticed also in standard entity like SalesInvoiceLineV3Entity ->

As you can see they create a calculated column for LineTotalTaxAmount, but inside it is only returning field value instead some further calculation ->

private static str invoiceLineTotalTaxAmount() { return SysComputedColumn::returnField( tableStr(SalesInvoiceLineV3Entity), identifierStr(CustInvoiceTransLineTaxAmountView), fieldStr(CustInvoiceTransLineTaxAmountView, LineTaxAmount)); }

Is it for Read only so it will not directly goes to the field ? can we just drag the field from datasource and make the field AllowEdit to No ? this is just for me to have better understanding.

Many thanks again.
André Arnaud de Cal... 307,271 Super User 2026 Season 2 on at

Like (1)

Report
Copy link

Link copied!

When the table with the Posted field is already available in the data entity, then yes, you can use this one instead of a calculated column. It can be either one of the two options.
Tony zhong 903 on at

Like (1)

Report
Copy link

Link copied!

Hi Andre,

Many Thanks for directed me to the correct way.

Solved!