--- title: "Boss’nX schema errors and warnings: frequently asked questions" description: "Issues button missing, empty image despite the background, Mark decorative not offered, error after Save anyway: answers about Boss’nX schema messages." canonical: https://wiki.can-nx.com/en/guides/boss-schema-validation-help/ language: en product: Boss’nX audience: - administrateur - installateur context: "Boss’nX on a computer: messages of the schema editor Issues panel" --- # Boss’nX schema errors and warnings: frequently asked questions Context: Boss’nX on a computer: messages of the schema editor Issues panel Issues button missing, badges that disappear, schema without a name, empty image, decorative element, Save anyway, datapoint not found: here are the answers to common questions about the messages of the Boss’nX schema editor, for administrators and installers on a computer. The detailed steps are in [the errors and warnings guide](https://wiki.can-nx.com/en/guides/boss-schema-validation/). ## Where can I read the errors of a schema? Open **Schemas** in the header bar or in the **Menu**, then **Actions → Edit schema** on the schema row. Once it has loaded, click **Issues** at the bottom right of the drawing. In **Detected issues**, expand the group of the layer concerned and read the message. A name issue appears in the **Schema** group. ## Why does the Issues button not appear? This button appears only when the editor reports an issue. First check that you are in **Edit schema** and that the drawing has loaded. Its absence relates to the configuration of the drawing: the actual operation of the devices is checked separately. ## Why do the orange badges disappear when I close the panel? The orange warnings of the active layer are shown when Detected issues is open. Reopen **Issues** to find them again. The red error badges can remain visible with the panel closed. Closing the panel does not fix any element. ## Does Locate or clicking the exclamation mark fix the issue? No. Both actions find and select the element so that you can examine it in **Configuration**. If another layer opens without Configuration, wait for it to load, then click **Locate** a second time, on the same row. If it still fails, contact support with the message and your attempts. ## Where do I enter the name when “The schema has no name.” appears? In **Schema name**, at the top of the left panel. Enter a non-empty name: spaces alone are not enough. Then **Save** the schema. Even if a blank drawing does not yet show this message in Issues, the name is still required to save. ## Why does “No image loaded for this element.” appear even though the background is visible? The message refers to an **Image** element, which is separate from the layer background. Click **Locate** on its row, then **Configuration → Style → Upload image**. Choose a small image, wait for its preview and for the message to disappear, then save. Importing another background does not fill this Image element. ## What if the chosen image does not appear and the message remains? Check the type and size of the file and that it opens on your computer. The import of an Image element rejects files larger than **10 MB**; the layer background has a different limit. Try a small valid image: the import is done only when the preview appears. If these checks remain unsuccessful, contact support with the type and size of the file, the message and your attempts. ## Should I click Mark decorative for a button that must turn on a lamp? No. The decorative status suits an intentionally visual element, with no data to control or display: it does not link the button to the lamp. Keep the control purpose; for an Icon button, associate the expected data as described in [the Linked data guide](https://wiki.can-nx.com/en/guides/boss-schema-binding/). Do not remove a useful binding to get rid of a warning. If you cannot set up the expected binding, contact support, specifying the button and the data concerned. ## How do I remove the warning of a purely decorative pictogram? In **Detected issues**, locate the element to display its layer, then click **Mark decorative** on its row. This choice is offered for the relevant types, on the active layer. The warning concerned disappears; save to keep the change. You can also use **Configuration → Interaction → Decorative element**. ## Why is Mark decorative missing on a row from another layer? This choice is offered only on the active layer. First click **Locate** to make this layer active. If Configuration covers the panel, close **Configuration** with its **Close** cross, then examine the row again. This action does not apply to all element types or to all errors. If the purpose or the fix remains uncertain, contact support with the message displayed. ## How do I undo marking an element decorative by mistake? Use the **Undo (Ctrl+Z)** arrow in the bottom bar; **Redo (Ctrl+Y)** applies the change again. You can also select the element, then turn off **Configuration → Interaction → Decorative element**. The warning comes back if no data is linked: this setting does not create the missing binding. Save the result you want to keep. ## Why is the issue still there after Save anyway? This choice saves despite the errors, without fixing them. An Image element that is still empty can therefore remain empty after reopening. Locate the element, fix the flagged point, then save again. To go back to the fixes before starting the save, choose **Cancel** in the **Save schema?** box. ## Was the equipment deleted when the bound datapoint cannot be found? Not necessarily. **The bound datapoint cannot be found — its equipment may have been deleted.** mentions a possibility, not an established cause. Locate the element and identify the expected data, without recreating or deleting equipment on this basis alone. If the binding remains uncertain, contact support with the context and the exact message. ## Contact support If the message comes back although you have already fixed, saved and reopened the right layer, or if a question remains unanswered, write to support@can-nx.com with: Boss’nX, the schema and layer, the exact message, the fix made, the result after reopening and the attempts already made, so that you do not start over from the beginning. A screenshot without sensitive data can help; do not send any password or access key.