Skip to main content
Question

Custom Field Value not Readable in Event before Transaction complete?

  • June 6, 2024
  • 1 reply
  • 36 views

haritha.waidyaratne
Sidekick
Forum|alt.badge.img+5

Hi,

I have designed two events, one each for this window’s LU and that for its parent. But, when a parent’s entry is created, a default entry is created by the business logic on this window as well. Anyway, when that happens, the event designed for this window is not meant to fire and generate an email, which is only expected when data on this window is manually entered.

For this purpose, I have introduced a custom field (which will be made invisible), which is highlighted below -
 


The problem here is that, although the value is correctly set at the end, its value is not successfully readable in the event during the transaction (autonomous transaction didn’t work either), as in the below:
 


 Note: Address type code is a key value used to identify creation of a new object.

Thank you.

1 reply

Forum|alt.badge.img+10
  • Hero (Partner)
  • 118 replies
  • June 6, 2024

The insert into the custom field table happens after the insert into the core table, so I don’t think that custom field will help you.

Question for anyone else who’s viewing this: Has anyone fired off an e-mail from a Workflow?

If so, that could be an option, because the Workflow can fire on selected projection actions (like manually Create on address type) rather than backend table inserts.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings