469.73

v 8.0 v 10.0 v 11.0 v 12.0 Third Party 55
Included Dependencies
Cloud Storage Solutions (1278 lines of code)
Lines of code 1978
Technical Name owncloud_odoo
LicenseSee License tab
Websitehttps://faotools.com/apps/10.0/owncloud-nextcloud-odoo-integration-227
Also available in version v 14.0 v 8.0 v 11.0 v 13.0 v 12.0
You bought this module and need support? Click here!
Included Dependencies
Cloud Storage Solutions (1278 lines of code)
Lines of code 1978
Technical Name owncloud_odoo
LicenseSee License tab
Websitehttps://faotools.com/apps/10.0/owncloud-nextcloud-odoo-integration-227
Also available in version v 14.0 v 8.0 v 11.0 v 13.0 v 12.0
Odoo document system is clear and comfortable to use. However, it is not designed to work with files as OwnCloud or NextCloud do. To process attachments users need to download a file, to change it, and to upload back. Documents are not synced locally and Odoo doesn't have powerful previewers and editors as OpenOffice. Both OwnCloud and NextCloud don't have such disadvantages. This is the tool to integrate their features into your Odoo business work flow. The app automatically stores all Odoo attachments in OwnCloud or NextCloud and provides an instant access to them via web links. In such a way users work with files comfortably in the cloud storage, while the results are fully available in Odoo.
Synchronization is bilateral. All Odoo attachments are put in OwnCloud / NextCloud regularly. OwnCloud / NextCloud files create attachments in Odoo in case they are placed in a correct folder. Look at the sections From Odoo to OwnCloud / NextCloud and From OwnCloud / NextCloud to Odoo
Integration is automatic in both ways. Based on scheduled jobs, Odoo send attachments to OwnCloud / NextCloud and retrieve files from there
Any Odoo document might be synced: customers, opportunities, sale or purchase orders, tasks or issues, employees or users, etc. You decide by your own which records should be in OwnCloud / NextCloud, and which should be left in Odoo
Synchronization equally works for OwnCloud and NextCloud
All synced files are easily accessible though clicking on an attachment. You might also open a whole document folder by clicking on 'Open folder' on the attachment widget
All sync activities might be logged. Control over files and folders creations, moves, name changes and removals. Just turn on the option 'Log sync activities' and access history through the button 'Sync logs'
The tool is compatible with Odoo reporting and mailing apps. If such an app faces a synced file, it retrieves a real content from OwnCloud / NextCloud. In particular, the reports 'always reload' feature and messages & mass mailing attachments work properly
Integration is based on a single user endpoint. It means that a single user login/password of OwnCloud / NextCloud is used. Afterwards for integrations Odoo would use that credentials disregarding an actual Odoo user. Make sure, however, that real Odoo users have an access to OwnCloud / NextCloud to open URLs linked to their attachments

From Odoo to OwnCloud / NextCloud

Direct synchronization has 2 prime aims:
  • Prepare and keep updated folders' structure in OwnCloud / NextCloud
  • Upload new attachments to a correct folder
Folders

Odoo creates a convenient directory structure in OwnCloud / NextCloud: Odoo / Document type name / Document name / Files, where:

  • Odoo is a central directory for Odoo Sync in your cloud storage.
  • Document type is a synced Odoo model, for example, 'Sale orders', 'Opportunities', 'Customers'
    • You select document types by yourself. It might be any document type
    • Moreover, you might have a few folders for a single document type. Use Odoo domains to have not global 'Partners, but 'Customers' and 'Suppliers', not just 'Sale orders' but 'Commercial offers', 'To deliver', and 'Done orders'
    • With each sync Odoo would try to update document types' folders. Add a new document type at any moment. It will appear in OwnCloud / NextCloud with a next sync
    • You are welcome to introduce or change document types folder names at any moment in Odoo. Take into account: renaming in OwnCloud / NextCloud will be recovered to Odoo names
    • If you remove a model from integration, it will not be deleted from OwnCloud / NextCloud to keep already synced files safe. However, new documents of this type would not be synced
    • In case you removed a directory in OwnCloud / NextCloud, but it is still configured in Odoo, with a next sync a folder structure is going to be recovered (not files, surely).
  • Document is an exact object to sync. For instance, 'Agrolait' or 'SO019'
    • Documents are synced in case they relate to a synced document type and satisfy its filters. For example, you are not obliged to sync all partners, you may integrate only 'Customers' and 'Vendors' or only 'Companies', not 'Contacts'
    • Odoo would generate a folder in OwnCloud / NextCloud for each suitable document even for documents without attachments. It is needed for a backward sync to easily add new files
    • OwnCloud / NextCloud folder name equals a real document name. It relies upon Odoo name_get method. Thus, Odoo 'Michael Fletcher' (a contact of 'Agrolait') would be OwnCloud / NextCloud 'Agrolait, Michael Fletcher'
    • If an exact document changes its document type (e.g. a quotation is now confirmed), Odoo will automatically relocate its related folder to a proper parent directory (in the example: from 'Commercial offers' to 'To deliver')
    • In case a document relates to a few types (for instance, you have 'Vendors' and 'Customers', while Agrolait is both), this document folder would be put into the most prioritized document type. A document type priority is higher as closer to the top in Odoo interfaces it is
    • If an Odoo document is removed, the next sync will remove a corresponding OwnCloud / NextCloud directory
    • In case you remove a directory in OwnCloud / NextCloud, but it still exists in Odoo, OwnCloud / NextCloud folder structure would be recovered (while files would be unlinked in both Odoo and OwnCloud / NextCloud)
    • Folders renaming in OwnCloud / NextCloud will be replaced with Odoo names, Odoo document names are more important
  • Files are real files taken from Odoo attachments

The resulted path would be, for example, 'Odoo / Quotations / SO019 / commercial offer.png'.

The only exclusion of the rule are stand alone attachments which do not relate to any Odoo documents (their document type is 'ir.attachment'). Such attachments' path is 'Odoo / Stand Alone Attachments / image.png'.

The direct sync might take quite a long, since a lot of folders should be created. It is not recommended to make sync too frequent: once an hour or two hours is fine.

Files

With each direct sync, Odoo tries to find not yet synced attachments. If such attachments suit any document type to sync, a file will be uploaded to OwnCloud / NextCloud to a proper folder. In Odoo such attachments will become of 'url' type. It means that a file is not any more kept in Odoo server space, but now it is in OwnCloud / NextCloud. Until sync is done, Odoo attachment remains binary and stores an actual file. Such approach helps Odoo to work faster.

If you unlinked an attachment from Odoo, it would be deleted in OwnCloud / NextCloud as well.

Take into account that file names should be managed in OwnCloud / NextCloud: each backward sync would recover OwnCloud / NextCloud names, Odoo is here less important.

From OwnCloud / NextCloud to Odoo

Backward integration aims to sync new files from OwnCloud / NextCloud to Odoo:
  • If a new file is added to a proper document folder (e.g. to 'Odoo / Customers / Agrolait'), the same attachment will be added to Odoo document (in the example – to 'Agrolait')
  • In document folders you can put not only files but also child folders. In that case a link for this folder (not its content) is kept in attachments
  • In case you rename a file in OwnCloud / NextCloud, it will be renamed in Odoo as well
  • Files' removal from OwnCloud / NextCloud leads to related Odoo attachments' removal
  • If you move a file to another document folder, in Odoo a related attachment would be re-attached to this new document. Take into account: if you move a file for a not document folder, in Odoo attachment will be deleted as it has been removed from OwnCloud / NextCloud
  • If you deleted a document type or document folder, their child files are deleted as well. Thus, Odoo would remove related attachments. The folders, however, will be recovered with a next direct sync. Folders' move to another directory is also considered as a removal. Avoid such situations by following the simple rule: folders are managed mostly by Odoo, files – mostly by OwnCloud / NextCloud.

Backward OwnCloud / NextCloud might take quite much time, since each folder should be checked (the more folders, the more time the backward sync requires). It is recommended to make frequency oftener than once an hour or two hours.

