LkSG Compliance error messages in Odoo: when they appear and what to do about each

Two families of message

Some messages are about who can open something or about data the module protects: the LkSG dashboard, audit log records and the company on records that depend on a supplier. Changing what you typed will not clear them: either someone with the right permission does it, or it cannot be done.

Others flag data that breaks a rule: text that is too long or badly encoded, a repeated code or name, a figure out of range, or a missing step before a supplier can be marked compliant. You fix them by correcting the data or completing what is missing first.

Table of LkSG Compliance messages

The texts appear exactly as they are in the module's code, in English and with %s where the message contains it.

Messages that ask for an earlier step

Some messages are not saying the data is wrong, but that something has to happen first. These are worth reading in full, because the text itself tells you the way out.

Marking a supplier as compliant

Cannot mark compliant: no approved risk assessment exists for this supplier. means exactly that: there is no approved risk assessment for that supplier. The module will not let you mark it compliant until there is one. Check that supplier's assessments and see whether any is approved; if none is, that is the step still to do.

Measures from another company on an assessment line

If you run several companies in the same Odoo, you may come across A risk assessment line can only link a measure of its own company. Unlink the measure from the line first. The line only accepts measures from its own company. The message sets the order: first remove the measure from the line, then link a measure from the right company.

The company comes from the supplier

The company is that of the supplier and cannot be changed by hand. appears in several places in the module with the same wording. In each of them, the record's company is the supplier's and it is not changed by hand. If the company you see is not the one you expected, what you need to check is the supplier, not the record where the message pops up.

Repeated or badly encoded supplier names

There are two messages about the supplier name. A supplier with this name already exists for this company: %s warns you that the name is already registered in the same company; before creating another, search for it in the supplier list. Supplier name must use NFC-normalized Unicode. Please re-enter: %s asks you to retype the name because it is not in NFC-normalised Unicode. The same goes for the subject in Subject must use NFC-normalized Unicode.: typing the text into the field again is the direct way to do what it asks.

What cannot be corrected: the audit log and dashboard access

Two of the messages have no data to fix. Audit log records are immutable and cannot be modified. and Audit log records cannot be deleted. mean the module does not let you modify or delete audit log records. Do not go looking for a button to do it: the record stays as it is.

Only LkSG users can open the LkSG dashboard. depends on the user, not the data. If you see it, whoever administers your Odoo needs to set you up as an LkSG user.

If you want to see which menus the module adds and what a record goes through, it is covered in how LkSG Compliance works inside Odoo.

How FlexigoTech can help

The module costs €9 excluding VAT, a one-off payment per Odoo version, for 17, 18, 19 and 20; details are on the Odoo Apps listing and the module page. If you want to know whether it suits your company before installing it, read whether LkSG Compliance fits your company.

At FlexigoTech we implement Odoo 17, 18, 19 and 20 and build bespoke connectors and integrations, so we can help you get it running or look at a message you cannot work out.

Keep reading