<h1 class="title">Base FileURL Field</h1> <p>This module adds a new field type FileURL to Odoo. FileURL is an extension of field type Binary, with the aim to store its value on any kind of external storage. It's been built with the focus on Amazon S3 but could be used with other storage solution as long as it extends the functionality of base_attachment_object_storage.</p> <a name="usage"></a> <h2>Usage</h2> <dl class="docutils"> <dt>FileURL fields is intended to store Binary data on an external storage</dt> <dd>with the possibility to be accessed outside of Odoo.</dd> </dl> <table class="docutils field-list" frame="void" rules="none"> <col class="field-name" /> <col class="field-body" /> <tbody valign="top"> <tr class="field"><th class="field-name">param storage_location:</th><td class="field-body">Required external storage that must be activated on the system (cf base_attachment_storage)</td> </tr> <tr class="field"><th class="field-name">param storage_path:</th><td class="field-body">Path to be used as a prefix to the filename in the storage solution (must be used with filename)</td> </tr> <tr class="field"><th class="field-name">param filename:</th><td class="field-body">Field on the same model which stores the filename. Will be used to set fname on ir.attachment and, if storage_path is defined, will be passed to force the storage key.</td> </tr> </tbody> </table> <a name="limitations-issues"></a> <h2>Limitations / Issues</h2> <ul class="simple"> <li>Filename must be stored in a separate field on the same model defining a FileURL field.</li> <li>While using storage_path and filename attributes, there's a risk existing storage object are overwritten if files with the same filename are added on different records.</li> </ul> <a name="example"></a> <h2>Example</h2> <p>cf <cite>test_base_fileurl_field</cite> module in <a class="reference external" href="https://github.com/camptocamp/odoo-cloud-platform">https://github.com/camptocamp/odoo-cloud-platform</a></p>