OneDrive / SharePoint Odoo Integration v.8
The tool to automatically synchronize Odoo attachments with OneDrive files in both ways
Synchronization is bilateral. All Odoo attachments are put in OneDrive regularly. OneDrive files create attachments in Odoo in case they are placed in a correct folder
Integration is automatic. Based on scheduled jobs Odoo would send attachments to OneDrive and retrieve files from there
Synchronization works for SharePoint sites, OneDrive for business, and personal OneDrive. In the first case the files are kept in preselected documents library, in the latter two – in a user' documents library
Odoo attachments, which are put in OneDrive, receive the URL type. It means that a file is not any more kept in Odoo server space, but now it is in OneDrive. Until sync is done, Odoo attachment remains binary and stores actual file
When you click on a synced attachment, Odoo automatically redirects you to a file previewer. Among others it might be Word or Excel editor (if Office365 is set up)
OneDrive files synced from Odoo has the structure to provide the backward sync: Odoo / Model / Object / files (e.g 'Odoo / Quotation / SO019 7 / commercial offer.png').
If you add a file to an Object folder (e.g. inside 'SO019 7'), that file will create an attachment in Odoo (e.g. for the sales order SO019) with a link to real file in OneDrive. You can put in object folders not only files but also child folders. In that case in attachments a link for this folder is kept (not its content)
You can rename/move folders or files in OneDrive without a harm for Odoo attachments. The only thing you should not do is to delete folders
If an attachment is removed from Odoo, a related OneDrive file will be deleted as well. Files removal from OneDrive leads to related Odoo attachments unlink
Synchronization is based on a single user endpoint. It means that you should login in OneDrive only once. Afterwards for integrations Odoo would use that credentials disregarding an actual Odoo user. Make sure, however, that real Odoo users have an access to OneDrive to open URLs linked to their attachments
Contents
- Preliminary steps
- SharePoint sites
- Personal Onedrive and Onedrive for business
- Reconnection (also in case of migration from this app's versions under 1.2.0)
- Scheduled jobs
SharePoint sites
- Go to your Azure Portal and prepare a new application:
- Grant the app full permissions for Office365 SharePoint online
- Assign the reply url as [YOURODOOSITENAME]/one_drive_token (e.g. https://odootools.com/one_drive_token)
- Generate a new key. Keep it safely somewhere for the future use
- 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
- Go to the OneDrive configuration menu:
- Copy 'Application ID' to 'App client_id'
- Put a previously generated key to the field 'App secret key'
- Enter the 'Redirect URL' as you entered 'Reply url' in Azure Portal
- Check the boxes 'OneDrive for business' and 'Use sharepoint sites'
- The SharePoint URL should be of the type https://[URL]/. The last '/' is required, sitename 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'
- 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 application in your Azure Portal
App's permissions
App's permissions
Redirect url should be https://[yourodoosite]/one_drive_token
Generate a secret key
Create a new SharePoint Documents Library
Create a new SharePoint Documents Library
Enter configuration keys in Odoo
Odoo attachments are ready for sync with Onedrive files. Press 'Sync to Onedrive' for the files upload
Personal OneDrive and OneDrive for business
- Go to 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)
- 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'
- 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 OneDrive application
New OneDrive Web platform and redirect url
Generate new secret for your application
Enter configuration keys in Odoo
Reconnection
- You use this tool with version prior to 1.2.0. In that case you should also install the library 'microsoftgraph'. Look above
- You have not used the sync tool for more than 6 months
- Press the button 'Reconnect'
- Press the button 'Login and confirm'
Scheduled jobs
- Turn on debug mode
- Go to technical settings > Automation > Scheduled jobs
- Find the jobs 'Synchronize attachments with cloud' and 'Synchronize attachments from OneDrive'
Frequently Asked Questions about OneDrive / SharePoint Odoo Integration Odoo v.8
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.
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 a deep and structured knowledge base for internal and external use. Knowledge System. KMS. Wiki-like revisions.
298€The tool to set up KPI targets and control their fulfillment by periods. KPI dashboards. Dashboard designer. KPI charts
The tool for time-based service management from booking appointments to sales and reviews
398€The core for Odoo integration with cloud file systems (ownCloud, Dropbox, Onedrive, etc.)
The tool to automatically synchronize Odoo attachments with Google Drive files in both ways
Manage Odoo documents in OwnCloud/NextCloud (bilateral sync)
The tool to automatically synchronize Odoo attachments with DropBox files in both ways