Add integration events to codeunit 50100 SDFileMgt#2
Draft
Conversation
Co-authored-by: demiliani <33155438+demiliani@users.noreply.github.com>
Co-authored-by: demiliani <33155438+demiliani@users.noreply.github.com>
Co-authored-by: demiliani <33155438+demiliani@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add integration events to codeunit 50100
Add integration events to codeunit 50100 SDFileMgt
May 19, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds integration events to codeunit 50100 SDFileMgt to support integrations from dependent extensions.
For each procedure in the codeunit, I've added appropriate
OnBeforeandOnAfterintegration events with the[IntegrationEvent(false, false)]attribute. These integration points allow dependent extensions to hook into the file management operations without modifying the base code.The integration events follow a consistent pattern:
OnBefore[ProcedureName]- Triggered at the beginning of each procedureOnAfter[ProcedureName]- Triggered after the procedure's main operations are completedEach event includes relevant parameters that subscribers might need:
Added integration events for the following procedures:
Example usage from a dependent extension:
Fixes #1.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.