Anyone getting involved with classic software systems should be aware of the risks involved. These include:
1) Right of use
The most significant risk is probably the right of use of many mainstream services, further exacerbated by the dismantling of local infrastructures in favor of cloud solutions. This has naturally attracted many manufacturers to make their systems available as cloud solutions. The risk of in-house operation has transferred to the manufacturer, who – after all – should know his system best and should be able to operate it more securely. Moreover, this solution has the added advantage that there is no need to finance a license package. Instead, the user may switch to a subscription model usually associated with such a license deal, which is also – if looked at by month – much cheaper.
We have already touched on this subject in our last blog. In this entry, we would like to discuss it in more detail.
If you add up our collective IT experience, you will probably get a result of several hundred years, maybe even a whole millennium. During all this time, in all our discussions, one topic was always sure to pop up: Data – and not because data are a classic!
Although we have covered many of the differences between Odoo and other systems in previous blog articles, there are a few essential features where Odoo uses a novel approach. That is sufficient reason to highlight some of these features. In some cases, these elements even replace classic functions, and you may not immediately find specific functions in Odoo simply because they look looks unfamiliar. In other instances, Odoo uses approaches that are fundamentally different. In this blog, I would like to concentrate on Integrated Communication and different View Types of a process, and the option to flexibly combine Groups and Filters.
I have to admit that I needed time to get used to working with these features, but it did not take as long as I expected. With a little knowledge of Excel and the Import/Export function, you can do pretty much anything. If you are still on the look-out for mass-update modules, you have obviously never worked with these features either, because, in combination with Excel, you have a real winning team!
Odoo is able to save a vast amount of data. Consequently, the field lists are incredibly long. Since none of the data are saved redundantly but are interlinked, a lot of information is distributed to sub-records. But there is almost unlimited access to both import and export – which does not shorten the field lists though.
But with a few little tips on handling (which we want to share in the course of this blog), the underbrush will clear up rapidly.
With Odoo 13, a lot has changed in the Invoicing and Finance modules. The most significant change probably is that Invoicing no longer exists as a single object. Until last October, with the release of version 13, the analog world acted as a template for the technical invoicing process. You generated an invoice, used „the next number“ on the list, put it on the document, sent it off, and forwarded it to the accounting department. The latter put a date of receipt stamp on it, allocated it to an account, added it to a batch, and finally posted it.