Customizing storage

• 12/03/2026
• 6 minutes to read

Expense Management provides support for three different storage models: File System, Database, and Azure Blob Storage. But it's also possible for you to customize your storage by extending or overruling the way documents are stored and fetched in Expense Management.

You can overrule or extend the existing behavior using four different publisher events that are provided in the codeunit CEM Doc. File Events:

• SetAttachment — invoked when a file is requested to be stored.
• GetAttachment — invoked when a file is requested.
• HasAttachment — invoked when the existence of a file is checked.
• ClearAttachment — invoked when a file deletion is requested, for example when a document related to the relevant file is deleted or imported.

PDF documents are split into pages that are displayed in the addin. You can interact with the images by using the following events:

• SetPage — invoked when a file is requested to be stored.
• GetPage — invoked when a file is requested.
• HasPage — invoked when the existence of a file is checked.
• ClearPage — invoked when a file deletion is requested, for example when a document related to the relevant file is deleted or imported.

In several localizations, document signing is a necessity. In these cases, the following events can be used for interaction with digitally-signed PDF documents:

• SetPDF — invoked when a file is requested to be stored.
• GetPDF — invoked when a file is requested.
• HasPDF — invoked when the existence of a file is checked.
• ClearPDF — invoked when a file deletion is requested, for example when a document related to the relevant file is deleted or imported.

In Expense Management, all files are initially downloaded from Continia Online in a buffer called Attachment Inbox. This is why all events are also available for inbox processes as well. These are:

• SetInboxAttachment — invoked when a file is requested to be stored.
• GetInboxAttachment — invoked when a file is requested.
• HasInboxAttachment — invoked when the existence of a file is checked.
• ClearInboxAttachment — invoked when a file deletion is requested, for example when a document related to the relevant file is deleted or imported.
• SetInboxPage — invoked when a PDF page is requested to be stored.
• GetInboxPage — invoked when a PDF page is requested.
• HasInboxPage — invoked when the existence of a PDF page is checked.
• ClearInboxPage — invoked when a PDF page deletion is requested, for example when a document related to the relevant file is deleted or imported.
• SetInboxPDF — invoked when a digitally signed PDF is requested to be stored.
• GetInboxPDF — invoked when a digitally signed PDF is requested.
• HasInboxPDF — invoked when the existence of a digitally signed PDF is checked.
• ClearInboxPDF — invoked when a digitally signed PDF deletion is requested, for example when a document related to the relevant file is deleted or imported.

All of the above methods implement a handled pattern, which enables programmers to overrule or extend the behavior. If Handled is set to true, Expense Management won't do anything, as it expects the file operation to be handled by the extension code. If Handled isn't set, the code will carry out the file operation as implemented according to the storage model selected in the Expense Management setup. In this way, it's possible to extend and store a subset of files externally and still let Expense Management handle the file storage.

All of the methods have the following arguments:

• EMAttachment — A reference to the attachment record that has all the information about the attachment.

• Success — A Boolean value indicating if the operation was successful. This value is only propagated if the Handled value is also set to true.

OnSet() and OnGet() have one additional parameter, TempFile, which is a CDC Temp File record. The CDC Temp File record is to be considered a file object, as it contains file information and the content of the file. The Data field on the record contains the data of the file that's either stored or fetched. So when you subscribe to OnSet(), the Data field will contain the content of the file that's to be stored, whereas for OnGet(), the content of the file that's requested should appear in the Data field.