REST Attachment Upload Size Limit

Appears there’s a 2MB files size limit when uploading attachments. Anyone know how to configure that.

Thanks in advance,


Found it in the Web config file on IIS.

What did you change?

@Olga I was asked a similar question about uploads. I’m running IIS 10. It appears the default upload limit is ~4GB.

The following site helped me connect the dots.

Here’s the text from the article in case it ever goes down.

You have 3 available options to increase the file upload limit:

  1. Modify the maxAllowedContentLength setting in the web.config
    You can increase the maximum file size by modify the maxAllowedContentLength setting in the web.config file.

  2. Edit the request filtering feature settings and the request limits using IIS manager
    Open IIS Manager.
    Select the website that you want to configure.
    Make sure you are in Features View per the button at the bottom of the manager.
    Select Requests Filtering and open it by double-clicking the icon. The Request Filtering pane displays.
    From the Actions pane on the right hand side of the screen click Edit Feature Settings… link. The Edit Request Filtering Settings window displays.
    In the Request Limits section, enter the appropriate Maximum allowed content length (Bytes) and then click the OK button.
    Restart IIS.

  3. Manually edit the ApplicationHost.config file
    Click Start. In the Start Search box, type Notepad. Right-click Notepad, and then click Run as administrator.
    On the File menu, click Open. In the File name box, type %windir%\system32\inetsrv\config\applicationhost.config, and then click Open.
    In the ApplicationHost.config file, locate the node.
    Remove the maxAllowedContentLength property. Or, add a value that matches the size of the Content-Length header that the client sends as part of the request.

1 Like

A 4th option, which I have been sidelined on a few times now, is change the responsibilities of uploading and linking. Instead of Kinetic doing both steps, do the upload to your repository (ECM, SharePoint, DropBox, S3, Blob Storage,…) with enough information to launch a WebHook to send the link and the attachment information back to Kinetic. The repository would have to know the Document type, number, etc so the WebHook supplies Kinetic with the necessary information to create a LINK attachment type.

The advantage is that you get the full feature set of your ECM and remove all of the limits imposed by Kinetic.


who would be responsible to upload it? client customization? What would browser UI do? Repeat the same in JS?
You will have to implement upload yourself using the API ECM, SP, etc, provided.
Does not look simple for me.

Depends on the Document Type I suppose. I’m thinking about automation. Start with AP invoices. Invoices arrive in the email inbox for AP and are sent to the “reader” (OCR, AI, etc.) to get the PO number. With the PO number, we fill in our ECM fields of the document where you want this attached. Import the into the ECM which would then send the hook to Kinetic.

For non-automation, manually upload into your ECM of choice and fill out the meta data to launch the hook.

Nothing? :person_shrugging:

But say we do, an upload component might be able accept a drop which grabs the meta data and formats it into the ECM’s upload API. :thinking:

@olga, you know I never suggest simple things!


1 Like

I am glad you are advocating for software that people spent good money on to be integrated and put to use.

well, this does not sound good.
Also, how SP, for example, will know to call a hook? you are now going to add some automation to other systems, instead of Epicor.

I think ERP needs eventually implement upload in chunks and then you can store a petabyte in one file if you want :smiling_imp:. Though it is tricky.

Not instead of but in addition to Epicor. I imagine a set of automation outside and above all of the business systems that communicate through a business-domain API. I am trying to take Mr. Bezos’ API mandate somewhat seriously. Hopefully this gives us a common gateway and security context between Kinetic, Document Storage, Emailing, Payroll/HR, CRM, IIoT, and other business systems. Users shouldn’t know or care if a file is stored in ECM, SharePoint, S3, Azure Blob Storage, or where-ever as long as we use an API that encapsulates the storage while enforcing security and tracking.

This doesn’t mean there isn’t a place for automation within each system. I wouldn’t replace Task Sets, ECM Workflows, etc. with an outside system. But I wouldn’t mind exposing all of these systems to a central location showing all of my approvals and/or to-dos in one place.

And yes, this is a lot of work. :sweat_drops: But an old man can dream. :slight_smile: