Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-08-06 17:36:53 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
bcquality/custom/knowledge/patterns/cmfrt-interface-injection.md
BeytullahCengiz88 afb1fa2883 Add CMFRT naming conventions, object ID ranges, and patterns documentation 
- Introduced guidelines for using the "CMFRT" prefix in object names, fields, and procedures to avoid naming collisions and ensure clarity.
- Established rules for object ID ranges to prevent conflicts with other extensions and maintain historical integrity.
- Documented best practices and anti-patterns for various coding patterns, including case statements, interface injection, label usage, and validation methods.
- Implemented a standards review skill to evaluate AL source changes against CMFRT company standards, ensuring compliance with naming, permissions, and architectural patterns.
2026-07-14 14:09:04 +02:00

1.9 KiB
Raw Blame History

bc-version domain keywords technologies countries application-area
all
patterns
interface
injection
extensibility
implementation
handled
on-before
pluggable
override
al
w1
all

CMFRT interface injection pattern

Description

The CMFRT interface injection pattern makes any table-level operation pluggable by dependent extensions using a four-step structure. Step 1: define an AL interface with a single procedure matching the operation's signature. Step 2: add a parameterless entry-point procedure on the base table that instantiates the default implementation codeunit, fires an OnBefore integration event with var Handled: Boolean, exits early if Handled is true, and otherwise calls the overloaded form in Step 3. Step 3: add an overloaded procedure on the same table that accepts the interface as a parameter and delegates to it. Step 4: declare the [IntegrationEvent(false, false)] OnBefore event as a local procedure passing var Handled: Boolean. Dependent extensions subscribe to OnBefore, set Handled := true, and call the overloaded procedure with their own implementation codeunit.

Best Practice

Apply this pattern whenever a calculation or operation might need different behaviour in different customer deployments. The separation between the parameterless entry-point and the interface-accepting overload means a subscriber can inject an alternative implementation without modifying the base table. The default implementation remains the fallback for all extensions that do not subscribe.

See sample: cmfrt-interface-injection.good.al.

Anti Pattern

Placing the entire implementation directly inside the entry-point procedure with no interface and no OnBefore event. Monolithic entry points cannot be overridden by a subscriber without an AL override pattern, which is a breaking change for the overriding extension every time the base procedure is updated.

See sample: cmfrt-interface-injection.bad.al.