How to trigger AES event from SP in CSI 10 MT Cloud environment?

Looking at alternatives to creating IDO custom assemblies as Infor moves away from extgen Stored Procedures. Does the return of an SP trigger anything in the IDO layer that AES would be able to act upon? For example, we have an extgen whose primary purpose is to grab some UET properties from an estimate and dump them into corresponding UETs on the Customer Order when copied from the 'Copy Order and Estimates' form. How would I copy over the UETs from Estimate to CO using AES?

I would also be interested to hear any criticisms of using AES vs an IDO custom assembly to achieve this goal. Thank you for your time!

Find more posts tagged with

General Discussions

Accepted answers

All comments

Stephen Cena

I'll take a stab at it:) Based on my understanding of your explanation:

In the AES, you would need to trigger on an IDOItemUpdate and then apply additional identifying criteria (ex:Applies to CopyOrderAndEstimates Form). You would then write the instructions in Event Actions. Writing the Handler is a lot like coding in BASIC w line numbers, and your functionality is 'limited'. You can call IDO Methods though.

If you wanted to ditch the AES entirely and do it all inside an IDO Method, you'd need to insert the IDO Method call into the Form to fire when your 'criteria' is met. For example, StdFormSavedComplete or StdFormSave.

I hope that made some kind of sense. I can elaborate more & clarify if need be.

Rees Howel

The problem may be that the Sp does everything below the IDO layer and IDOItemOnInsert doesn't fire when the Estimate is converted to a CO. The quickest way to test is to set up an AES Notification for the creation of a new CO. If you don't get a Notification, all is not lost. An additional step to the form event handler can be added to Generate Application Event which would pass out the Estimate and CO number as parameters.

The Application Event Handler would then be written to do a Load IDO Row to pass your Estimate UET field values to a set of event variables. This would then be followed by an Update Collection action to write the event variables into the CO UETs.

This kind of thing is practical if all your UETs are at the Estimate/CO Header level but it quickly becomes messy if you also need to pass UET at the Estimate/Co Line level. It *can* be achieved with loops, lots of care and your headache pills of choice but I'm not sure it's worth the effort. If Header AND Line fields need to be passed, I'd be inclined to write an IDO Extension Class if SQL is off the table.

chris

ReesH is correct, the IDO layer does not see anything the SP is doing, so an IDOItemUpdate would not trigger. I was hoping there was something at the IDO layer that would see the return of a completed SP or something that I could act upon. I've tested using an application even handler, and it does not fire when an IDO is updated or created by a SP. I'll take a look at the method call idea, but I'm not clear on how I would be able to retrieve variables from what the SP came back with. Sticking with this example, how would I be able to tell the custom IDO method what the new CO number is? Since the New CO number would be determined by the SP.

Thank you for your responses!

Rapid Development of a COVID-19 PPE Inventory Dashboard Set.pdf

BradleyBrown

If possible, why not just emulate what the SP is doing in an IDO method and avoid calling the SP altogether?

Copyright © 2025 Infor. All rights reserved.