Application Event Handler IdoOnItemInsert not firing

How do you trigger the IdoOnltemInsert event?

I've added a new Event Handler on the IdoOnItemInsert event but I'm having trouble with the event not firing as expected. As far as I'm aware, this should trigger whenever a new record is added into an IDO, isn't it? I apply this handler only to SLLots so when a new lot is saved I'm expecting that my event handler should trigger but nothing happens. I've checked my Event Handler Status and Event Status and there are no entries for this event.

I have another Event Handler attached to the IdoOnItemUpdate event and that triggers whenever we update an IDO collection as expected. Why wouldn't the IdoOnItemInsert not trigger?

These are the properties of the event handler:

Event Name: IdoOnltemInsert
Handler Description: Set Exp Date for Lots
Sequence: 9
Applies To Initiators:
Applies To Objects: SLLots
Applies To Sites:
Chronology:
Keep With:

Access As:
Purpose:
Triggering Property:
Method To Call:
Initial State:
Initial Action:

Active: True
Can Override: True
Ignore Failure: False
Suspend: False
Obsolete: False
Synchronous: True
Transactional: True

Any insights on why this event wouldn't fire when we save a new Lot?

Find more posts tagged with

General Discussions

Accepted answers

All comments

Rees Howel

How is your new Lot being created?

If you are entering it manually through the Lots form, your event should trigger.

If it is being created from PO Receipt or Job Receipt then the chances are the Lot is inserted via SQL which bypasses the IDO and thereby your Event Handler.

jarod_m

My test was done using the Lots form so it's weird that it's not firing. However, in real time scenarios they can also be created through other forms so maybe this approach isn't the way to go.

I assumed that the IdoOnItemInsert would fire even if it was created through another form but it sounds like that's not the case? Unfortunately I can't confirm because it's not firing in either scenario.

So my objective is to set a specific default expiration date on new lots where the lot code matches a specific text pattern (ie. "*-XXX"). We are using an on prem version but I am avoiding using DB triggers since we plan to migrate to the cloud and I don't know if that will still be available. We also have an integration of Infor Factory Track to Syteline/CSI so it's possible that lots could be created from there as well.

Are there any other ways I could cover all of these scenarios?

unknown

I have been working on a similar issue. I'm not much of a programmer, but I am an experienced user, so it took me a while to understand how the event system wants to operate (and veterans please correct anything I'm saying that isn't totally true.

Most events are really monitoring for human changes to the system from the front-end, or triggered on a schedule from the Event Triggers form. When the system updates SQL tables directly due to background programming, it's a different kind of action than an "event". So if a user changes a field and saves, that's an event the system can see through AES and respond to. But if a trigger fires and changes SQL detail on a related table, that isn't something AES can see directly. I'm sure that's obvious for seasoned users and folks with a CS background, but it wasn't for me.

There are ways to get around this. I just built (with a lot of help) a tool that runs a filter on the SLPoItems IDO every 10 minutes and looks for records with a record date within the last 10 minutes, then fires an e-mail with those records to a distribution list in an HTML email (if any exist). But I had to set a timed trigger to make that happen, because it needs some kind of signal to react to. I would presume you could program a similar trigger to fire your event if it sees activity on that IDO.

Anyway, I'm writing that out for you and anybody else who's just learning AES. That one was an aha moment for me.

0712050809193544.doc

Copyright © 2025 Infor. All rights reserved.