The requirement was to add an additional address type based on the global address table to the sales order tables.
I made this similar to a delivery address by adding a additional relation to LogisticsPostallAddress. Everything works very well and as required. The challenge now is to make it possible to import the additional address through the standard data entity SalesOrderHeaderV3.
Does anyone have any experience or suggestions on how to try to solve this problem? What data entity methods are key here?
If I was you, I would try to convince them to use a separate entity for the other address rather than trying to put everything into SalesOrderHeaderV3Entity.
But if you want, pay attention to how the delivery address is handled, rather then trying to design the whole thing on your own. First of all, notice that it uses LogisticsPostalAddressBaseEntity. You miss all the logic of LogisticsPostalAddressBaseEntity by trying to use LogisticsPostallAddress directly.
Then look at how it's used, e.g. notice relevant code in findEntityDataSource(), insertEntityDataSource() and a few other places.
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.