OneDrive / SharePoint Odoo Integration v.14
The tool to automatically synchronize Odoo attachments with OneDrive files in both ways
This is the tool to integrate OneDrive / SharePoint features into your Odoo business work flow. The app automatically stores Odoo attachments in OneDrive / SharePoint, and it 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.
- the technical core which provides basic mechanics of auto synchronization. This is a required module for integration.
Its price is
245€
220€.
- the connector itself which introduces links between Odoo and OneDrive / SharePoint.
Its price is
149€
134€.
- an optional add-on to sync Odoo documents (introduced by the enterprise app 'Documents') with clouds. The features assumed by this add-on are marked by the icon . Its price is 44€.
Automatic regular sync
Synchronization between Odoo and OneDrive / SharePoint is based on scheduled jobs. No manual interaction is required
Bilateral OneDrive / SharePoint sync
Odoo sends attachments to OneDrive / SharePoint and retrieves files from there. Binary content is kept in clouds, while Odoo provides direct access to synced items
Any Odoo document types for sync
Decide which Odoo document types should be synced. Customers, opportunities, sale or purchase orders, tasks or issues, employees or users, etc. Custom models are also supported
Instant access for OneDrive / SharePoint
The tool redefines Odoo attachments boxes to make work comfortable: download files locally without login, open files and folders in OneDrive / SharePoint (if possible, items would be opened in OneDrive / SharePoint editors and previewers), use standard Odoo previewers
Compatible with Odoo Enterprise documents
Reflect Odoo Enterprise Documents' structure and items in OneDrive / SharePoint. All features (including sharing, downloading, and signing) would anyway work
Personal OneDrive and SharePoint
Sync works both for personal OneDrives and business SharePoint tariffs
OneDrive / SharePoint sync history
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 you would be able to observe the history through the button 'Sync logs'
Default folders
The tool let generate default directories' structure for this document type during the very first sync of a related object. For example, for all employees you may have pre-defined folders 'Scans', 'Scans/Official', 'Photos', etc.
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.
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.
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.
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.
Sync any documents you like
Configuring models to sync
-
To sync a specific document type, you should add it as a model to sync. Any Odoo model might be chosen
-
The app let split models into a few folders based on selected filters. Use any document storable field to distinguish a directory. Have a separate folder for individuals and companies, for European and American opportunities, for quotations and confirmed orders, for each project, etc.
-
Limit also documents by relative periods through using date fields of linked documents. For example, leads registered in the last 3 months or invoices updated the last week
-
Define name expressions to specify titles of documents' OneDrive / SharePoint folders. For instance, to include project name to a task directory
-
Prepare hierarchy of default folders to be created when a document directory is synced to OneDrive / SharePoint for the first time
Typical use cases
-
Projects: have an own OneDrive / SharePoint folder for each customer project
-
Customers: add all partner files in a single directory available both from Odoo and from OneDrive / SharePoint. Modify those using default cloud editors and access them when working in Odoo
-
Employees: gather all files by this employee in a single cloud folder: photos, document scans, contracts. Access and upload those from Odoo and OneDrive / SharePoint alternatively
-
Opportunities: carefully store all specifications, requirements, any files which would let you make a good offer
-
Orders: keep all printings and contracts in OneDrive / SharePoint with instant availability from Odoo
-
Picking operations: save warehouse docs to OneDrive / SharePoint.
How synchronization works
Direct Sync
-
Direct synchronization is based on the scheduled job 'Synchronize attachments with cloud'
-
Direct sync make all synced Odoo attachments change their type to a link (URL), while binary content is removed with a next Odoo cleaner. So, no actual files would be stored on your Odoo server
-
Direct sync checks whether attachments are added or deleted for synced documents. If so, they would be created or removed in OneDrive / SharePoint
-
Direct sync checks whether a new document type (e.g. sale orders) is added / renamed / replaced in the to-sync-models configurations. If so, this should be reflected in OneDrive / SharePoint
-
Direct sync checks whether a new document (e.g. quotation SO-001) related to a synced document type is generated / updated / unlinked. If so, the connector would make the same changes in OneDrive / SharePoint
-
The final goal of direct OneDrive / SharePoint integration is to have the structure 'Odoo / Document Types / Documents / Files. For example, 'Odoo / Quotations / SO019 / commercial offer.pdf'
Backward Sync
-
Backward synchronization is based on the scheduled job 'Synchronize attachments from cloud'
-
Backward sync checks whether any items are added to a OneDrive / SharePoint document folder. If so, the app would create URL attachments for that items in a linked Odoo object
-
Backward sync checks whether any items are deleted / moved in a cloud document folder. If so, a linked Odoo attachment would be also unlinked or moved
-
Backward sync checks whether any item is renamed in OneDrive / SharePoint. If so, a chained Odoo attachment should be also renamed
-
In OneDrive folders you can put not only files but also child folders. In that case a link for this folder (not its content) would be kept in Odoo attachments
-
If you deleted a folder related to this document type or this document, their child files would be deleted as well. Thus, Odoo would remove related attachments. The folders, however, will be recovered with a next direct sync
Misc notes
-
The connector works on a queue (first in - first out) principle: it tries to firstly reflect the oldest changes
-
Each sync, especially the very first one, might take quite a long. It is not recommended to make sync too frequent: once an hour seems reasonable frequency
-
File names and content should be managed in OneDrive / SharePoint: each backward sync would recover OneDrive / SharePoint names, Odoo is here less important
-
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.
Odoo Enterprise Documents
-
The special add-on 'Cloud Sync for Enterprise documents' is introduced to synchronize OneDrive / SharePoint with the Odoo app 'Documents' (the latter is distributed under the Odoo Enterprise license)
-
Based on that add-on the Odoo documents' hierarchy would be reflected within the folder 'Odoo / Odoo Docs'
-
Each Odoo folder would have a linked OneDrive / SharePoint folder. Take into account that folders created in the cloud storage will be synced as Odoo attachments. The key principle is: folders are managed by Odoo, files are managed by the cloud client
-
All files are synced with the same logic as usual attachments. Files created in Odoo will be added to the cloud storage and will be replaced with links in Odoo. Files created in cloud storage will generate URL attachments within a paired documents directory
-
Standard OneDrive / SharePoint sync and integration with Enterprise Documents are done within the same jobs. Avoid the scenarios when a single file is synced as a simple Odoo attachment and as an Odoo document simultaneously
-
Odoo spread sheet files are not synced by the connector: so, they are still manageable in Odoo
-
Please do not name synced models as 'Odoo Docs'. This is the reserved name for Odoo Enterprise Documents.
Configuration and Installation Tips for OneDrive / SharePoint Odoo Integration Odoo v.14
Python dependency
The tool depends on external libraries 'microsoftgraph'. Install this library for your Odoo server through the command:
pip3 install microsoftgraph-pythonConfiguration and log in
- 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 any where in Odoo, and would not be used any more. 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)'.
- Copy the Application Client ID to the Odoo field 'App client_id'
- Go to Certificates & secrets - Click 'New Client Secret'. Copy the secret value to the Odoo field 'App Secret Key'
- For SharePoint sites only:
- 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 afterwards, and it would be impossible to move it for another library
- Check the boxes 'OneDrive for business' and 'Use SharePoint sites'
- The SharePoint URL should be of the type https://[URL]/. The last '/' is required - site name should not be included into. For example, https://odootools.sharepoint.com/
- SharePoint site should be either 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 Save on the Odoo configuration Page.
- Press 'Login and Confirm'. Odoo redirects you to Microsoft login page. Check in and grant permissions asked.
- After login, Microsoft redirects you back to Odoo. OneDrive - Odoo synchronization is ready to be done.
Create Azure application
New OneDrive Web platform and redirect URL
Generate new secret for Azure application
Enter configuration keys in Odoo
Odoo server configuration and cron job 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.
Then, timeout should be entered to your Odoo. To that goal find the section 'Settings' on the app configuration page and copy the number there.
Afterwards, it is needed to make the cron jobs suit the applied timeouts. In the debug mode go to the Settings > Technical > Automation > Scheduled Jobs:
- Set up the job 'Synchronize attachments with cloud' as (a) frequency - 2*timeout; (b) the next execution as the next hour +timeout. For example, for 900seconds timeout: frequency - as 30minutes; the next execution - at 08:15
- Set up the job 'Synchronize attachments from cloud' as (a) frequency - 2*timeout; (b) the next execution as the next hour + timeout*2. For example, for 900seconds timeout: frequency - as 30minutes; the next execution- at 08:30.
Reconnection
Reconnection is required, when you have not used the sync tool for more than 6 months. In such a case:
- Press the button 'Reconnect'
- Press the button 'Login and confirm'
Frequently Asked Questions about OneDrive / SharePoint Odoo Integration Odoo v.14
The error "This item might have been deleted, expired, or you might not have permission to access it. Contact the owner of this item for more information." indicates that you are not logged in to the service photos.onedrive.com.
Yes, you can. To this end:
Turn on debug mode
Go to technical settings > Automation > Scheduled jobs
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 15 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.
No, this feature is available only from version 15. Prior to that version, the module works with the pre-defined structure of folders:
Odoo - a core folder for sync
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.
Objects - folders for each document, e.g. 'Project 1' or 'Customer 1'
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.
The app assumes that the binary content of attachments is kept in Cloud Client instead of the Odoo server. So, such attachments in Odoo become of the URL type, and you may any time access them either from the attachments box or from the Cloud Client.
After the setup, no manual actions are required, as the synchronization is fully automatic. Just decide which Odoo document types should be synced and set up a related model to sync for each of those (Customers, Sale or Purchase Orders, Tasks, Projects, etc.).
Yes, you can. To that goal, prepare a rule for each, and then 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.
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.
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 is only a technical core. You also need the connector for your cloud client.
For models' directories (sale orders, opportunities, suppliers, etc.): you may assign your own name 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. However, you can change that by defining name_expression. The same syntax as for Odoo email templates is used.
Yes, depending on your cloud client configuration.
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:
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.
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, this feature becomes available only from version 15.
According to the current Odoo Apps Store policies:
- every module bought for version 12.0 and prior gives you access to all versions up to 12.0.
- starting from version 13.0, every module version should be purchased separately.
- disregarding the version, purchasing a tool grants you a right to all updates and bug fixes within a major version.
Take into account that the faOtools team does not control those policies. For all questions, please contact the Odoo Apps Store representatives directly.
The easiest approach is to use the Odoo store built-in workflow:
1. Open the module's page and click the button Deploy on odoo.sh
2. After that, you will be redirected to the GitHub page. Login to your account and click 'Create a new repo' or use the existing one. Please, make sure, that your repository is private. It is not permitted to publish the apps under the OPL-1 license. If necessary, create a new repo for your Odoo.sh project
3. Then, go to odoo.sh and click on the deploy button, submit the decision in the pop-up window and click 'Continue'. The action will trigger the installation process.
These steps will install the app for your project production branch. If you want to deploy the apps for other branches or update the module, you should undertake the following actions:
1. Upload the source code for the app from the Odoo store
2. Commit the module to a required GitHub repository. Make sure that none of the app folders/files are ignored (included in the .gitignore of your repo). Repositories are automatically created by odoo.sh, which might add by default some crucial items there (e.g. /lib). You should upload all module directories, subdirectories, and files without exceptions
3. Deploy a target branch of the odoo.sh project or wait until it is automatically built if your settings assume that.
Unzip the source code of the purchased tools in one of your Odoo add-ons' directories;
Re-start the Odoo server;
Turn on the developer mode (technical settings);
Update the apps' list (the apps' menu);
Find the app and push the button 'Install';
Follow the guidelines on the app's page if those exist.
Yes, sure. Take into account that Odoo automatically adds all dependencies to a cart. You should exclude previously purchased tools.
A 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).
No, we distribute the tools only through the official Odoo apps store
Regretfully, we do not have a technical possibility to provide individual prices.
No, third party apps can not be used on Odoo Online.
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.
The price for our modules is set up in euros. The Odoo store converts prices in others currencies according to its internal exchange rate. Thus, the price in US Dollars may change, when exchange rate changes.
Bug reporting
In case you have faced any bugs or inconsistent behavior, do not hesitate to contact us. We guarantee to provide fixes within 60 days after the purchase, while even after this period we are strongly interested to improve our tools.
No phone number or credit card is 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: screenshots, Odoo server logs, a full description of how to reproduce your problem, and so on. Usually, it takes a few business days to prepare a working plan for an issue (if a bug is confirmed) or provide you with guidelines on what should be done (otherwise).
Public features requests 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 in our to-do list.
Such a to-do list is processed on a regular basis and does not assume extra fees. Although we cannot promise deadlines and final design, it might be a good way to get desired features without investments and risks.
No phone number or credit card is required to contact us: only a short email sign up which does not take more than 30 seconds.
The tool to build deep and structured knowledge base for internal and external use. Knowledge System. KMS
298€
The tool to set up KPI targets and control their fulfillment by periods
The tool for time-based service management from booking appointment to sale and reviews
398€
The technical core to synchronize your cloud storage solution with Odoo
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