Misc peculiarities

  • Do not add folders inside root or document types' folders. If they have the same name as newly synced folders, the latter would not be uploaded
  • Make sure your database has a proper SSL certificate required to use OwnCloud API
  • Try to avoid the following symbols in folders' and files' names: *, ?, ", ', :, <, >, |, +, %, !, @, \, /,. Direct sync will replace such symbols with '-'. It is done to avoid conflicts with file systems.

Preliminary steps

The tool depends on external libraries 'owncloud'. Install this library for your Odoo server through the command: pip install pyocclient

Log in

To log in in OwnCloud / NextCloud you should:
  • Enter your cloud storage full url
  • Select an OwnCloud / NextCloud, which has full rights to read, create, write and delete files and folders within a root directory
  • Enter login and password of this user
  • Introduce the title for OwnCloud / NextCloud folder, e.g. Odoo
  • Push the button 'Login and Confirm'
  • If everything is fine, push the button 'Sync'
  • Make sure that the root directory or its children are shared with your colleagues

Enter OwnCloud / NextCloud credentials

OwnCloud / NextCloud settings

Confirmed credentials to start sync

Sync to NextCloud / OwnCloud

Migration from the versions prior to the version 1.3.0

In case you decided to upgrade this module form the version prior to the version 1.3.0, you should:
  • Push the button 'Backward sync' (to make sure recent OwnCloud / NextCloud changes are synced)
  • Push the button 'Migrate from the version under 3.0'
  • Check / update synced models
  • Push the button 'Sync' to apply changes

Scheduled jobs

You may change the frequency of sync jobs. To this end:
  1. Turn on debug mode
  2. Go to technical settings > Automation > Scheduled jobs
  3. Find the jobs 'Synchronize attachments with cloud' and 'Update attachments from cloud'

No, the tags are not synchronized. We considered this feature previously, but made a decision not to introduce such a feature due to a number for reasons:

  • The connector library doesn't support getting or updating OwnCloud tags

  • Odoo attachments do not have the attribute 'tags' and it is not fully clear when those tags would be assigned to users.

  • Since the app provides bilateral sync, there might be critical conflicts during sync which would be difficult to resolve.

Yes, you can. To this end:

  1. Turn on debug mode

  2. Go to technical settings > Automation > Scheduled jobs

  3. Find the jobs 'Synchronize attachments with cloud' and 'Update attachments from cloud'.

Take into account that you should not make them too frequent. It is preferable this job is finished until a new one is started. Thus, the configuration should depend on how many items you to sync you have. Usually, the frequency is set up between 10 minutes to 4 hours.

Make also sure that you have set up enough time limits in your Odoo configuration file. Thus, LIMIT_TIME_CPU and LIMIT_TIME_REAL parameters should be equal or bigger than planned cron job time. Starting from the version 13 consider also the parameter LIMIT_TIME_REAL_CRON.

An import notice for Odoo.sh clients: the maximum time for cron job might be set up as 15 minutes only.

Yes, you can. To that goal you should prepare a separate sync model on the configuration tab. Then, for each of those apply filters: for example by type of a project.

Try to make filters self-exclusive in order a document can be definitely assigned. For instance, 'customer but not supplier', 'supplier but not customer'. Otherwise, a specific document folder would jump from one model to another.

For Odoo Enterprise you have 2 options:

  1. To sync only standard documents' attachments, but not to sync folders' and files' structure related to the Enterprise module 'Documents'.

  2. To sync both Odoo standard attachments and to reflect Enterprise Documents' folders/files. In such a case you need an extra add-on Cloud Sync for Enterprise Documents https://apps.odoo.com/apps/modules/13.0/cloud_base_documents/ (44 Euro).

No. We have strong reasons to avoid real time sync:

  • Performance issues. In case a sync is real time, each file upload will result in the loading screen.

  • Conflict issues. If 2 users simultaneously change an item, it might lead to unresolved situations. In case of regular jobs we can fix it afterwards, while in case of real time we would need to save it as some queue, and it will be even more misleading for users.

  • Functionality issues. In particular, renaming and restructuring of items. In the backward sync the tool strictly relies upon directories' logic, and during each sync 100% of items are checked. In case it is done after each update, it will be thousands of requests per second. If not: changes would be lost.

