Finance | Project Operations, Human Resources, ...

Import data using LedgerJournalEntity

(0) Share

Report

Posted on by Dev

451

Hi All,

I have a requirement where I need to populate the terms of payment in genereal journal using LedgerJournalEntity.

I have tried using UpdateEntityDatasource to update the LedgerJournalTrans table directly with the customers terms of payment but this is not getting called along with some more methods.

As this field LedgerJournalTrans.Payment is not a part of entity so I cannot explicitly set its value in postGetStagingData. Can you please suggest how to populate this.

Even extending and adding the field is not helping.

Thanks!

I have the same question (0)

All responses (7)

Answers (0)

Sort by

Martin Dráb 239,118 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!
Which type of journal are you trying to import?

The field already available in several entities, such as:

CustInvoiceJournalLineEntity

CustomerPaymentJournalLineEntity

ExpenseJournalLineEntity

VendInvoiceRegisterLineV2Entity

VendorPaymentJournalLineEntity

Was this reply helpful? Yes No
Dev 451 on at

Like (0)

Report
Copy link

Link copied!

I am trying to import general journal.

Was this reply helpful? Yes No
Suggested answer

Martin Dráb 239,118 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

If it makes sense from business point-of-view (although Microsoft didn't think that), simply add the field to the entity through an extension. There is no need to write any code, either in updateEntityDatasource() or postGetStagingData().

Was this reply helpful? Yes No
Dev 451 on at

Like (0)

Report
Copy link

Link copied!

I have tried that too but the record is not updating.

I have added a field in extension and mapped that field to LedgerJournalTrans.Payment . In the extension class for LedgerJournalEntity in postGetStagingData I have written below code to get terms of payment for that customer

ledgerJournalEntityStaging.TermsOfPayment = custTable.PaymTermId;

I have regenerated mapping the synchronized everything but this value is not reflecting in new general journal although the customer has this setup.

There is a method copyCustomStagingToTarget do we need to make any modification here.

Was this reply helpful? Yes No
Martin Dráb 239,118 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

I thought you wanted to import the value, but now I see you're tryting to populate it from CustTable. Can you clarify what you're trying to achieve, please?

In either case, postGetStagingData() is a bad place for it. copyCustomStagingToTarget() is not related to any of those requirements either.

Was this reply helpful? Yes No
Dev 451 on at

Like (0)

Report
Copy link

Link copied!

So I have an xml with details of customer and other details for general journal lines that I want to import. When importing I am fetching the terms of payment from the customer mentioned in the xml and trying to populate its value in the general journal. For all the existing fields in the standard entity I am writing logic to modify the values based on our requirement in the postGetStagingData() and they are working fine but for this newly added field in the extension I am unable to get the value although while debugging i can see that at this stage the value is populating in the staging but doesn't make it to the target table.

Was this reply helpful? Yes No
Martin Dráb 239,118 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

I'm confused. You said thay you want to fetch the data from a customer, which means that you don't want to get it from outside. But you're also talking about "a newly added field in extension". If you want to intitialize the value from customer, you don't need any new field in entity extension, do you? You would need that if you wanted to import the value from a file, but then you wouldn't be taken the value from a customer.

I looked into CDE repository at the implementation of LergerJournalEntity and I see that you're right - the logic there is heavily based on manipulating staging table and using custom copy-to-target logic. It's not usual, but Microsoft did it here for performance reasons.

I guess that the right place for your logic are methods createJournalLines() and updateExistingJournalLines(), but I'll look at it in more detail on Monday.

Was this reply helpful? Yes No