| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 317 |
| Technical Name |
cm_sa_attachment_size |
| License | OPL-1 |
| Website | https://cm.sa |
| Versions | 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 317 |
| Technical Name |
cm_sa_attachment_size |
| License | OPL-1 |
| Website | https://cm.sa |
| Versions | 17.0 18.0 19.0 |
Attachment Size Enforcer (Per-Model)
Set a different upload size cap for each Odoo model, not one cap for the whole database.
Other attachment-size apps give you a single global limit or a per-user one, but a 200 MB CAD file on a sale.order is fine while a 10 MB phone photo on a res.partner is filestore bloat. IT admins need different caps for different workflows. This module sets the max upload size per model: 25 MB on sale.order, 10 MB on res.partner, whatever each workflow needs.
Attachment Size Enforcer (Per-Model)
Set a per-model max upload size on ir.attachment, block oversize files with a clear error, and allow an optional bypass group.
What it does
Existing attachment-size-limit modules on apps.odoo.com are global or per-user, one cap for the whole database, or one cap per user. In practice a 200 MB CAD file on a sale.order is fine, but a 10 MB selfie on res.partner is a disaster. Different workflows need different caps.
Odoo core has no per-model upload cap, so admins either pick an over-broad global limit or leave the filestore to bloat.
What this module adds:
- Per rule: pick the Odoo model (
ir.model), set the max size in MB, optionally pick a bypass group. - Upload over the cap raises a
UserErrorwith a clear message naming the field, the file size, and the cap. - Bypass group can override, with a chatter note on the target record and an optional reason.
- Rules enabled or disabled from the same settings list, no code changes required.
- Works across every model, from
product.productimages tores.partnerbusiness cards tomrp.bomdrawings.
Who benefits
IT admins, system administrators, and operations managers at SMB and mid-market companies trying to keep the filestore lean.
How it works
No core-model inheritance. _register_hook wraps ir.attachment.create at registry load. TransactionCase tested on Odoo 17, 18, and 19. Safe to install, safe to uninstall. Pairs well with our Filestore Orphan Sweeper, this one stops new bloat, that one cleans up old bloat.
What the module looks like
Real screenshots from a live Odoo 19 install. Every view is standard Odoo chrome, no bespoke widgets to learn.
Common questions
Does it inherit or patch core Odoo models?
_register_hook to wrap the target method at registry load, and the wrapper unwinds cleanly at uninstall. No schema changes to core tables, no monkey-patches, no Studio surgery.Does it work on Odoo Community, or only Enterprise?
Can I uninstall it cleanly if it does not fit?
What support do I get after buying?
Can Cube Master customise it for my company?
Beyond this module, Cube Master also builds:
We are a full technology house. The Odoo utility you are reading about is one part of what we ship. If your back office, website, or app team needs more, we have the team for it.
More from the Cube Master catalogue
We ship 33 single-feature utilities at the same price point. If this one solved a pain for you, the others probably will too.
About Cube Master
We blend mastery with creativity - نمزج الإتقان بالإبداع
Cube Master is a Saudi technology house based in Al-Mubarraz. We design, build, and run business systems for customers across the Gulf and beyond: end-to-end Odoo ERP rollouts, custom AI workflows, corporate websites, and mobile apps. Strategic technology partners with Microsoft, AWS, Odoo, and Umbraco.
The Odoo utility you are reading about is one small piece of what we ship. If you need any of the above for your company, talk to us.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module