[Event Request] table 179 Reversal Entry InsertFromEmplLedgerEntry

[PauliusPocius]

Why do you need this change?

Allow reversal in specific cases

Describe the request

Hello, is it possible to extend the procedure InsertFromEmplLedgerEntry by adding an event OnInsertFromEmployeeLedgEntryOnBeforeCheckSameTransaction, similar to the events available in InsertFromCustLedgEntry (OnInsertFromCustLedgEntryOnBeforeCheckSameTransaction) and InsertFromVendLedgEntry (OnInsertFromVendLedgEntryOnBeforeCheckSameTransaction)?

[AleksandricMarko]

Hi @PauliusPocius,

Thanks for submitting this extensibility request. To help us process it efficiently, please update the issue to include the required information.

📚 Extensibility Guidelines

Missing Information:

• Meaningful Justification: "Allow reversal in specific cases" is too vague. Please describe which specific cases require a different reversal behavior and why the standard CheckSameTransaction logic is insufficient. Include a concrete business scenario or technical limitation you are encountering.

• Proposed Code Change: Please provide the exact code addition showing the event declaration and invocation with 5-10 lines of surrounding context from Table 179 "Reversal Entry", procedure InsertFromEmplLedgerEntry.

• Alternatives Evaluated: Please explain which existing events or patterns you tried and why they are insufficient for your scenario. Referencing similar events for Customer/Vendor is helpful context, but please also describe what alternatives you considered.

• Justification for IsHandled: Since this event would allow bypassing the CheckSameTransaction validation, please explain why a standard event (without bypass capability) would not be sufficient, and what specific business logic within the check needs to be skippable.

• Performance Considerations: Please briefly describe expected execution frequency and potential impact (e.g., "Runs only during reversal posting, so impact should be minimal").

• Data Sensitivity Review: Please confirm whether sensitive data is involved (e.g., "No sensitive data involved" is sufficient).

• Multi-Extension Interaction: Please briefly acknowledge whether you see conflict risks if multiple extensions subscribe (e.g., "No major conflict expected; subscriber will only add logic").

Please update the issue with the missing details. We'll automatically re-analyze once updated.