Hi everybody. I'm having a similar problem. [Similar to AX7 Extension / Overlayering: New specific extension field and initialize.]
I created a field in a form (PriceDiscAdm)
When the field is filled with a value, the related datasource is populated and the underlying table (PriceDiscAdmTrans) gets correctly updated.
The posting process for the journal anyway proceeds to update another table (PriceDiscTable).
This latter gets populated via a system class (PriceDiscAdmCheckPost) which in turn extends the RunBaseBatch, information being taken from the previous table (PriceDiscAdmTable).
Now to the point: to extend such behavior with my new field I tried to implement right the logic you are describing.
The handler your are suggesting to build needs to be aware of the caller though.
Too bad that the method preceding the handler in this case is static, which makes impossible to get the caller.
So the question is: does a workaround exists for the such a case?
As an aside, more generally speaking: if this is the standard logic suggested by Microsoft it seems a bit debatable (don’t get me wrong: I am not flaming, just trying to understand) since
1) the new field will be updated out of the first transaction updating the other fields
2) each time I have to access the DB twice
3) Isn't there a simpler way to integrate customizations with the core logic of AX365? Since overlayering does not support the continuous upgradability model Microsoft envisions for the product?