I am working on an application where I need to handle large Excel files (up to 40 MB). Here’s how I’m processing the files:

1. Upload and Chunking:

   • The file is uploaded via the browser.
   • It is split into 5 MB chunks and saved into the database.

2. Processing with Timer:

   • A Timer fetches these chunks from the database and processes them asynchronously.
   • The Timer calls a .NET extension to merge the chunks back into a single binary file using a method similar to the BinaryConcat function in the Binary Concat Forge component.

3. Issue:

   • When I pass all the chunks to the .NET extension method, I receive the following error:

     name: 'OutSystems.Application.ErrorHandling.ExtensionException', message: 'Input payload is too large (33.33MB), maximum allowed is 5.5MB.', stack: 'OutSystems.Application.ErrorHandling.ExtensionException'

   • This indicates that the input payload exceeds the OutSystems limit of 5.5 MB.

Questions:

1. Is there any way to increase the maximum allowed payload size in OutSystems ODC for server-side processing?
2. If not, what is the best approach to handle this requirement? My main goal is to reassemble the file efficiently to process it asynchronously.
3. Is there another recommended method in OutSystems to handle such large files?

Additional Details:

• The chunks are stored in the database as binary data.
• The final merged binary file needs to be processed further (parsing the Excel data).
• This process is triggered and executed entirely on the server-side (via a Timer).

Looking forward to suggestions and best practices for managing this scenario. Thank you!