OwnCloud / NextCloud Odoo Integration

• 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

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 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.

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 would be better if that this job should be 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.

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

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 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.

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.

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 Odoo v12 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-in Cloud Sync for Enterprise Documents (44 Euro).

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 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 synchronisation, since there would be no criteria to rely upon.

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

Yes, depending on your cloud client configuration.

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 representatives directly.

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

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.

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.  

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.

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

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