Hello, everyone!
Can you explain, what is the great purpose for next methods:
mapEntityToDataSource
updateEntityDataSource
mapDataSourceToEntity
In the context of Import job?
Thank you!
It depends on what exactly you mean by that. Please create a new thread and explain your actual problem in detail there.
In general, mapDataSourceToEntity() isn't applicable if you're talking about data import. And updateEntityDataSource() may not be applicable if you're interested just in inserts and not updates (which is unfortunately not completely clear from your description).
Yes.
Hi Mark,
didn't you already ask the same question here, and mark the answer as verified?
One of these three will accomplish the requirement of "allows override of data after it has been inserted into target entity?
Ahmed, please look at Data entities overview. If you have more questions, please create your own thread with an appropriate title and tags.
What is definition of data entity ?
is it classes that responsible of export and import
Hi Saurabh,
Did you tried 'mapEntityToDataSource' method as Martin suggested, you should be able to write your business logic based on imported values in this method.
there is another method postTargetProcess(), both serves the same purpose? any pros and cons?
postLoad() is called after fetching data from database, which doesn't look useful in this case.
mapEntityToDataSource() sounds like a more appropriate place for the business logic. You can find examples in standard entities. For instance, CustCustomerEntity uses mapEntityToDataSource() to fill in MainContactWorker based on the value of EmployeeResponsibleNumber.
Try PostLoad method
#1
André Arnaud de Cal...
292,884
Super User 2025 Season 1
#2
Martin Dráb
231,754
Most Valuable Professional
#3
nmaenpaa
101,156
Moderator
Share
Report
All responses (
Answers (