No, the module works with the pre-defined structure of folders:

  1. Odoo – a core folder for sync

  2. Models – folders for each Odoo document type. For example, 'Projects', 'Partners'. Distinguished by domain there might be more specific folders: e.g., 'Customer 1 Projects', 'Projects of the Customer 2', 'Internal Projects', etc.

  3. Objects – folders for each document, e.g. 'Project 1' or 'Customer 1'

  4. Files and folders related to this Odoo document to be synced.

As a result you may have for instance:

  • Odoo / Projects / Project 1 / files and folders related to the  project 1

  • Odoo / Customer 1 Projects / Project 1; Odoo / Customer 2 Projects / Project 3, ...

  • Odoo / Customers / Customer 1 / files and folders related to the customer 1

This structure is always flat, meaning that there are only those levels of hierarchy. Thus, it is correct that various document types can't be done within the same structure. Within the folder 'Customer 1' we can't keep the files related both to sale orders, invoices, and projects. Each of those document type has an own (or a few own) folders. Otherwise, we will not have a chance to make backward synchronization, since there would be no criteria to rely upon.

All synced files are kept only in the clouds, in Odoo attachments become of the URL-type. When a user clicks on those, Odoo would redirect him/her to a cloud storage.

No, the tool relies upon a single user end point. It means that all sync processes are done under a single cloud admin (app). Access rights for created folders / files are not automatized. You should administrate those rights in your cloud storage solution.

Yes, although in case of many folders / attachments to sync, the process might be slow. Simultaneously, our clients reported to us the environments with >10k partners and ~5k product variants to be synced, and the processes were acceptable.

A few points to emphasize:

  1. The sync is constructed in such a way that anyway any item will be synced and will not be lost, although it might be not fast. It is guaranteed by first-in-first-out queues and by each job commits.

  2. The number of objects might be limited logically. The models' configuration let you restrict sync of obsolete items (e.g there is no sense to sync archived partners or orders which are done 2 years ago).

No, since files are now kept in the cloud storage, and retrieving binary contents would consume a lot of resources. Odoo has a link which would redirect a user to a proper previewer or editor.

For models' directories (sale orders, opportunities, suppliers, etc.): you may assign your own name on the configuration tab for any document type.

For objects' folders (SO-001, John Smith, etc.): the tool relies upon the Odoo 'name_get' method for this document type. In case you need to make a different title, you should re-define this method for a specific model. It requires source code modification.

No, the tool is only a technical core. You also need the connector for your cloud client.

According to the current Odoo Apps Store policies:

  • every module bought for the version 12.0 and prior gives you an access to the all versions up to 12.0.
  • starting from the version 13.0, every version of the module should be purchased separately.
  • disregarding the version, purchasing a tool grants you a right for all updates and bug fixes within a major version.

Take into account that Odoo Tools team does not control those policies. By all questions please contact the Odoo Apps Store representativesdirectly.

  1. Restart your Odoo server and update the module

  2. Clean your browser cache (Ctrl + Shift + R) or open Odoo in a private window.

Yes, sure. Take into account that Odoo automatically adds all dependencies to a cart. You should exclude previously purchased tools.

Regretfully, we do not have a technical possibility to provide individual prices.

  1. Unzip source code of purchased tools in one of your Odoo add-ons directory

  2. Re-start the Odoo server

  3. Turn on the developer mode (technical settings)

  4. Update the apps' list (the apps' menu)

  5. Find the app and push the button 'Install'

  6. Follow the guidelines on the app's page if those exist.

Sorry, but no. We distribute the tools only through theofficial Odoo apps store

Yes, all modules marked in dependencies are absolutely required for a correct work of our tool. Take into account that price marked on the app page already includes all necessary dependencies.  

No, third party apps can not be used on Odoo Online.

Red / orange warning itself does not influence features of the app. Regretfully, sometimes our modules do not pass standard automatic tests, since the latter assumes behavior which is in conflict with our apps goals. For example, we change price calculation, while standard Odoo module tests compare final price to standard algorithm.

So, first of all, please check deployed database features. Does everything work correctly?

If you still assume that warning influences real features, please contact us and forward full installation logs and the full lists of deployed modules (including core and third party ones).

