OnCustomProcessing in CU1380, Batch Processing Mgt. about alappextensions HOT 3 CLOSED

Hi,

I will pass your feedback on the relevant team.

A few comments:

• whether MS uses events or not should not matter. Any extension could do the same and you would know even less about what is going on (you can't see their code at all). When using events you have to design for multiple subscribers and make sure your code runs properly regardless of order or what others do. The handled pattern has the problem that when used properly, only the first subscriber gets to execute but no-one knows what that is. If used improperly, multiple subscribers will run their code and the results may be unpredictable or result in error (like try and post the same doc twice using different codeunits?)
• In this particular case, if you don't want the MS subscriber to handle the processing of SalesHeaders you can turn off "Post with Job Queue" in Sales & Receivables Setup. You'll then be able to handle this yourself.

br/Gert

from alappextensions.

Hi @renebrummel,

You mentioned three events of COD1380 that are considered to be "internal". If you say you want to subscribe to these events, where COD1371 or COD1372 are manually bind to, then you trying to get into the internals of the mechanism supporting this whole functionality.
In order to help you we need more details about a scenario you want to implement.
The options will be:

• we add events to COD1371/1372 so you can customize sales/purchase posting.
• we suggest you to create a new codeunit similar to COD1371/1372 where you implement you very special handling.

Best regards,
Stan.

from alappextensions.

This issue seems to have been resolved. Closing issue.

from alappextensions.