Errors and exceptions in Odoo 18 - Odoo Slides

Errors and exceptions in Odoo 18
Enterprise

Enterprise
Introduction
In Odoo 18, there are many kinds of errors and exceptions possible
while running the module or code under development.
Error management in Odoo 18 involves understanding how the
system handles exceptions and bugs, as well as employing good
practices to manage and resolve them effectively.
Odoo 18 have the common and standard exceptions like Attribute
Error, Value Error, Type Error, Validation Error, etc

Enterprise
1.ValidationError
At any time, we can raise an exception in Odoo using the ValidationError based
on any condition we need to set. For example, we can just set a Validation error
for the stock.picking model if the field partner_id , ie ‘Receive From’ is not filled
using the code.
from odoo import models
from odoo.exceptions import ValidationError
class StockPicking(models.Model):
_inherit = 'stock.picking'
def button_validate(self):
result = super(StockPicking, self).button_validate()
if not self.partner_id:
raise ValidationError('Fill in the field "Receive From"')
return result

Enterprise
While trying to validate the picking without filing the ‘Receive From’ field, it
shows like

Enterprise
2.UserError
User Errors can also be raised with the needed constraints or conditions with
which the system undergoes checks for every record. Import UserError from
odoo.exceptions and we can just replace the previous code as below to
demonstrate the workflow.
from odoo.exceptions import UserError
if not self.partner_id:
raise UserError('Fill in the field "Receive From"')
return result

Enterprise
And in the UI, whenever the condition is true, the exception will pop
up like

Enterprise
3.AccessError
This exception is used when the user tries to login to the Odoo instance with
invalid login details. First, we need to import AccessError as
from odoo.exceptions import AccessError
Now, let’s write a simple python code to block all the users other than Admin
from accessing a document.
if not self.env.is_admin():
raise AccessError(_("Sorry, you are not allowed to access this
document."))

Enterprise
4.MissingError
These Missing Errors are used in Odoo 18 usually when the user tries to access
any record or data that is not actually available in the database of the instance. It
may have either been deleted/ removed or doesn’t exist at all.
For the previous code, let’s try to access any record with a random ID, say 1000 as
print(self.browse(1000).name)
return result

Enterprise
Here, the stock.picking(1000,) is a non existing record and hence, while
clicking on the Validate button, it will pop up the Odoo 18’s inbuilt
exception as

Enterprise
We can add our own Missing Error exception first by importing it from
odoo.exceptions.
from odoo.exceptions import MissingError
And then by raising it as below.
raise MissingError('Missing Error Demo')

Enterprise
5.Access Denied
Access Denied exception in the case when a user tries to perform any
kind of action or operation for which he/she is not allowed to do due
to the restriction in the access rights.
from odoo.exceptions import AccessDenied
if not self.env.is_admin():
raise AccessDenied("You are not allowed to validate the
Operation")
return super(StockPicking, self).button_validate()

Enterprise
Here, for any user other than Admin, the right to validate the stock
movement will be denied. Let us login to the system as any other
internal user with no Admin access and try to validate the picking. The
error will come like

Enterprise
6.CacheMiss
This error is raised by Odoo in case when a record or a data is not found. Odoo
usually caches data about the record that is accessed recently for some time. This
CacheMiss occurs when the needed record is not found in the cache. It can be
caused due to high traffic or the memory limits allowed.
country = self.env['res.country].browse(1)
print(country.name)
Here, in the first line, the ‘country’ variable is having a value. Odoo fetches it from the
database and stores it in the cache. And in the second line, ‘country.name’ is printed.
During this time, Odoo will return it from cache without requiring to run a database
query again as in the first line.
In case if it is not found in the cache, CacheMiss exception will pop up.

Enterprise
7. RedirectWarning
This error is raised to redirect the workflow to a particular page instead of giving any
warning to the user. Redirect Warning can be useful to suggest an alternate flow that
should be followed, such as confirming an operation or redirecting to a form view
before continuing with the original action.
The necessary parameters for RedirectWarning are
action_id: It is the id of the action were to perform the redirection
message: It is the message for exception
button_text: It is the text to put on the button that will trigger the redirection

Enterprise
With our previous example of validating a picking, let’s rewrite the code to implement
Redirect Warning for demonstration as
from odoo import _, models
from odoo.exceptions import RedirectWarning
warehouse_action = self.env.ref('stock.action_warehouse_form')
msg = _('Please create a warehouse for company %s.',
self.env.company.display_name)
raise RedirectWarning(msg, warehouse_action.id, _('Go to Warehouses'))
return super(StockPicking, self).button_validate()

Enterprise
Here, while validating the picking, the system will generate a Redirect
Warning with a message on the body and two buttons named ‘Go to
Warehouses’ and ‘Close’.

Enterprise
While clicking on the ‘Go to Warehouses’ button, we get the page

For More Info.
Check our company website for related blogs
and Odoo book.
Check our YouTube channel for
functional and technical videos in Odoo.
Enterprise
www.cybrosys.com

Errors and exceptions in Odoo 18 - Odoo Slides

Recommended

More Related Content

Similar to Errors and exceptions in Odoo 18 - Odoo Slides (20)

More from Celine George (20)

Recently uploaded (20)

Errors and exceptions in Odoo 18 - Odoo Slides