DropBox Odoo Integration v.12
The tool to automatically synchronize Odoo attachments with DropBox files in both ways
Synchronization is bilateral. All Odoo attachments are put in DropBox regularly. DropBox files create attachments in Odoo in case they are placed in a correct folder. Look at the sections From Odoo to DropBox and From DropBox to Odoo
Integration is automatic in both ways. Based on scheduled jobs, Odoo send attachments to DropBox and retrieve files from there
Any Odoo document might be synced: customers, opportunities, sale or purchase orders, tasks or issues, employees or users, etc. You decide by your own which records should be in DropBox, and which should be left in Odoo
Synchronization works for any DropBox tariff, including Personal DropBox (Basic, Plus, Family) and business DropBox (Professional, Standard, Advanced)
The tool works fine with the Odoo Enterprise Documents module. For full compatibility and to reflect new module directories structure use the app Cloud Sync for Enterprise Documents. Look also at the section Odoo Enterprise Documents
All synced files are easily accessible though clicking on an attachment. You might also open a whole document folder by clicking on 'Open folder' on the attachment widget. This feature migth be optionally turned off: look at the section DropBox URLs
All sync activities might be logged. Control over files and folders creations, moves, name changes and removals. Just turn on the option 'Log sync activities' and access history through the button 'Sync logs'
New For each document of this type you may create a default directories' structure. When this folder is firstly synced, Odoo would generate default folders. For example, for all employees you may have pre-defined folders 'Scans', 'Scans/Official', 'Photos', etc.
The tool is compatible with Odoo reporting and mailing apps. If such an app faces a synced file, it retrieves a real content from DropBox. In particular, the reports 'always reload' feature and messages & mass mailing attachments work properly
Integration is based on a single user endpoint. It means that a single user login/password of DropBox is used. Afterwards for integrations Odoo would use that credentials disregarding an actual Odoo user
- Prepare and keep updated folders' structure in DropBox
- Upload new attachments to a correct folder
Odoo creates a convenient directory structure in DropBox: Odoo / Document type name / Document name / Files, where:
- Odoo is a central directory for Odoo Sync in your cloud storage.
- Document type is a synced Odoo model, for example, 'Sale orders', 'Opportunities', 'Customers'
- You select document types by yourself. It might be any document type
- Moreover, you might have a few folders for a single document type. Use Odoo domains to have not global 'Partners, but 'Customers' and 'Suppliers', not just 'Sale orders' but 'Commercial offers', 'To deliver', and 'Done orders'
- With each sync Odoo would try to update document types' folders. Add a new document type at any moment. It will appear in DropBox with a next sync
- You are welcome to introduce or change document types folder names at any moment in Odoo. Take into account: renaming in DropBox will be recovered to Odoo names
- If you remove a model from integration, it will not be deleted from DropBox to keep already synced files safe. However, new documents of this type would not be synced
- In case you removed a directory in DropBox, but it is still configured in Odoo, with a next sync a folder structure is going to be recovered (not files, surely).
- Document is an exact object to sync. For instance, 'Agrolait' or 'SO019'
- Documents are synced in case they relate to a synced document type and satisfy its filters. For example, you are not obliged to sync all partners, you may integrate only 'Customers' and 'Vendors' or only 'Companies', not 'Contacts'
- Odoo would generate a folder in DropBox for each suitable document even for documents without attachments. It is needed for a backward sync to easily add new files
- DropBox folder name equals a real document name. It relies upon Odoo name_get method. Thus, Odoo 'Michael Fletcher' (a contact of 'Agrolait') would be DropBox 'Agrolait, Michael Fletcher'
- If an exact document changes its document type (e.g. a quotation is now confirmed), Odoo will automatically relocate its related folder to a proper parent directory (in the example: from 'Commercial offers' to 'To deliver')
- In case a document relates to a few types (for instance, you have 'Vendors' and 'Customers', while Agrolait is both), this document folder would be put into the most prioritized document type. A document type priority is higher as closer to the top in Odoo interfaces it is
- If an Odoo document is removed, the next sync will remove a corresponding DropBox directory
- In case you remove a directory in DropBox, but it still exists in Odoo, DropBox folder structure would be recovered (while files would be unlinked in both Odoo and DropBox)
- Folders renaming in DropBox will be replaced with Odoo names, Odoo document names are more important
- Files are real files taken from Odoo attachments
The resulted path would be, for example, 'Odoo / Quotations / SO019 / commercial offer.png'.
The only exclusion of the rule are stand alone attachments which do not relate to any Odoo documents (their document type is 'ir.attachment'). Such attachments' path is 'Odoo / Stand Alone Attachments / image.png'.
The direct sync might take quite a long, since a lot of folders should be created. It is not recommended to make sync too frequent: once an hour or two hours is fine.
FilesWith each direct sync, Odoo tries to find not yet synced attachments. If such attachments suit any document type to sync, a file will be uploaded to DropBox to a proper folder. In Odoo such attachments will become of 'url' type (look also at the section DropBox URLs). It means that a file is not any more kept in Odoo server space, but now it is in DropBox. Until sync is done, Odoo attachment remains binary and stores an actual file. Such approach helps Odoo to work faster.
If you unlinked an attachment from Odoo, it would be deleted in DropBox as well.
Take into account that file names should be managed in DropBox: each backward sync would recover DropBox names, Odoo is here less important.
- If a new file is added to a proper document folder (e.g. to 'Odoo / Customers / Agrolait'), the same attachment will be added to Odoo document (in the example - to 'Agrolait')
- In document folders you can put not only files but also child folders. In that case a link for this folder (not its content) is kept in attachments
- In case you rename a file in DropBox, it will be renamed in Odoo as well
- Files' removal from DropBox leads to related Odoo attachments' removal
- If you move a file to another document folder, in Odoo a related attachment would be re-attached to this new document. Take into account: if you move a file for a not document folder, this Odoo attachment will be deleted as it has been removed from DropBox
- If you deleted a document type or document folder, their child files are deleted as well. Thus, Odoo would remove related attachments. The folders, however, will be recovered with a next direct sync. Folders' move to another directory is also considered as a removal. Avoid such situations by following the simple rule: folders are managed mostly by Odoo, files - mostly by DropBox.
Backward DropBox might take quite much time, since each folder should be checked (the more folders, the more time the backward sync requires). It is recommended to make frequency oftener than once an hour or two hours.
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 DropBox business account.
This tool relies upon share 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 a 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 quite a many cases. Thus, if you need to open DropBox files / folders from Odoo, do not switch off the feature 'No links to DropBox from Odoo'.
- 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.
This tool is not in conflict with the 'documents' module provided by the Enterprise license. Attachments related to Enterprise folders would be synced as any other files: according to a document they relate to. In the most cases it means they would be linked to stand-alone attachments.
It is not always comfortable, and you might be interested in reflecting directories' structure introduced by the module 'Documents'. To this end the extension Cloud Sync for Enterprise Documents (its standard price is 44 Euros) is developed. This tool has the following features:
- The documents hierarchy is reflected within the folder 'Odoo / Odoo Docs'
- Each Odoo folder has a linked cloud 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 attachments within a paired directory
- Please do not name synced models as 'Odoo Docs'. This is the reserved name for Odoo Enterprise Documents
Configuration and Login
- 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 general settings - DropBox
- Copy App Key, App secret, and redirect URI to the Odoo configuration page
-
For team DropBoxes only
- Check the box 'DropBox Team'
- Set an email of DropBox user. Inside this user folder all Odoo related items would be created and only after that they are shared to all other users. Under this user all files and folders are created, changed, moved, and deleted
- Choose a suitable name for the root Odoo folder, e.g. 'Odoo' or 'ERP'
- Press Save
- Press 'Login and Confirm'
Create a DropBox app
Set up DropBox App: redirection URL
DropBox permissions for personal accounts
DropBox permissions for business accounts
Set up Odoo for DropBox integration
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 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.
Često postavljana pitanja o DropBox Odoo Integration Odoo v.12
Mogu li mijenjati učestalost poslova sinkronizacije?
Da, možete. U tu svrhu:
Uključite način rada za otklanjanje pogrešaka
Idite na tehničke postavke > Automatizacija > Zakazani poslovi
Pronađite poslove 'Synchronize attachments with cloud' i 'Update attachments from cloud'.
Nemojte ih pokretati prečesto. Poželjno je da posao završi prije nego što krene sljedeći. Postavka ovisi o tome koliko stavki imate za sinkronizaciju. Učestalost je obično između 15 minuta i 4 sata.
Provjerite i da ste u konfiguracijskoj datoteci Odoo postavili dovoljna vremenska ograničenja. Parametri LIMIT_TIME_CPU i LIMIT_TIME_REAL moraju biti jednaki ili veći od planiranog vremena cron posla. Od verzije 13 uzmite u obzir i parametar LIMIT_TIME_REAL_CRON.
Važna napomena za klijente Odoo.sh: maksimalno vrijeme cron posla može biti samo 15 minuta.
Mogu li konfigurirati drugačiju strukturu sinkroniziranih direktorija od one koju pretpostavlja sinkronizacija?
Ne, ova je značajka dostupna tek od verzije 15. Prije te verzije modul radi s unaprijed definiranom strukturom mapa:
Odoo - središnja mapa za sinkronizaciju
Models - mape za svaki tip dokumenta Odoo. Na primjer, 'Projects', 'Partners'. Po domeni mogu postojati specifičnije mape: npr. 'Customer 1 Projects', 'Projects of the Customer 2', 'Internal Projects' itd.
Objects - mape za svaki dokument, npr. 'Project 1' ili 'Customer 1'
Datoteke i mape povezane s ovim Odoo dokumentom koje se sinkroniziraju.
Kao rezultat možete imati na primjer:
Odoo / Projects / Project 1 / datoteke i mape povezane s project 1
Odoo / Customer 1 Projects / Project 1; Odoo / Customer 2 Projects / Project 3, ...
Odoo / Customers / Customer 1 / datoteke i mape povezane s customer 1
Ova je struktura uvijek ravna, što znači da postoje samo te razine hijerarhije. Stoga je točno da se različiti tipovi dokumenata ne mogu držati unutar iste strukture. Unutar mape 'Customer 1' ne možemo držati datoteke povezane i s prodajnim narudžbama, i s računima, i s projektima. Svaki od tih tipova dokumenata ima vlastitu mapu (ili nekoliko vlastitih). Inače ne bismo mogli napraviti povratnu sinkronizaciju jer ne bi bilo kriterija na koji se osloniti.
Trebam li u Odoo postaviti pristupe određenih korisnika?
Ne, alat se oslanja na jednu korisničku krajnju točku. Svi procesi sinkronizacije izvode se pod jednim cloud administratorom (aplikacijom). Prava pristupa za stvorene mape / datoteke nisu automatizirana. Ta prava trebate administrirati u svom rješenju pohrane u oblaku.
Gdje se pohranjuju sinkronizirana polja? Jesu li duplicirana u Odoo i oblake?
Aplikacija pretpostavlja da se binarni sadržaj privitaka čuva u Cloud Clientu umjesto na Odoo poslužitelju. Takvi privici u Odoo postaju tipa URL i možete im bilo kada pristupiti iz okvira privitaka ili iz Cloud Clienta.
Nakon postavljanja nisu potrebne ručne radnje jer je sinkronizacija potpuno automatska. Odlučite koje vrste Odoo dokumenata treba sinkronizirati i postavite povezani model za svaku od njih (klijenti, prodajni ili nabavni nalozi, zadaci, projekti itd.).
Mogu li imati nekoliko mapa za isti tip dokumenta? Na primjer, interni projekti i projekti kupaca?
Da, možete. U tu svrhu pripremite pravilo za svaki, a zatim primijenite filtre: na primjer prema vrsti projekta.
Pokušajte filtre učiniti međusobno isključivima kako bi se dokument mogao jednoznačno dodijeliti. Npr. „klijent, ali ne dobavljač“, „dobavljač, ali ne klijent“. Inače će mapa određenog dokumenta skakati s jednog modela na drugi.
Trebam li samo aplikaciju Cloud Storage Solution?
Ne, alat je samo tehnička jezgra. Trebate i konektor za svoj cloud client.
Je li u redu ako imam mnogo objekata za sinkronizaciju, na primjer 10000?
Da, iako kod mnogo mapa/privitaka koje treba sinkronizirati proces može biti spor. Istodobno, klijenti su prijavili okruženja s >10k partnera i ~5k varijanti proizvoda za sinkronizaciju, a procesi su bili prihvatljivi.
Nekoliko točaka za naglasiti:
- Sinkronizacija je izgrađena tako da se svaka stavka sinkronizira i ne izgubi, iako možda nije brza. To jamče redovi prvi-uđi-prvi-izađi i svaki posao koji se potvrdi.
- Broj objekata može se logički ograničiti. Konfiguracija modela omogućuje ograničenje sinkronizacije zastarjelih stavki (npr. nema smisla sinkronizirati arhivirane partnere ili naloge od prije 2 godine).
Je li moguće sinkronizaciju učiniti u stvarnom vremenu?
Ne. Imamo ozbiljne razloge da izbjegavamo sinkronizaciju u stvarnom vremenu:
Problemi performansi. Ako je sinkronizacija u stvarnom vremenu, svako učitavanje datoteke rezultirat će zaslonom učitavanja.
Problemi sukoba. Ako 2 korisnika istodobno promijene stavku, to može dovesti do neriješenih situacija. Kod redovitih poslova to možemo popraviti naknadno, a u stvarnom vremenu morali bismo to spremiti kao red, što bi korisnike još više zbunitilo.
Problemi funkcionalnosti. Posebno preimenovanje i restrukturiranje stavki. U povratnoj sinkronizaciji alat se strogo oslanja na logiku direktorija i pri svakoj sinkronizaciji provjerava se 100% stavki. Ako se to radi nakon svake promjene, bit će tisuće zahtjeva u sekundi. Ako ne: promjene bi se izgubile.
Mogu li sinkronizirati privitke s nekoliko cloud klijenata
Ne, ova je značajka dostupna tek od verzije 15.
U našim cloudovima koristimo poseban uređivač (npr. OnlyOffice, Office 365 itd.). Bi li se datoteke otvarale u tom uređivaču?
Da, ovisno o konfiguraciji cloud clienta.
Koje su politike ažuriranja vaših alata?
Prema važećim pravilima Odoo Apps Store:
- Svaki modul kupljen za verziju 12.0 i stariju daje pristup svim verzijama do 12.0.
- Od verzije 13.0 svaku verziju modula treba kupiti zasebno.
- Bez obzira na verziju, kupnja daje pravo na sva ažuriranja i ispravke unutar glavne verzije.
Imajte na umu da tim faOtools ne kontrolira ta pravila. Za pitanja obratite se izravno predstavnicima Odoo Apps Store.
Kako mogu instalirati vašu aplikaciju na Odoo.sh?
Najizravniji je pristup koristiti ugrađeni tijek rada Odoo trgovine:
1. Otvorite stranicu modula i kliknite gumb Deploy on odoo.sh
2. Nakon toga bit ćete preusmjereni na GitHub stranicu. Prijavite se na račun, zatim kliknite 'Create a new repo' ili upotrijebite postojeći. Provjerite da je spremište privatno. Nije dopušteno objavljivati aplikacije pod licencijom OPL-1. Ako treba, stvorite novi repo za Odoo.sh projekt
3. Zatim idite na odoo.sh i kliknite gumb Deploy. U skočnom prozoru potvrdite odluku i kliknite 'Continue.' Time se pokreće instalacija.
Ovi koraci instalirat će aplikaciju na produkcijsku granu projekta. Ako želite postaviti aplikacije na druge grane ili ažurirati modul, poduzmite sljedeće:
1. Prenesite izvorni kod aplikacije iz Odoo trgovine
2. Napravite commit modula u potrebni GitHub repozitorij. Provjerite da nijedna mapa/datoteka aplikacije nije ignorirana (tj. nije u .gitignore repozitorija). Repozitorije automatski stvara odoo.sh i po zadanim postavkama mogu sadržavati važne stavke (npr. /lib). Prenesite sve direktorije, poddirektorije i datoteke modula bez iznimaka
3. Postavite ciljnu granu odoo.sh projekta ili, ako to pretpostavljaju postavke, pričekajte dok se automatski izgradi.
Kako trebam instalirati vašu aplikaciju na vlastiti poslužitelj?
2. Ponovno pokrenite Odoo poslužitelj;
3. Uključite način za razvoj (tehničke postavke);
4. Ažurirajte popis aplikacija (izbornik aplikacija);
5. Pronađite aplikaciju i pritisnite „Activate“/„Install“;
6. Slijedite smjernice na stranici aplikacije ako postoje.
Primijetio sam da vaša aplikacija ima dodatne dodatke. Mogu li ih kupiti naknadno?
Da, naravno. Istodobno Odoo automatski dodaje sve ovisnosti u košaricu, pa prethodno kupljene alate treba isključiti da ne platite dvaput.
Postavio sam vašu aplikaciju na Odoo.sh i u testovima vidim upozorenje/pogrešku
Crveno/narančasto upozorenje ne utječe na značajke aplikacije. Nažalost, naši moduli ponekad ne prođu standardne automatske testove jer oni pretpostavljaju ponašanje koje je u sukobu s ciljevima aplikacije. Npr. mijenjamo izračun cijene, a testovi standardnog Odoo modula uspoređuju konačnu cijenu sa standardnim algoritmom.
Prije svega provjerite značajke postavljene baze. Radi li sve ispravno?
Ako i dalje smatrate da upozorenje utječe na stvarne značajke, javite nam i pošaljite potpune zapisnike instalacije i potpuni popis postavljenih modula (uključujući jezgru i treće strane).
Mogu li kupiti aplikaciju izravno od vaše tvrtke?
Ne, alate distribuiramo samo preko službene trgovine aplikacija Odoo.
Želio bih dobiti popust
Nažalost, nemamo tehničkih sredstava za individualne cijene.
Mogu li instalirati aplikaciju u svoju bazu Odoo Online (SaaS)?
Ne, aplikacije trećih strana ne mogu se koristiti na Odoo Online. Nažalost Odoo SaaS to blokira.
Vaš alat ovisi o drugim aplikacijama. Trebam li ih kupiti?
Da, alatu su potrebni svi moduli navedeni u ovisnostima da bi ispravno radio. Cijena na stranici aplikacije već uključuje sve potrebne ovisnosti.
Koja je cijena modula u američkim dolarima? Zašto se promijenila?
Cijena naših modula je u eurima. Odoo trgovina pretvara cijene u druge valute prema internom tečaju. Stoga se cijena u američkim dolarima može promijeniti kad se tečaj ažurira.
Tekstovi aplikacije i web stranice na jezicima osim engleskog izrađeni su uz pomoć UI i usklađeni sa službenim Odoo prijevodima. Ako uočite pogrešku, pošaljite prijavu o ispravnosti prijevoda i ispravit ćemo.
Prijava grešaka
Ako naiđete na greške ili nedosljedno ponašanje, slobodno nas kontaktirajte. Jamčimo ispravke unutar 60 dana od kupnje i i dalje želimo unapređivati alate nakon tog razdoblja.
Za kontakt nije potreban broj telefona ni kreditna kartica. Potrebna je samo kratka prijava e-poštom koja ne traje više od 30 sekundi.
U zahtjev uključite što više pojedinosti: snimke zaslona, zapisnike Odoo poslužitelja, potpuni opis kako reproducirati problem i slično. Obično treba nekoliko radnih dana za pripremu radnog plana (ako je greška potvrđena) ili smjernica što učiniti (inače).
Javni zahtjevi za značajke i ideje modula (besplatan razvoj)
Snažno smo motivirani poboljšati svoje alate i zahvalni smo na svakoj povratnoj informaciji. Ako su vaši zahtjevi od javne koristi i mogu se učinkovito provesti, tim će ih uvrstiti na naš popis zadataka.
Takav popis zadataka obrađuje se redovito i ne podrazumijeva dodatne naknade. Iako ne možemo obećati rokove i konačni dizajn, to može biti dobar način da dobijete željene značajke bez ulaganja i rizika.
Za kontakt nije potreban broj telefona ni kreditna kartica. Potrebna je samo kratka prijava e-poštom koja ne traje više od 30 sekundi.
Alat za sigurno čuvanje lozinki u Odoo za zajedničku upotrebu. Dijeljeni trezori
198€Alat za izgradnju duboke i strukturirane baze znanja za internu i vanjsku uporabu. Knowledge System. KMS. Revizije poput wikija.
398€Alat za vremenski upravljanje uslugama od rezervacije termina do prodaje i recenzija
Alat za postavljanje KPI ciljeva i kontrolu njihova ispunjenja po razdobljima. KPI nadzorne ploče. Dizajner ploča. KPI grafikoni
198€Alat za upravljanje Odoo iz omiljenih AI chatova putem MCP. Claude. Bilo koji AI koji podržava MCP.
198€Alat za fleksibilno strukturiranje Odoo privitaka u mapama i sinkronizaciju direktorija s cloud klijentima: Google Drive, OneDrive/SharePoint, Nextcloud/ownCloud, Dropbox, Amazon S3, Box i NAS. DMS. Upravitelj datotekama. Sustav za upravljanje dokumentima
Alat za automatsku dvosmjernu sinkronizaciju Odoo privitaka s datotekama OneDrive
Alat za automatsku dvosmjernu sinkronizaciju Odoo privitaka s datotekama Google Drive
Alat za automatsku dvosmjernu sinkronizaciju Odoo privitaka s datotekama ownCloud/Nextcloud