Add the appropriate Insight code changes to the codeunit design. Carefully editing codeunit 414 can preserve any changes that have already been made to it.
The file COD414.txt resides in the NAS working directory subfolder that holds the Dynamics NAV localization, database version, and build, for example: ..\Microsoft Dynamics NAV\90\Service\Add-Ins\Scribe\ScribeModifications\W1.9.00.42815.
To edit the codeunit, use the .txt file that matches your version of Dynamics NAV. TIBCO suggests that you review COD414.txt before editing codeunit 414.
To edit codeunit 414
Name | DataType | Subtype | Length |
---|---|---|---|
ScribePublisher | Codeunit | Scribe Publisher | |
RecRef | RecordRef | ||
xRecRef | RecordRef |
After:
IF Status = Status::Released THEN EXIT;
Add:
// ***** SCRIBE BEGINS *****
// Get the RecordRef of the original record
xRecRef.GETTABLE(Rec);
// ***** SCRIBE ENDS *****
Add:
// ***** SCRIBE BEGINS *****
// Trigger the Scribe Publisher
RecRef.GETTABLE(Rec);
ScribePublisher.PublishModification(RecRef,xRecRef);
// ***** SCRIBE ENDS *****
Name | DataType | Subtype | Length |
---|---|---|---|
ScribePublisher | Codeunit | Scribe Publisher | |
RecRef | RecordRef | ||
xRecRef | RecordRef |
After:
IF Status = Status::Open THEN EXIT;
Add:
// ***** SCRIBE BEGINS *****
// Get RecordRef of the original record
xRecRef.GETTABLE(SalesHeader);
// ***** SCRIBE ENDS *****
After:
WhseSalesRelease.Reopen(SalesHeader);
Add:
// ***** SCRIBE BEGINS *****
RecRef.GETTABLE(SalesHeader);
ScribePublisher.PublishModification(RecRef,xRecRef);
// ***** SCRIBE ENDS *****
Make a note of the codeunit's new revision level.
Note: In the Object Designer, in the Version List column, edit the Release Sales Document codeunit's version to reflect the new revision level.
See also
Editing the codeunits — Dynamics NAV 2016