Cloud Storage Solutions v.17
The tool to flexibly structure Odoo attachments in folders and synchronize directories with cloud clients: Google Drive, OneDrive/SharePoint, Nextcloud/ownCloud, Dropbox, Amazon S3, Box, and NAS. DMS. File Manager. Document management system
This tool organizes Odoo attachments in folders' trees and synchronizes those with your choice's cloud storage solution(s). The app introduces automatic algorithms to prepare directories for documents and integrate those with workflows of Google Drive, OneDrive/SharePoint, Nextcloud/ownCloud, Dropbox, Amazon/MinIO S3, Box, and NAS/WebDAV (Synology, QNAP, TrueNAS, etc.).
- the core module which introduces the file manager interface and basic mechanics for synchronizations with various cloud clients.
Su precio es
398€
358€.
- the connector to synchronize Odoo folders and attachments with OneDrive or/and SharePoint. The features assumed by this add-on are marked by the icon .
Su precio es
89€
80€.
- the connector to synchronize Odoo folders and attachments with Google Drive. The features assumed by this add-on are marked by the icon .
Su precio es
89€
80€.
- the connector to synchronize Odoo folders and attachments with Amazon S3. The features assumed by this add-on are marked by the icon .
Su precio es
89€
80€.
- the connector to synchronize Odoo folders and attachments with Nextcloud or/and ownCloud. The features assumed by this add-on are marked by the icon .
Su precio es
89€
80€.
- the connector to synchronize Odoo folders and attachments with Dropbox. The features assumed by this add-on are marked by the icon .
Su precio es
89€
80€.
- the connector to synchronize Odoo folders and attachments with NAS solutions (Synology, QNAP, TrueNAS) and generic WebDAV storage. The features assumed by this add-on are marked by the icon .
Su precio es
89€
80€.
- the connector to synchronize Odoo folders and attachments with Box. The features assumed by this add-on are marked by the icon .
Su precio es
89€
80€.
- an optional add-on to prepare workspace-related folders and to sync Odoo documents (introduced by the enterprise app 'Documents') with clouds. The features assumed by this add-on are marked by the icon .
Su precio es
44€
39€.
Automatic Folders
Decide which Odoo document types should have their folder trees. Directories are regularly updated based on flexible rules and existing Odoo objects
Sync with Cloud Storage Solutions
Synchronize chosen folders and files with specific cloud storage: Google Drive, OneDrive, SharePoint, Nextcloud, Dropbox, Amazon, Box, MinIO S3, NAS/WebDAV (Synology, QNAP, TrueNAS, etc.), and ownCloud. Have as many connections as you need
File Manager Interface
Manage folders and attachments from a single view. Comfortably navigate by directories and tags. Search and download files one by one or in a batch. Upload and move attachments
Enhanced Attachment Box
Organize files of any Odoo object in a set of subfolders. Instantly access folders and files in the attachment box and in synced cloud interfaces
Portal Sharing
Share files, directories, and tags with particular partners or with an access URL. Let users download whole shares and separate items, upload attachments, and add folders or tags
Enterprise documents compatible
Set up rules to prepare folders based on Odoo Enterprise workspaces. All features, including sharing, downloading, and signing, will work even after the sync
Automatic Regular Sync
Rely on auto-synchronization between Odoo and cloud solutions based on scheduled jobs. No manual interaction is required
Bilateral Sync
Odoo sends attachments to cloud storage solutions and retrieves files from there. Binary content is kept in clouds, while Odoo provides direct access to synced items.
Works well with SharePoint. Supportive team
We've been using this with SharePoint and it's been working great. One of the best things is having everything, including logs right in Odoo's interface, so you can actually see what's going on. It's also super convenient that you can view or download synced files from the attachment box without having to leave the page or even log in to Sharepoint.
Setup was pretty smooth for us. When we had a few questions about setting up the folder hierarchy and priorities, the developer team got back to us in just a couple of hours and helped us figure it out. Great support and great extension!
Tricky setup, but works perfectly now
Really solid module. We managed to get a very flexible folder structure (sorted by clients) and synced all our sales orders, invoices and tasks by projects to Google Drive.
Initial setup was a bit of a pain and kinda tricky to configure everything at first, but now it's running smoothly and works perfectly. The faotools team helped a lot. Def worth it if u need to keep your docs organized in Odoo and Google Drive.
Recommended!
Great support, assistance and very good connector!
We are very happy with the support we received when configuring the Sharepoint - Odoo connector. The connector has great functionalities.
All our questions were answered very fast (within one day).
FaOtools helped us optimising our connector and assisted us with future improvements.
We really recommend this connector.
Great module and Great Support!
The module works great! and the support is phenomenal!
A must-buy if it suits your requirements!
very professional app, excellen t customer service
This app is very well programmed and does its job very well. But the best is the excellent customer service who also helps when the problem lies somewhere else. You receive a lot for your money.
Excellent !!!
Great App and great Service from faOtools.
An impressive app and world-class support
I have been very impressed by the way the OneDrive / SharePoint Odoo Integration module synchronises content in both directions and allows me to share documents in Odoo with my SharePoint site. Above all the technical support is top-notch, which greatly increases the value of this product. I highly recommend this product for anyone considering synchronising Odoo with SharePoint/OneDrive.
Very good product
A perfect solution to integrate Owncloud with Odoo. We sync a high volume of objects across multiple Odoo models, which works seamless and stable. For us it is the perfect solution to have an external DMS instead of the Odoo native attachment handling, which also enables us to interchange files between systems in our best-of-breed setup.
The team behind this module is extremely professional and responsive. They helped us on a few occasions and provided clear answers and prompt support when required, and they even went out of their way to assist us with another requirement we had. Cannot recommend the product and team highly enough, try this if you're in the market to connect Odoo with an external document solution.
Works fine, good support
The first experience with the module is excellent. I had some trouble to configure things right on the Microsoft-side, but the team provided quick and good support.
Best module for integration with google drive
The module performs its function correctly and faOtools responds quickly to any problem and, in case of detecting any bug, quickly apply the changes. Its support is 10 stars.
Works according to specs
I have used this app with Odoo 12 and Nextcloud 16 and it works as specified. Odoo Tools offers very responsive support which is really helpful. Of course 5 stars...!
This is Awesome
I have used Cloud Sync on Next/Own Cloud and works really great.
Odoo File Manager Interface
-
Navigate by folders: select a directory to show its attachments. Expand and hide folders' layers in a click. Add subfolders to any directory (right mouse click > Create subfolder)
-
Open any synced folder in its cloud client (right mouse click > Open in clouds). Show a folder peer Odoo object if there is such a connection (right mouse click > Open linked object). Change settings of manually created folders, including granting access rights (right mouse click > Edit Settings)
-
Navigate by attachment tags. Create and edit tags right from the navigation panel
-
Search and highlight tags and folders in seconds even if there are thousands of items
-
Drag and drop to re-structure folders (relates only to manually created directories; for automatic folders change rules instead) and tags
-
Download any folder or any tag with all its attachments as a single zip archive (right mouse click > Download as archive)
-
Upload attachments to the current folder. Use the top header button 'Upload file' or drag and drop files
-
Instantly open any synced attachment in a linked cloud client (push the link in the middle of attachment cards)
-
Download any attachment to your local computer disregarding whether it is synced or not (push the icon 'cloud' or 'download' in the footer right corner)
-
Consequentially select attachments and download them as a single zip archive
-
Move any files to any folder, including re-attaching items between Odoo objects (e.g. from a sale order SO-001 to another quotation or its customer folder). Use the mass action for that end or just drop an attachment to a required directory. Update attachments' tags by dragging those to the left navigation panel or by executing the mass action. Delete attachments in a batch
-
Apply standard attachments search to find required files.
Enhanced Attachment Box
-
Any Odoo object might be linked to its folder. See Automatic folders' structure
-
Flexibly define subfolders to organize the structure you need (right mouse click > Create subfolder)
-
Drag and drop to re-structure subfolders
-
Select a folder to see its attachments. By default, files of the object root directory are shown
-
Download any folder with all attachments as a single zip archive (right mouse click > Download as archive)
-
Open the already synced folder in its cloud client (right mouse click > Open in clouds)
-
Upload attachment to a chosen folder (use the button 'Add attachments' or drag files to the attachment box area)
-
Instantly open any synced attachment in a linked cloud client (push the icon 'clouds')
-
Download any attachment to your local computer disregarding whether it is synced or not (push the icon 'download')
-
Use standard Odoo preview for both synced and local files (click on a file thumbnail)
-
Delete attachments as usual
-
All actions are equally applicable to object attachments and attachments related to messages.
Cloud Storage Synchronization
Multi synchronization
-
Use optional add-ons to synchronize the document management system with the cloud client(s) of your choice: Google Drive, OneDrive, SharePoint, Nextcloud, Dropbox, Amazon, Box, MinIO S3, NAS/WebDAV (Synology, QNAP, TrueNAS, etc.), and ownCloud. Have as many connections as you need
-
Establish multiple connections to different cloud clients simultaneously. For example, sync sales-related folders to Google Drive; tasks and projects - to SharePoint or OneDrive; HR documents - to Nextcloud/ownCloud; manufacturing specifications - to Dropbox. Take into account that a specific folder might be synced to only a single cloud storage solution. Its children would be synced to the same client
-
For each cloud client, the app lets set up a few instances. For example, for Google Drive, you may share some folders to your personal drive, others - to one of your team drives, and the rest - to your teammate's drive
-
To establish a connection with particular cloud storage, follow the instructions that are specific for client types. See the tab Configuration for details
-
Any connection might be paused manually if it is needed. It might be also auto-stopped if there are critical issues during the sync. Then, you should re-connect to a target cloud client
Cloud clients
-
Synchronization for all cloud clients is based on the same principles and on the same queue. Simultaneously, there might be differences in sync results due to different features of various cloud storage solutions
-
Establishing connections for different types of cloud clients assumes installing optional add-ons, different approaches for Odoo, and external API configuration. Follow the instructions on the tab 'Guidelines'
-
Google Drive Odoo Integration allows establishing a connection with any personal or team drive
-
OneDrive / SharePoint Odoo Integration assumes synchronization with any drive of personal/business/SharePoint tariffs
-
ownCloud/Nextcloud Odoo Integration et integrate Odoo with any instances of ownCloud and Nextcloud. In comparison to other clients, the app allows setting the type of attachment links. By default, Odoo links are internal: only authorized users may access them. Optionally make links public (the setting 'Use Public URLs'). See details on the guidelines tab
-
Dropbox Odoo Integration works for all DropBox tariffs, including Personal DropBox (Basic, Plus, Family) and business DropBox (Professional, Standard, Advanced). In comparison to other clients, the app allows choosing whether cloud items would be shared or internal. See details on the guidelines tab
-
Amazon S3 Odoo Integration (amazon_s3_odoo) synchronizes Odoo folders and attachments with Amazon S3 buckets
-
NAS/WebDAV Odoo Integration (nas_odoo) connects Odoo documents with NAS and WebDAV-compatible storage, including Synology, QNAP, and TrueNAS
-
Box Odoo Integration (box_odoo) synchronizes Odoo folders and attachments with Box cloud storage
Automatic two-sided sync
-
Integration is based on scheduled jobs and is fully automatized. The app regularly checks changes in systems and runs sync operations
-
Synchronization is bilateral. Updates in Odoo are reflected in cloud clients (direct sync); changes in cloud clients modify Odoo folders and attachments (backward sync)
-
Any cloud connection might be reset. In this way, the app assumes getting back all items back to Odoo (reverse sync)
-
Odoo folders and attachments might be re-attached to a new cloud client. Hence, items will be first taken back to Odoo (reverse sync) and then put will be put to the new cloud storage (direct sync)
Queue-based synchronization
-
Once in 15 minutes, the app examines updates in Odoo and cloud storage(s) to prepare a synchronization queue
-
Folders' checks follow the First-In-First-Out (FIFO) principle. So, directories that have not been examined for the longest will be processed first
-
Once in 15 minutes, the sync queue is run by the special scheduled job. Firstly, the most important (blocking) tasks would be done
-
Control planned jobs and their fulfillment in the special Odoo logs interface (Cloud Storage > Configuration > Sync Logs). Subscribe for particular cloud clients notifications
-
If the app faces sync failures, it will re-try operations afterward. Sync queue processing would not be stopped if there are items not blocked by such failures
Odoo attachments for cloud storage: direct sync
-
Direct sync prepares the folders' hierarchy and uploads Odoo attachments for cloud storage
-
Direct sync checks whether attachments are added or deleted for synced directories. If so, they would be created or removed in cloud storage. In particular, it means that any file added to a folder-related Odoo object (e.g. Quotation), would be automatically moved to a linked cloud client
-
Direct sync makes all synced Odoo attachments change their type to a link (URL), while binary content is removed with one of the next Odoo cleaners. So, no actual files would be stored on your Odoo server
-
Direct sync checks whether a new folder is added. Disregarding whether it is done manually or automatically, the app would generate a peer directory in a cloud storage
-
Direct sync checks whether there are any updates in folders. If so, such changes are reflected in a cloud client
Cloud storage files and folders for Odoo: backward sync
-
Backward sync checks whether any files or subfolders are added to cloud storage folders. If so, the app would create URL attachments/subdirectories inside linked Odoo directories (and hence Odoo objects if any)
-
Backward sync checks whether there are any updates in folders or attachments. Such updates would be then reflected in Odoo
-
Backward sync checks whether any files are deleted/moved in a cloud document folder. If so, a linked Odoo attachment would be also unlinked or moved
-
If you deleted a cloud storage folder related to a folder rule / Odoo object, their child files would be deleted as well. Thus, Odoo would remove related attachments. The folders, however, will be recovered with a direct sync
-
In case of conflicts, direct sync changes are in general considered more important than backward updates.
Resetting or changing cloud client: reverse sync
-
In case you decided to reset the connection with a specific cloud client, files would be moved back to Odoo
-
In case you decided to change the cloud client of a folder rule or a folder, files would be first taken back to Odoo, and then direct sync for a new client would be done
-
Reverse sync operations are prioritized to direct and backward sync operations
-
Not all items can be correctly reversed to Odoo due to cloud client peculiarities. For example, there are documents that may exist only in cloud storage environments (e.g. Google Sheets). The app would try to convert such documents, but in some cases, it would require manual interactions.
Automatic Folder Structure
Rules for automatic folders
-
The app allows preparing its own folder for any Odoo object
-
To configure a particular Odoo document type to generate a folder, you should just prepare a new folder rule (Cloud Storage > Configuration > Folder rules). For example, select the model 'Task' to make Odoo add a folder for each project task, so Tasks > Task 1, Task 2, ...
-
Automatically created directories would contain all attachments their linked objects have
-
Folders are updated regularly based on the scheduled job
Multi directories for each model
-
Each Odoo model might have a few linked folders
-
Apply any model storable field to filter Odoo objects and, in this way, split objects into a few super directories. For example, have own folders for individuals and companies, for European and American opportunities, for quotations and confirmed orders, for each project
-
Filter Odoo objects by relative periods by applying date fields of linked documents. For example, leads registered in the last 3 months or invoices updated in the last week
-
As a result, the app lets have paths like 'Odoo > Quotations Europe > SO-001' or ' Odoo > the last year posted invoices (America) > SO-001'
Flexible folders' tree
-
It is possible to set up a hierarchy of folder rules to prepare a more flexible directories structure
-
To that goal define a parent rule for a required folder configuration. For example, use a project-related rule as a parent for a task-related rule, a customer-related rule - for invoices-related rules
-
In order for folder relations to work correctly, it is also needed to enter a parent model field. So, it is the field that links models between each other (many2one relation). For example, 'Project' of a task, 'Customer' of a sales order, or 'Sales Team' of an opportunity
-
As a result, the tool allows reflecting your Odoo workflow logic and have paths like 'Odoo > Customers > Azure Interior > Projects > Software Design > Prepare Specification' and 'Odoo > Customers > Azure Interior > Quotations > SO-001'
Subfolders, default folders, and default files
-
The app lets add an unlimited number of manual subfolders for each folder. In particular, you may have a directories tree right in each object attachment box
-
For the first generation, it is possible to define default folders, so subdirectories would be auto-generated for a specific Odoo object folder. Afterward, you may add delete/edit those or add new ones
-
The same mechanics are applied to prepare default files. For example, to have contract/personal card templates which then are assumed to be filled with real data
Configurable folder titles
-
Each folder rule assumes to generate a directory. Names for such directories are assigned right on a rule form. For example, introduce 'Jobs' for a task-related rule or 'HR' for employees' folders. By default, the Odoo model name would be used
-
For object-related folders, the names are generated based on the Odoo standard display names. So, if not defined the opposite, it would be the same title as you see in the Odoo form view header
-
The app lets define complex name expressions for object-related folders (the tab 'Name Expression' on a folder rule form). To that goal, apply the syntax used in Odoo email templates. For example, {{ object.project_id.name }}, {{ object.name }} to reflect a project name in tasks folders
-
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. Avoid also too long names: e.g. more than 100 symbols
Enterprise Documents
-
The app allows generating folders for workspaces introduced by the Odoo Enterprise apps 'Documents'
-
To force Odoo to prepare workspace-related directories, define folder rule(s) of the type 'Workspace-Related rule'. The tool would automatically create linked folders and sync those for chosen cloud storage with one of the next jobs
-
It is not obligatory to reflect the whole DMS structure. Thus, it is possible to filter workspaces by any storable field. For example, to add a folder only for workspaces that contain the keyword 'Internal'. Take into account: if a workspace was synced, all its child workspaces would be also synced
-
If you generated a subfolder for any workspace-related folder, the app would also create such a Documents workspace
Typical use cases
-
Customers: add all partner files in a single super directory. Optionally distinguish companies and individuals. For example, Odoo > Customers > Azure Interior > Contacts > John Brown
-
Sales orders and invoices: keep all sale-related printings and contracts in your own quotation directories for each customer. For example, Odoo > Customers > Azure Interior > Orders > SO-001 and Odoo > Customers > Azure Interior > Invoices > INV-00001
-
Opportunities: store all specifications, requirements, and any files which would let you make a good offer carefully structured by each sales team and case. For example, Odoo > Sale teams > Europe > Leads > Interest in 50 chairs
-
Project and tasks: prepare a folder for each customer project and task. For example, Odoo > Customers > Azure Interior > Projects > Software design > Tasks > Specification
-
Human resources: gather all files by each employee in a single folder: photos, document scans, contracts. Structure employees by department. For example, Odoo > Departments > Accounting department > Employees > Anita Olivier.
Files and Folders Sharing
-
Share particular attachments, whole directories, or even all files of specific tags
-
Grant access to chosen Odoo contacts. Send an invitation to any Odoo portal users at any moment
-
Generate a special access link for public use (even without a user). Change it to make the previous one outdated
-
Make shares for temporary use or available constantly until archived
-
Create an unlimited number of shares with any setups and attachments involved. Portal users might access those through the special entry "Shares" in the Odoo's portal
-
For single-view purposes, shares support hierarchy so as to make comfortable navigation by those
-
Share users can download any shared file, a whole share, a particular directory, or a tag as a ZIP archive
-
Optionally let upload files to the selected or default folder. Files drag and drop is supported
-
Users are always allowed to search attachments by title, linked folder, and tags
-
Optionally allow navigation by folders and/or tags. Shared tags/folders, their children, and ones linked to shared attachments will be available
-
Let users add tags and folders by themselves. Show/hide searching items in tags/folders navigation trees
-
Turn on/off a chat per each share.
Document Management and Sync Access Rights
-
Access for each Odoo automatic folder is regulated based on a linked object. If such an Odoo object is available for a specific user, its directory would be also available for her/him. For example, if Anita Olivier is the task manager of 'Prepare specification', then she may access the folder 'Tasks' and 'Tasks > Prepare Specification'
-
Access to Odoo manual folders is regulated based on its user groups and users stated in those folders' settings. If nobody is specified, a manually created folder is available for everyone. For example, if Anita Oliver is a sales manager, she may access the quotation-related folder 'Odoo > Orders > SO-001'
-
To access any folder, a user should be able to access all its parents. For example, if Anita Oliver has rights for employees but does not have for departments, then she might not read 'Odoo > Departments > Administration > Employees > Mitchel Admin'. However, if the folder 'Employees' becomes a stand-alone folder without a parent, then Anita would be able to access 'Odoo > Employees > Mitchel Admin'
-
The app does not regulate access levels for cloud clients and their items. The tool regulates rights only for Odoo objects and synchronizes those to required storage. After the sync, if necessary, you should apply the settings for a target cloud client, folders, and files
-
To observe the menu 'Cloud Storage' and the app file manager, a user should belong to the security group 'Cloud Storage > File Manager Access'
-
To configure automatic folder rules, establish connections with various cloud clients, control sync logs, and apply the app settings, a user should belong to the security group 'Cloud Storage > Administration'.
Use Notes
-
The app assumes automatic regular synchronization with various cloud clients. Please take into account that synchronization is not real-time but is based on tasks queue and scheduled jobs. Depending on the number of folders and attachments, it might take time for the app to check all directories and do the jobs. That's why, until the sync is done, Odoo attachment interfaces work as in standard Odoo.
-
Cloud connections rely upon the API of the related cloud clients. Such communication between systems is risky by concept due to possible disconnections, API updates, and unsolvable conflicts. The app is designed to cope with such risks by carefully processing failures and checking cloud client states. Simultaneously, make sure that you have configured a proper backup strategy for both Odoo and cloud clients.
-
The special factors of risks are sync scope and reverse operations. The higher the sync scope is, the more it would take Odoo to finish integrations. Hence, more space for errors exists. Try to decrease sync scope logically by choosing only required folders. Reverse operations might be risky since assume reflecting cloud clients' features which might be absent in Odoo. For example, Google Sheets cannot be opened outside Google Docs. The app would try to solve the scenarios by applying similar features (e.g. by converting a file to simple electronic tables). However, that is not always possible, and in this way, manual interactions would be required.
Consejos de configuración e instalación para Cloud Storage Solutions Odoo v.17
Odoo server configuration
To make sure the synchronization works correctly apply proper timeouts to the Odoo configuration file: LIMIT_TIME_CPU, LIMIT_TIME_REAL, LIMIT_TIME_REAL_CRON should be more than 900 seconds.
For Odoo.sh this should not be done, since timeouts are predefined and are not configurable.
Avoid also changing the cron jobs frequency assumed by the app: '[Cloud Storage] Prepare Cloud Folders', '[Cloud Storage] Run / Prepare sync queue'. Those jobs are configured to be run each 15 minutes, and that frequency is used in the algorithms to avoid breaks and data losses. If you need to stop sync for a while, pause particular cloud clients instead.
General Python dependency
The tool depends on the external library 'sortedcontainers'. Install this library for your Odoo server through the command:
pip3 install sortedcontainersSetting up OneDrive or/and SharePoint Integration
Python dependency
The tool depends on the external library 'microsoftgraph'. Install this library for your Odoo server through the command:
pip3 install microsoftgraph-python
Configuration and log in
- Turn on the option 'OneDrive / SharePoint Sync' (cloud Storage > Configuration > Configuration). The optional add-on OneDrive / SharePoint Odoo Integration is required
- Make sure your Microsoft user has full admin rights for OneDrive / SharePoint you want to connect to Odoo. This user is required only to grant permissions, the user data would not be kept in Odoo, and would not be used afterward. Besides, make sure a Microsoft email address you use does not have a redirection (usually happens when you configure your domain name, while the prime address is still one of Microsoft domains like @outlook.com, @office365, etc.)
- Go to your Azure Portal: https://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade
- Click 'New registration'
- Introduce a new name for the application and assign the redirect URI as [YOURODOOSITENAME]/one_drive_token (e.g. https://odootools.com/one_drive_token). As the supported account types choose 'Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)'.
- Go to Certificates & secrets - Click 'New Client Secret'. Save somewhere the secret value
- Go to Odoo Cloud Storage > Configuration > Cloud Clients press 'Create'
- As a reference introduce any name which would be clear to all users
- As a Cloud client choose 'OneDrive' or 'SharePoint' depending on the software you are using
- As a Root folder name enter a title which would be users as the parent OneDrive directory for all synced folders. For example, 'Odoo' or 'OdooERP'
- Copy 'Application Client ID' to the 'App client ID'
- Copy secret value into the field 'App client secret'
- Insert previously generated redirect URL
- If you use SharePoint:
- Go to your SharePoint site and prepare a new documents library (drive). You might use one of the existing ones, e.g. 'Documents'. Odoo folder would be put there afterward, and it would be impossible to move it to another library
- The SharePoint URL should be of the type https://[URL]/. The last '/' is required - the site name should not be included. For example, https://odootools.sharepoint.com/
- SharePoint site should be either root (the very root SharePoint site), my_site_name (in that case it is considered as sites/my_site_name) or sites/my_site_name (instead of 'sites' it might be 'teams' and so on). There should be no '/' at the beginning or at the end. For example, sites/odootools
- As Documents Library use one created in SharePoint
- Press 'Confirm'. Odoo redirects you to the Microsoft login page. Check in the system, agree with all conditions, and grant all permissions asked
- After login, OneDrive redirects you back to Odoo. OneDrive - Odoo synchronization is ready to be done
- Apply the newly created cloud client to folder rules and/or manual folders which should be synced to that OneDrive or SharePoint instance
- Await the sync scheduled job to be started. For testing purposes only: trigger integration manually from Cloud Storage > Configuration > Configuration > the button 'Launch sync'.
Watch also the configuration video
Create Azure application
New OneDrive Web platform and redirect URL
Generate new secret for Azure application
Enter configuration keys in Odoo
Setting up Google Drive Integration
- Turn on the option 'Google Drive Sync' (cloud Storage > Configuration > Configuration). The optional add-on Google Drive Odoo Integration is required
- Go to the Google Developer Console via the url https://console.developers.google.com
- Select or create a project
- Find the section 'Dashboard' and press 'ENABLE APIS AND SERVICES'
- Find Google Drive API and push the button to enable its API
- Go to 'Credentials' and press the button 'Configure Consent Screen'. As the User Type select 'External' and push 'Create'
- Add app information
- As an app name select any suitable
- As a user support email and developer contact information select your email address
- Press 'Save and Continue'
- On the 'Scopes' page just press 'Save and Continue'
- As Test Users add your GMail email address, then press 'Save and Continue'
- Then, go to Credentials and push the button 'Create Credentials'
- 'Web application' as the application type
- As the authorized redirect URI add the link in a format [YOURODOOSITENAME]/google_drive_token (e.g. https://odootools.com/google_drive_token).
- Save the app and copy 'Client ID' and 'Client Secret'
- Go to Odoo Cloud Storage > Configuration > Cloud Clients press 'Create'
- As a reference introduce any name which would be clear to all users
- As a Cloud client choose 'Google Drive'
- As a Root folder name enter a title which would be users as the parent Google Drive directory for all synced folders. For example, 'Odoo' or 'OdooERP'
- Copy 'Client ID' to the 'App client ID'
- Copy 'Client Secret' into the field 'App client secret'
- Insert previously generated redirect URL
- If you use team drives, check the related box. Make sure you really use team drives. In you Google Drive you should find the item 'Team Drives' in the left sidebar. This feature is available only for business and enterprise tariffs
- If the option 'Team Drive' is enabled, introduce its name. It should be absolutely the same as you see it in your Google Drive. Make sure that your user has full rights for all Google drives (usually, it is the same user who configures your team Google Drive)
- Press 'Confirm'. Odoo redirects you to Google login page. Check in the system, agree with all conditions, and grant all permissions asked
- After login, Google redirects you back to Odoo. Google Drive - Odoo synchronization is ready to be done
- Apply the newly created cloud client to folder rules and/or manual folders which should be synced to that Google Drive
- Await the sync scheduled job to be started. For testing purposes only: trigger integration manually from Cloud Storage > Configuration > Configuration > the button 'Launch sync'.
Watch also the configuration video
Google Console: APIs
Google Drive API
Enable Google Drive API
Configuring Google Consent Screen
Setting up External User Type API
Entering Google app details
Google app scopes
Adding authorized users
Creating Google app credentials
Google Drive app redirect URL
Copy app credentials
Enter Google app credentials to Odoo
Setting up Amazon S3
- Turn on the option 'Amazon S3 Sync' (Cloud Storage > Configuration > Configuration). The optional add-on Amazon S3 Odoo Integration is required
- Open the Amazon S3 Console: https://console.aws.amazon.com/s3/
- Create a new bucket or choose an existing one. Copy the exact bucket name: it should be inserted in Odoo into the field 'Bucket'
- Open the bucket details and copy its AWS Region. Insert it in Odoo into the field 'Region' (for example, eu-west-1 or us-east-1)
- Open the AWS IAM Console: https://console.aws.amazon.com/iam/
- Create a new IAM user or choose an existing technical user. This user should have full rights to list, read, create, write, copy, and delete objects within the selected bucket. You can select the full right admin, or create a new policy (see below)
- In the IAM user form, open the tab 'Security credentials' and press 'Create access key'
- On the page 'Access key best practices & alternatives', select the option Application running outside AWS. This is the correct option when your Odoo server connects to S3 by access key from outside AWS, from Odoo.sh, from your own server, or from another hosting provider. If your Odoo is installed on an AWS EC2 instance, you may instead select Application running on an AWS compute service, but the fields copied to Odoo are the same
- Press 'Next'. On the next step, optionally enter a description tag such as Odoo S3 Sync, then press 'Create access key'
- On the final AWS page, copy Access key or Access key ID into the Odoo field 'Access Key'
- Copy Secret access key into the Odoo field 'Secret Key'. Important: AWS shows the secret key only once, so save it before closing the window
- If you use an S3-compatible provider instead of AWS S3, copy the endpoint URL from that provider's admin panel and insert it into Odoo into the field 'Amazon S3 endpoint URL'. For example, MinIO often uses a URL like https://minio.example.com or http://localhost:9000; LocalStack commonly uses http://localhost:4566
- Go to Odoo Cloud Storage > Configuration > Cloud Clients and press 'Create'
- As a reference, introduce any name which would be clear to all users
- As a Cloud client, choose 'Amazon S3'
- As a Root folder name, enter a title that will be used as the parent S3 prefix for all synced folders. For example, 'Odoo' or 'OdooERP'
- Fill in the fields 'Bucket', 'Region', 'Access Key', 'Secret Key', and, if needed, 'Amazon S3 endpoint URL' and addressing style
- Choose whether Odoo should use temporary presigned URLs or public bucket/CDN URLs. For private buckets, keep presigned URLs enabled and set their lifetime in seconds
- Press 'Confirm'. Odoo checks bucket access and creates or verifies the root folder prefix. Amazon S3 - Odoo synchronization is ready to be done
- Apply the newly created cloud client to folder rules and/or manual folders which should be synced to that Amazon S3 bucket
- Await the sync scheduled job to be started. For testing purposes only: trigger integration manually from Cloud Storage > Configuration > Configuration > the button 'Launch sync'.
Useful AWS documentation: creating an S3 bucket: https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-bucket.html, managing IAM access keys: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html.
Bucket policy example
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "ListObjectsInBucket",
"Effect": "Allow",
"Action": [
"s3:ListBucket"
],
"Resource": "arn:aws:s3:::NAME_OF_YOUR_BUCKET"
},
{
"Sid": "AllObjectActions",
"Effect": "Allow",
"Action": [
"s3:GetObject",
"s3:PutObject",
"s3:DeleteObject"
],
"Resource": "arn:aws:s3:::NAME_OF_YOUR_BUCKET/*"
}
]
}
Create a new AWS IAM user
Specify the IAM user name
Attach permission policies directly
Amazon S3 bucket policy JSON example
Review and name the S3 policy
Select the bucket policy for the user
Review and create the IAM user
Create an access key for the user
Choose the access key use case
Set the access key description tag
Retrieve the access key and secret
Configure the Amazon S3 client in Odoo
Setting up Nextcloud or/and ownCloud Integration
Configuration and log in
- Turn on the option 'onwCloud / Nextcloud Sync' (cloud Storage > Configuration > Configuration). The optional add-on ownCloud / Nextcloud Odoo Integration is required
- Go to Odoo Cloud Storage > Configuration > Cloud Clients press 'Create'
- As a reference introduce any name which would be clear to all users
- As a Cloud client choose 'Nextcloud' or 'ownCloud' depending on the software you are using
- As a Root folder name enter a title which would be users as the parent directory for all synced folders. For example, 'Odoo' or 'OdooERP'
- Enter your ownCloud / Nextcloud full URL
- Select an ownCloud / Nextcloud user, which has full rights to read, create, write and delete files and folders within a root directory
- Enter login and password of this user to the fields 'Login' and 'Password'
- Choose whether you would like to apply public or internal URLs (see below)
- Press 'Confirm'. Odoo synchronization is ready to be done
- Apply the newly created cloud client to folder rules and/or manual folders which should be synced to that Nextcloud or ownCloud instance
- Await the sync scheduled job to be started. For testing purposes only: trigger integration manually from Cloud Storage > Configuration > Configuration > the button 'Launch sync'.
Internal and public URLs
By default links from Odoo to ownCloud / Nextcloud are internal: only authorized users may access them. Optionally make links public (the setting 'Use Public URLs'). Then, URLs would be 'shared', and everybody would access items by a direct link.
Be cautious if you decide to use shared (public) URLs. Although the links would be hardly known by external users, there is a slight chance that they become available as a result of some user actions. Besides, sharing links generation is not fast and might make the synchronization slower.
Watch also the configuration video
Enter ownCloud / Nextcloud credentials
Setting up NAS (Synology, QNAP, TrueNAS, etc.)
- Turn on the option 'NAS Sync' (Cloud Storage > Configuration > Configuration). The optional add-on NAS Odoo Integration is required
- Prepare your NAS WebDAV endpoint:
- Synology: install and enable WebDAV Server in DSM and choose HTTPS where possible
- QNAP: enable WebDAV for the target shared folder and use HTTPS where possible
- TrueNAS CORE: enable the WebDAV service; TrueNAS SCALE: install and configure the WebDAV app, since native WebDAV was removed in modern SCALE releases
- Generic WebDAV: make sure PROPFIND, MKCOL, PUT, GET, MOVE, and DELETE are available
- If Odoo is hosted outside the local NAS network, make the WebDAV endpoint reachable securely. Prefer a reverse proxy with a valid TLS certificate, a VPN/secure tunnel such as WireGuard, Tailscale, or Cloudflare Tunnel, or a vendor relay such as Synology QuickConnect or QNAP myQNAPcloud. Avoid exposing an administrator interface to the Internet
- Create a dedicated NAS user with full rights only inside the target shared folder: read, create, write, move, and delete. Do not use an administrator account
- Go to Odoo Cloud Storage > Configuration > Cloud Clients and press 'Create'
- As a reference, introduce any name which would be clear to all users
- As a Cloud client, choose 'Synology NAS', 'QNAP NAS', 'TrueNAS', or 'WebDAV NAS'
- As a Root folder name, enter a title that will be used as the parent NAS directory for all synced folders. For example, 'Odoo' or 'OdooERP'
- Enter the full WebDAV URL, login, and password. Optionally define a base path if Odoo should create the root folder inside an existing share or directory
- Keep 'Verify SSL' enabled for public HTTPS endpoints. Disable it only for a trusted private endpoint with a self-signed certificate
- Optionally define a browser base URL if NAS files should be opened through a vendor file station URL instead of the raw WebDAV URL
- Press 'Confirm'. Odoo checks the WebDAV connection and creates or finds the root directory. NAS - Odoo synchronization is ready to be done
- Apply the newly created cloud client to folder rules and/or manual folders which should be synced to that NAS storage
- Await the sync scheduled job to be started. For testing purposes only: trigger integration manually from Cloud Storage > Configuration > Configuration > the button 'Launch sync'.
NAS Pre-configuration
NAS systems usually expose files through a local network. If your Odoo server is hosted outside that network, the WebDAV endpoint should be reachable from Odoo through a secure channel. Recommended options are a reverse proxy with a valid HTTPS certificate, a VPN or secure tunnel such as WireGuard, Tailscale, or Cloudflare Tunnel, or a vendor relay such as Synology QuickConnect or QNAP myQNAPcloud. Plain port forwarding is possible but should be treated as the least preferred option.
Use a dedicated NAS user with the minimum required rights to one shared folder: read, create, update, move, and delete. Avoid administrator accounts. Publicly exposed endpoints should always use HTTPS and a valid TLS certificate. The connector has a "Verify SSL" option for trusted self-signed certificates, but it should normally remain enabled.
Enter QNAP credentials
Enter Synology credentials
Enter TrueNAS credentials
Setting up Box
- Turn on the option 'Box Sync' (cloud Storage > Configuration > Configuration). The optional add-on Box Odoo Integration is required
- Create or open a Box developer account and go to the Box Developer Console: https://app.box.com/developers/console
- Create a Custom App and choose OAuth 2.0 (Authorization Code Grant) as the authentication method
- Add the redirect URI as [YOURODOOSITENAME]/box_token (e.g. https://faotools.com/box_token). A valid SSL certificate (https) is required
- Grant the app access to read and write files and folders. Avoid assigning unrelated permissions
- Go to Odoo Cloud Storage > Configuration > Cloud Clients and press 'Create'
- As a reference, introduce any name which would be clear to all users
- As a Cloud client, choose 'Box'
- As a Root folder name, enter a title that will be used as the parent Box directory for all synced folders. For example, 'Odoo' or 'OdooERP'
- Copy Box Client ID to the field 'Client ID'
- Copy Box Client Secret to the field 'Client Secret'
- Insert previously generated redirect URL
- Press 'Confirm'. Odoo redirects you to the Box login page. Check in the system, agree with all conditions, and grant all permissions asked
- After login, Box redirects you back to Odoo. Box - Odoo synchronization is ready to be done
- Apply the newly created cloud client to folder rules and/or manual folders which should be synced to that Box account
- Await the sync scheduled job to be started. For testing purposes only: trigger integration manually from Cloud Storage > Configuration > Configuration > the button 'Launch sync'.
Create a new Box developer app
Copy Box OAuth credentials
Configure the Box cloud client in Odoo
Grant Odoo access to Box
Setting up Dropbox Integration
Python dependency
The tool depends on the external library 'dropbox'. Install this library for your Odoo server through the command:
pip3 install dropbox
Configuration and log in
- Turn on the option 'Dropbox Sync' (cloud Storage > Configuration > Configuration). The optional add-on Dropbox Odoo Integration is required
- Follow the URL https://www.dropbox.com/developers/apps/create
- Choose an API as 'Scoped access'
- Choose the type of access as 'Full Dropbox'
- Select any suitable name for the app and push the button 'Create app'
- Add the redirect URI as [YOURODOOSITENAME]/dropbox_token (e.g. https://faotools.com/dropbox_token). A valid SSL certificate (https) is required
- Grant permissions to the app: 'Account Info (Read)', 'Files and folders Metadata (Write)', 'Files Content (Write)', 'Collaboration (Write)'. For team DropBox assign also 'Team Data Members', 'Members (Read)'. Make sure no other permissions are assigned.
- Submit App
- Go to Odoo Cloud Storage > Configuration > Cloud Clients press 'Create'
- As a reference introduce any name which would be clear to all users
- As a Cloud client choose 'Dropbox'
- As a Root folder name enter a title which would be users as the parent Google Drive directory for all synced folders. For example, 'Odoo' or 'OdooERP'
- Copy 'App key' to the 'App key'
- Copy 'App Secret' into the field 'App secret'
- Insert previously generated redirect URL
- If you use Dropbox team drives
- Check the related box
- Set an email of the Dropbox user. Inside this user folder, all Odoo related items would be created, and only after that they are shared with all other users. Under this user, all files and folders are created, changed, moved, and deleted
- Press 'Confirm'. Odoo redirects you to the Dropbox login page. Check in the system, agree with all conditions, and grant all permissions asked
- After login, Dropbox redirects you back to Odoo. Dropbox - Odoo synchronization is ready to be done
- Apply the newly created cloud client to folder rules and/or manual folders which should be synced to that Dropbox instance
- Await the sync scheduled job to be started. For testing purposes only: trigger integration manually from Cloud Storage > Configuration > Configuration > the button 'Launch sync'.
Dropbox URLs
Dropbox has a specific way to generate links for existing files and folders. In particular, there are no concepts of internal or private URLs. Instead, each Dropbox item might get so-called shared URLs. Such shared links are either public or team-only. Moreover, the latter feature is available only for the Dropbox business account.
This tool relies upon shared links' mechanics. It means, that each attachment link is either public (all personal Dropbox accounts) or team-only (all business Dropbox accounts).
Sometimes it is considered to be not fully safe. Although website URLs will be hardly known by external users, there is a slight chance that they become available as a result of some user actions. Besides, sharing links generation is not super fast and might make the sync process slower. That is why the feature to switch off sharing URLs is introduced.
If checked, all Dropbox URLs in Odoo will be of type https://www.dropbox.com/home/Odoo/[PATH]. Such links will not work in many cases. Thus, if you need to open Dropbox files/folders from Odoo, be careful with the setting 'No links to Dropbox from Odoo'.
Watch also the configuration video
Create Dropbox app
Set up Dropbox App: redirection URL
Dropbox permissions for personal accounts
Dropbox permissions for business accounts
Set up Odoo for Dropbox integration
Setting up MinIO
- Prepare a running MinIO server
- Open the MinIO Console
- Create a new bucket or choose an existing one. Copy the exact bucket name: it should be inserted in Odoo into the field 'Bucket'
- Create access credentials for Odoo. In MinIO, use an access key / secret key pair or a service account that has rights to list, read, create, write, copy, and delete objects within the selected bucket
- Copy the MinIO Access Key into the Odoo field 'Access Key'
- Copy the MinIO Secret Key into the Odoo field 'Secret Key'. Important: save the secret before closing the MinIO page if MinIO shows it only once
- Copy the MinIO S3 API endpoint URL into Odoo into the field 'Amazon S3 endpoint URL'. For example, a local server usually uses http://localhost:9000, while a production server may use https://minio.example.com
- Go to Odoo Cloud Storage > Configuration > Cloud Clients and press 'Create'
- As a reference, introduce any name which would be clear to all users
- As a Cloud client, choose 'MinIO'
- As a Root folder name, enter a title that will be used as the parent MinIO object prefix for all synced folders. For example, 'Odoo' or 'OdooERP'
- Fill in the fields 'Bucket', 'Access Key', 'Secret Key', and 'Amazon S3 endpoint URL'. The field 'Region' is optional for MinIO; if it is empty, Odoo uses us-east-1 for S3-compatible signing
- Keep the addressing style as Path-style. This is the recommended option for MinIO endpoints, especially when the MinIO host does not provide bucket-specific DNS names
- Choose whether Odoo should use direct public MinIO URLs. Enable 'Use Public URLs' only when the bucket, prefix, reverse proxy, or CDN is publicly readable. For private MinIO buckets, leave it disabled
- Press 'Confirm'. Odoo checks bucket access and creates or verifies the root folder prefix. MinIO - Odoo synchronization is ready to be done
- Apply the newly created cloud client to folder rules and/or manual folders which should be synced to that MinIO bucket
- Await the sync scheduled job to be started. For testing purposes only: trigger integration manually from Cloud Storage > Configuration > Configuration > the button 'Launch sync'.
Useful MinIO documentation: https://min.io/docs/minio/linux/administration/identity-access-management.html, https://min.io/docs/minio/linux/reference/minio-server/minio-server.html.
Create a MinIO access key
Copy the new MinIO credentials
Configure the MinIO cloud client in Odoo
Preguntas frecuentes sobre Cloud Storage Solutions Odoo v.17
¿Dónde se almacenan los archivos sincronizados? ¿Se duplican en Odoo y en las nubes?
La aplicación asume que el contenido binario de los adjuntos se guarda en el Cloud Client en lugar del servidor Odoo. Esos adjuntos en Odoo pasan a ser de tipo URL y puede acceder a ellos en cualquier momento desde el recuadro de adjuntos o desde el Cloud Client.
Tras la configuración no se requieren acciones manuales: la sincronización es totalmente automática. Decida qué tipos de documento de Odoo sincronizar y configure un modelo relacionado para cada uno (clientes, pedidos de venta o compra, tareas, proyectos, etc.).
¿Puedo tener varias carpetas para el mismo tipo de documento? Por ejemplo, proyectos internos y proyectos de clientes?
Sí, puede. Para ello, prepare una regla para cada una y aplique filtros: por ejemplo, por tipo de proyecto.
Haga que los filtros se excluyan entre sí para que un documento se asigne con certeza. Por ejemplo: «cliente pero no proveedor», «proveedor pero no cliente». Si no, la carpeta de un documento saltaría de un modelo a otro.
¿Es posible hacer la sincronización en tiempo real?
No. Tenemos razones de peso para evitar la sincronización en tiempo real:
Rendimiento. Si la sincronización es en tiempo real, cada subida de archivo muestra la pantalla de carga.
Conflictos. Si 2 usuarios cambian un elemento a la vez, la situación puede no resolverse. Con trabajos regulares se puede corregir después; en tiempo real habría que guardar una cola, aún más confusa.
Funcionalidad. En concreto, renombrar y reestructurar. La sincronización inversa se basa estrictamente en la lógica de directorios y en cada sincronización se comprueba el 100 % de los elementos. Tras cada actualización serían miles de peticiones por segundo. Si no, se perderían los cambios.
¿Puedo cambiar el nombre predeterminado de las carpetas en las nubes?
Puede asignar su nombre a los directorios de modelos (pedidos de venta, oportunidades, proveedores, etc.) para cualquier tipo de documento.
Para las carpetas de objetos (SO-001, John Smith, etc.), la herramienta usa el método de Odoo que construye el nombre visible. Puede cambiarlo definiendo una expresión de nombre. Se usa la sintaxis de las plantillas de correo de Odoo.
¿Puedo cambiar la frecuencia de los trabajos de sincronización?
No, desde la versión 15 no debe cambiar las acciones planificadas. Están optimizadas para ejecutarse cada 15 minutos y garantizar la conexión más estable y rápida.
Los tiempos de espera del servidor Odoo deben ser de al menos 15 minutos (900 segundos).
Si necesita detener la sincronización un tiempo, hágalo en el formulario del cliente cloud concreto.
Puedo sincronizar adjuntos con varios clientes cloud
Sí, desde la versión 15 puede configurar varias conexiones. Así se pueden sincronizar unas carpetas con un cliente cloud y otras con otro.
Tenga en cuenta que no es posible sincronizar la misma carpeta con varios almacenamientos cloud a la vez.
Usamos un editor especial en nuestras nubes (p. ej. OnlyOffice, Office 365, etc.). ¿Se abrirían los archivos en ese editor?
Sí, según la configuración de su cliente cloud.
¿Necesito solo la aplicación Cloud Storage Solution?
Desde la versión 15 la aplicación puede usarse sola para estructurar adjuntos en carpetas y ofrecer una interfaz de gestor de archivos.
Si el objetivo es conectar con uno de sus clientes cloud, hay que instalar al menos una aplicación opcional del cliente.
¿Qué ocurre cuando cambio una regla de carpeta?
Cuando cambia una regla de carpeta, cambia también la lista de carpetas. Si una carpeta deja de cumplir las condiciones, se elimina. Si los archivos ya estaban sincronizados, la sincronización inversa los devuelve a Odoo y los borra del Cloud Client.
Si el objeto del documento no cumple la regla de carpeta, no se crea su carpeta. Si más adelante sí la cumple, se generará la carpeta relacionada.
Cuales son las politicas de actualizacion de sus herramientas?
Segun las politicas actuales de Odoo Apps Store:
- Cada modulo comprado para la version 12.0 o anterior da acceso a todas las versiones hasta 12.0.
- A partir de la version 13.0, cada version del modulo se compra por separado.
- Sea cual sea la version, la compra da derecho a todas las actualizaciones y correcciones dentro de una version mayor.
El equipo de faOtools no controla esas politicas. Para cualquier duda, contacte directamente con los representantes de Odoo Apps Store.
Como instalo su aplicacion en Odoo.sh?
La via mas directa es el flujo integrado de la tienda Odoo:
1. Abra la pagina del modulo y pulse Deploy on odoo.sh
2. Sera redirigido a GitHub. Inicie sesion y pulse Create a new repo o use uno existente. El repositorio debe ser privado. No esta permitido publicar las apps con licencia OPL-1. Cree un repo nuevo para el proyecto Odoo.sh si hace falta
3. Luego, en odoo.sh, pulse Deploy, confirme y pulse Continue. Se inicia la instalacion.
Estos pasos instalan la app en la rama de produccion. Para otras ramas o para actualizar:
1. Descargue el codigo fuente de la tienda Odoo
2. Haga commit del modulo en el repositorio GitHub. Ninguna carpeta/archivo de la app debe estar en .gitignore. Los repos creados por odoo.sh a veces ignoran rutas importantes (p. ej. /lib). Suba todos los directorios y archivos del modulo
3. Despliegue la rama destino del proyecto odoo.sh o espere la compilacion automatica si asi esta configurado.
Como instalo su aplicacion en mi propio servidor?
2. Reinicie el servidor Odoo;
3. Active el modo desarrollador (ajustes tecnicos);
4. Actualice la lista de aplicaciones (menu Aplicaciones);
5. Encuentre la app y pulse Activate/Install;
6. Siga las pautas de la pagina de la app si existen.
Su app tiene complementos extra. Puedo comprarlos despues?
Si. Odoo anade automaticamente las dependencias al carrito: excluya las herramientas ya compradas para no pagar dos veces.
Desplegue su app en Odoo.sh y veo un aviso/error en las pruebas
Un aviso rojo/naranja no afecta a las funciones de la app. A veces nuestros modulos no pasan las pruebas automaticas estandar porque estas asumen un comportamiento que choca con los objetivos de la app. Por ejemplo, cambiamos el calculo del precio y las pruebas de Odoo comparan el precio final con el algoritmo estandar.
Compruebe primero las funciones de la base desplegada. Funciona todo correctamente?
Si aun cree que el aviso afecta a funciones reales, contactenos y envie los registros completos de instalacion y la lista completa de modulos desplegados (nucleo y de terceros).
Puedo comprar su aplicacion directamente a su empresa?
No, solo distribuimos las herramientas a traves de la tienda oficial de aplicaciones Odoo.
Quiero un descuento
Lamentablemente, no tenemos medios tecnicos para ofrecer precios individuales.
Puedo instalar la app en mi base Odoo Online (SaaS)?
No, las apps de terceros no se pueden usar en Odoo Online. Odoo SaaS bloquea esa posibilidad.
Su herramienta depende de otras apps. Debo comprarlas?
Si, la herramienta necesita todos los modulos marcados como dependencias. El precio de la pagina de la app ya las incluye.
Cual es el precio del modulo en dolares estadounidenses? Por que cambio?
El precio de nuestros modulos esta en euros. La tienda Odoo convierte a otras monedas segun su tipo de cambio interno. Por eso el precio en dolares estadounidenses puede cambiar cuando se actualiza el tipo.
La redacción de la aplicación y el sitio web en idiomas distintos del inglés cuenta con asistencia de IA y se ajusta a las traducciones oficiales de Odoo. Si detecta un error, enviar un ticket de traduccion y lo corregiremos.
Bases de datos de demostración de Odoo (vistas previas)
Para esta aplicación, podemos proporcionar una base de datos de demostración personalizada gratuita.
No necesita un número de teléfono ni una tarjeta de crédito para contactarnos. Sólo debes pasar un breve registro por correo electrónico, que no lleva más de 30 segundos.
A petición suya, preparamos una base de datos de vista previa individual en la que puede realizar cualquier prueba y comprobar sus hipótesis durante unas dos semanas.
Notificación de errores
Si encuentra errores o comportamiento inconsistente, no dude en contactarnos. Garantizamos proporcionar correcciones dentro de los 60 días posteriores a la compra y estamos muy interesados en mejorar nuestras herramientas incluso después de este período.
No necesita un número de teléfono ni una tarjeta de crédito para contactarnos. Sólo debes pasar un breve registro por correo electrónico, que no lleva más de 30 segundos.
Incluya tantos detalles como sea posible en su solicitud: capturas de pantalla, registros del servidor Odoo, una descripcion completa de como reproducir el problema, etc. Por lo general, se necesitan varios dias laborables para preparar un plan de trabajo para un problema (si se confirma un error) o proporcionarle indicaciones sobre lo que se debe hacer (en caso contrario).
Solicitudes de funciones públicas e ideas de módulos (desarrollo gratuito)
Estamos muy motivados para mejorar nuestras herramientas y agradeceríamos cualquier comentario. Si sus requisitos son de uso público y podrían implementarse de manera eficiente, el equipo los incluirá en nuestra lista de tareas pendientes.
Esta lista de tareas pendientes se procesa periódicamente y no implica cargos adicionales. Aunque no podemos prometer plazos ni diseño final, podría ser una buena manera de conseguir las funciones deseadas sin inversiones ni riesgos.
No necesita un número de teléfono ni una tarjeta de crédito para contactarnos. Sólo debes pasar un breve registro por correo electrónico, que no lleva más de 30 segundos.
17.0.1.4.48
- Optimized folder sync by searching only attachments of updated records instead of all model attachments.
17.0.1.4.47
- The feature to requeue failed tasks has been added.
17.0.1.4.46
- Support for Amazon S3, MinIO S3, Synology, QNAP, TrueNAS, other NAS/WebDAB, and BOX has been added.
17.0.1.4.45
- The feature to control the maximum number of folders per rule has been added.
17.0.1.4.44
- The issue fix text break in folder titles has been fixed.
17.0.1.4.43
- The issue with the non-synced invoice report has been fixed.
17.0.1.4.42
- The asynchronous folder check has been optimized.
17.0.1.4.41
- The issue with a newly selected folder search has been fixed.
17.0.1.4.40
- The issue with the non-refreshing folder tree while switching between records has been fixed.
17.0.1.4.39
- The issue with the double click needed to remove selected attachments has been fixed.
17.0.1.4.38
- The backup removal queue has been changed to first-in, first-out.
17.0.1.4.37
- The app is adapted to the new domain logic to support dynamic parts.
17.0.1.4.36
- The filestore evaluation is added to the configuration page.
- The feature to restrict cloud client sync to a particular database name has been added.
17.0.1.4.35
- The feature to lock backup creation has been added.
17.0.1.4.34
- The issue with the untranslated warnings has been fixed.
17.0.1.4.33
- The feature to automatically and manually sync a current database backup to chosen cloud clients has been added. Configure the backup schedule and keep time. Backups might be with or without filestore and manifest.
17.0.1.4.32
- The domain now supports Python libraries' use, including datetime ('date', 'datetime', 'time', 'timedelta', 'timezone', 'tzinfo', 'MAXYEAR', 'MINYEAR'), time ('time', 'strptime', 'strftime'). Also, context_today (short for datetime.now) and relativedelta might be applied.
17.0.1.4.31
- Attachments are unselected after deletion.
17.0.1.4.30
- The synced attachments' URLs might be precalculated.
17.0.1.4.29
- Folders created based on cloud clients get increased sequence.
17.0.1.4.28
- The archived ribbon for inactive records is added to form views of rules, folders, tags, and shares.
17.0.1.4.27
- The interface is updated to reflect the core attachment list view changes.
17.0.1.4.26
- The issue with not added links to certain folders is fixed.
17.0.1.4.25
- Se crean de nuevo las subcarpetas de padres ligados a espacios de trabajo.
17.0.1.4.24
- Se ha corregido la actualizacion de subcarpetas ya sincronizadas.
17.0.1.4.23
- Se pueden borrar las fechas de bloqueo de carpetas de reglas.
17.0.1.4.22
- Al redactar mensajes de Odoo se pueden elegir adjuntos existentes, tambien los sincronizados.
- Se anaden adjuntos URL a la caja de adjuntos y al gestor de archivos.
17.0.1.4.21
- Se ha corregido el desplazamiento automatico al registrar una nota.
17.0.1.4.20
- Los registros se pueden filtrar por fecha y hora.
- En la configuracion se define cuantos registros se exportan.
17.0.1.4.19
- El numero de reintentos es configurable y puede diferir entre tareas estandar y reverse/move.
17.0.1.4.17
- El bloqueo padre de tareas atiende primero la de mayor prioridad.
17.0.1.4.15
- Se precisa el bloqueo de las operaciones de sync al mover elementos.
17.0.1.4.13
- El acceso a una carpeta intermedia de regla se basa en la carpeta padre, no en el modelo de la regla.
17.0.1.4.12
- El tamano maximo de las URL sube a 4096.
17.0.1.4.11
- La sync inversa esta optimizada. Se eliminan tareas colgadas por bloqueo mutuo.
17.0.1.4.10
- Se han corregido los problemas de sync inversa y hacia atras a la vez.
17.0.1.4.9
- El proceso de carpetas reordenadas y movidas esta optimizado.
17.0.1.4.8
- Se ha corregido crear etiquetas y carpetas desde el portal.
17.0.1.4.7
- Se ha corregido la busqueda del portal por titulo de etiqueta o carpeta.
17.0.1.4.6
- La accion masiva "Slideshow" abre una presentacion de las imagenes elegidas en el backend.
- La opcion "Allow slideshow" en el recurso compartido deja a portal/publico lanzar una presentacion de las imagenes encontradas.
- El algoritmo de sincronizacion inversa esta optimizado.
17.0.1.4.5
- Hay comprobaciones previas para tareas colgadas. Si una tarea para el cron (p. ej. memoria), el siguiente cron sigue con otra.
17.0.1.4.4
- La vista previa estandar de Odoo esta en la tarjeta de adjunto del gestor. En Kanban, pulse la miniatura. Tipos y comportamiento iguales a la caja de adjuntos.
- Los formularios de adjunto se abren con el menu de tres puntos del Kanban. Alli tambien se cambian los colores.
- Los niveles de los registros de sync se colorean segun el nivel del mensaje.
- El registro guarda mensajes aunque el trabajo falle y detenga el hilo.
17.0.1.4.3
- Se ha corregido la carpeta mal seleccionada al cargar el gestor de archivos.
17.0.1.4.2
- Se pueden priorizar carpetas segun la frecuencia de sync de las reglas.
17.0.1.4.1
- La estructura del modulo se actualiza al nuevo gestor de archivos, arrastrar y soltar y compartir en el portal
17.0.1.3.14
- Se ha corregido duplicar adjuntos con res_model y res_id explicitos (compatibilidad HR Expenses).
17.0.1.3.13
- En el gestor de archivos ya se pueden seleccionar varias carpetas.
- La carpeta actual de subida se muestra en el titulo del boton "Upload".
- Se introduce el compartir adjuntos y carpetas. Comparta archivos, directorios o etiquetas con contactos del portal o en publico. Opcionalmente permita subir, navegar el arbol y crear etiquetas y carpetas.
- Se pueden descargar todos los adjuntos de una etiqueta. La navegacion por etiquetas pasa a ser opcional.
17.0.1.3.12
- Se introduce arrastrar y soltar para subir archivos desde el PC.
- Ya se puede actualizar carpeta y etiquetas soltando adjuntos en el panel izquierdo.
17.0.1.3.11
- Se han corregido los errores al actualizar etiquetas masivamente.
- Se ha corregido la carpeta incorrecta para registros nuevos.
- Ya se puede crear una carpeta en el panel cuando no hay otras.
- La interfaz de registros de sync muestra el HTML de las respuestas recibidas.
17.0.1.3.10
- Se cubre el caso raro en que la configuracion inicial de una carpeta falla 8 veces pero aun debe sincronizarse.
The tool to set up KPI targets and control their fulfillment by periods. KPI dashboards. Dashboard designer. KPI charts
198€The tool to build a deep and structured knowledge base for internal and external use. Knowledge System. KMS. Wiki-like revisions.
398€The tool for time-based service management from booking appointments to sales and reviews
The tool to manage your Odoo from your favorite AI chats through MCP. Claude. Any MCP-supporting AI.
198€The tool to automatically synchronize Odoo attachments with OneDrive files in both ways
The tool to automatically synchronize Odoo attachments with Google Drive files in both ways
The tool to automatically synchronize Odoo attachments with ownCloud/Nextcloud files in both ways
The tool to automatically synchronize Odoo attachments with DropBox files in both ways