[Event Request] Codeunit 1173 "Document Attachment Mgmt"

[kalozoya-orisha]

Why do you need this change?

We use Azure Blob Storage to store the files in the "Document Attachment" table instead of the database (Media field). To maintain consistency between the recors and the physical path (blob path), we leverega existing events during the copy processes:

• OnCopyAttachmentsForPostedDocsLinesOnAfterSetToTableID
• OnCopyAttachmentsOnAfterSetToDocumentFilters
• OnCopyAttachmentsForPostedDocsOnBeforeToDocumentAttachmentInsert

In those events, we can download the original blob and republish it to ABS, generating a new path that incorporates the new "No." value. However, in the MoveAttachmentsWithinSameRecordType procedure (whhen moving/rename attachments within the same record type by changing the "No."), there is no event before the Insert that allows this. Furthermore, it deletes the original record, causing the blob in ABS to be deleted as well, and the new record continues to reference the same blob path.

Describe the request

Proposed event:
Name: OnMoveAttachmentsWithinSameRecordTypeOnBeforeInsert

Parameters:

• var DocumentAttachmentToCreate: Record "Document Attachment"
• MoveToRecRef: RecordRef
• MoveToRecNo: Code[20]

Suggested insertion (just before the Insert)

// ...existing code...
repeat
    Clear(DocumentAttachmentToCreate);
    DocumentAttachmentToCreate.Init();
    DocumentAttachmentToCreate.TransferFields(DocumentAttachmentFound);
    DocumentAttachmentToCreate.Validate("No.", MoveToRecNo);
    OnMoveAttachmentsWithinSameRecordTypeOnBeforeInsert(DocumentAttachmentToCreate, MoveToRecRef, MoveToRecNo);
    DocumentAttachmentToCreate.Insert(true);
until DocumentAttachmentFound.Next() = 0;
// ...existing code...

IntegrationEvent declaration:

[IntegrationEvent(false, false)]
local procedure OnMoveAttachmentsWithinSameRecordTypeOnBeforeInsert(var DocumentAttachmentToCreate: Record "Document Attachment"; MoveToRecRef: RecordRef; MoveToRecNo: Code[20])
begin
end;

Without it, a function gap remains, forcing subsecquent solutions that are less efficient and more fragile.

Thank you very much for your time.
Internal work item: AB#614927

[AleksandricMarko]

✅ Analysis complete - approved for implementation

---

Implementation:

Add a new integration event in the MoveAttachmentsWithinSameRecordType procedure of Codeunit 1173 "Document Attachment Mgmt" before DocumentAttachmentToCreate.Insert(true) in the loop.

Location in MoveAttachmentsWithinSameRecordType procedure (around line 1607):

        // Create a copy of all found attachments with new number [MoveToRecNo]
        // Need to do this because MODIFY does not support renaming keys for a record.
        if DocumentAttachmentFound.FindSet() then
            repeat
                Clear(DocumentAttachmentToCreate);
                DocumentAttachmentToCreate.Init();
                DocumentAttachmentToCreate.TransferFields(DocumentAttachmentFound);
                DocumentAttachmentToCreate.Validate("No.", MoveToRecNo);
                OnMoveAttachmentsWithinSameRecordTypeOnBeforeInsert(DocumentAttachmentToCreate, MoveToRecRef, MoveToRecNo);  // <-- New event
                DocumentAttachmentToCreate.Insert(true);
            until DocumentAttachmentFound.Next() = 0;

Event Publisher (add at the end of the codeunit with other events):

    [IntegrationEvent(false, false)]
    local procedure OnMoveAttachmentsWithinSameRecordTypeOnBeforeInsert(var DocumentAttachmentToCreate: Record "Document Attachment"; MoveToRecRef: RecordRef; MoveToRecNo: Code[20])
    begin
    end;

---

File: DocumentAttachmentMgmt.Codeunit.al

[JesperSchulz]

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.

Build ID: 43723.