Skip to main content

Hi all,

I have a Generic Inquiry which triggers a business event on “Record Inserted”.

The point of this is to trigger a downstream process when a new Customer Location is inserted (from AR303020 let’s say). This works in principle, however we’re finding the following issue:

If a user enters anything other than basic information on the location record, let’s say someone picks from a user defined field or some other association; when we’re consuming the data in our custom business event subscriber, The locationID key field from the Location table is being passed through as zero. If the user just fills in basic information then the correct new id for the Location is passed.

It’s as if the event is being kicked off before the Location record has been persisted to the database.

We have a number of joins on the Generic Inquiry so in theory I guess it is data being persisted in those tables that is triggering the event too early (for our needs).

Can anyone shed any light on this behaviour? We need to try and keep the joins we have in the GI as we use that data in a downstream process. Is there a way to configure the Business Event to trigger later, or once all records for that operation have persisted?

Many thanks.

There seems to have been an issue in 2019 R1 as seen here that affected the GI, BE and Location table combination:

AC-132393: A business event triggered by a record change was not triggered if the Location table was used in a generic inquiry linked to this event.

Could this be related in any way? 


We are using 2022 R2


For the moment we’re moving away from using the LocationID to using the LocationCD as this seems to be generated in time for the business event and should be unique


Reply