As soon as you purchased the app, the button 'Deploy on Odoo.sh' will appear on the app's page in the Odoo store. Push this button and follow the instructions.

Take into account that for paid tools you need to have a private GIT repository linked to your Odoo.sh projects

Fast access to OwnCloud / NextCloud files and folders

Integrate Odoo and OwnCloud / NextCloud

Synced files are simply found in OwnCloud / NextCloud. Add unlimited number of files or folders here

Odoo attachments as OwnCloud / NextCloud files

Choose document types to be synced

OwnCloud / NextCloud models structure

Document type might have a few folders based on filters

Documents filtered

All document types are in the root directory 'Odoo'

Onedrive root directory

Document types' folders

Document types' folders in OwnCloud / NextCloud

All document of this type has an own folder

Documents' folders

Logged synchronisation activities

Sync Logs

Bug reporting

In case you have faced any bugs or inconsistent behavior, do not hesitate to contact us. We guarantee to provide fixes during 60 days after a purchase, while even after this period we are strongly interested to improve our tools.

To send us a bug report: press the "Website" link on the top of this page and push the button "Bug Report" (the tab Support). Alternatively, copy the link https://faotools.com/my/tickets/newticket?&url_app_id=46&ticket_version=10.0&url_type_id=1

No phone number or credit card are required to contact us: only a short email sign up which does not take more than 30 seconds.

Please include in your request as many details as possible: screen shots, Odoo server logs, full description of how to re-produce your problem, and so on. Usually it takes a few business days to prepare a working plan by an issue (if a bug is confirmed) or provide you with guidelines what should be done (otherwise).

Public features request and module ideas (free development)

We are strongly motivated to improve our tools and would be grateful for any sort of feedback. In case your requirements are of public use and might be efficiently implemented, the team would include those into our to-do list.

Such to-do list is processed on a regular basis and does not assume extra fees. Altough we cannot promise deadlines and final design, it might be a good way to get desired features without investments and risks.

To share ideas: press the "Website" link on the top of this page and push the button "Share Features Ideas" (the tab Support). Alternatively, copy the link https://faotools.com/my/tickets/newticket?&url_app_id=46&ticket_version=10.0&url_type_id=5

No phone number or credit card are required to contact us: only a short email sign up which does not take more than 30 seconds.

New features and extra Odoo services (individual development)

Each of our apps might be customized and extended to suit your specific requirements.

Our customization team (itlibertas.com) fulfills not only such jobs but it also provides a full range of Odoo services. From simple modifications and consultations to complex enterprise projects. The team has completed over 100 implementations since 2012, and might help with any technical or business needs.

To contact us for details and conditions: press the "Website" link on the top of this page and push the button "Request Individual Customization" (the tab Support). Alternatively, copy the link https://faotools.com/my/tickets/newticket?&url_app_id=46&ticket_version=10.0&url_type_id=2

No phone number or credit card are required to contact us: only a short email sign up which does not take more than 30 seconds.

Questions and misc issues

Feel free to contact us by any other concerns, doubts, or questions: press the "Website" link on the top of this page and push the button "Raise Question" (the tab Support). Alternatively, copy the link https://faotools.com/my/tickets/newticket?&url_app_id=46&ticket_version=10.0&url_type_id=4

About the team

faOtools (faotools.com, former odootools.com) is the team of developers and business analysts to help you extend Odoo potential. We have been communicating with end users to whom the software became the main business tool since 2012. As a result, we are proud of dozens of successful Odoo apps developed. We are open for new ideas and challenges to create the best Odoo apps for business needs all over the world.

You may like the tools

Google Drive Odoo Integration

The tool to automatically synchronize Odoo attachments with Google Drive files in both ways

394
OneDrive / SharePoint Odoo Integration

The tool to automatically synchronize Odoo attachments with OneDrive files in both ways

394
DropBox Odoo Integration

The tool to automatically synchronize Odoo attachments with DropBox files in both ways

394
KnowSystem: Knowledge Base System

The tool to build deep and structured knowledge base for internal and external use. Knowledge System. KMS

298
KPI Balanced Scorecard

The tool to set up KPI targets and control their fulfillment by periods

298
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

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.