Form fields do not have a data path (WrongDataPathForFormElements)

Type	Scope	Severity	Activated by default	Minutes to fix	Tags
Error	BSL	Critical	Yes	5	unpredictable

Description

Form fields do not have a data path (WrongDataPathForFormElements)

Type	Scope	Severity	Activated by default	Minutes to fix	Tags
Error	BSL	Critical	Yes	5	unpredictable

Diagnostics description

When actively reworking a form or associated metadata, there may be elements on the form that do not have an associated data element. Problems can arise after deleting metadata or metadata attributes, or when changing the main form attribute. As a result, such a form field will not be displayed. Errors occur with forms when extended validation is enabled in the 1C Configurator.

Справочник.Контрагенты.Форма.ФормаЭлемента.Форма Неразрешимые ссылки на объекты метаданных (12)

In this case, in form files from XML unloading, the value of the "Data path" property begins with a "~" sign, for example, for the "Description" field: "~Object.Description".

When you manually change the query of a dynamic list, the "Data path" property of its fields on the form is cleared. This leads to a breakdown of the connection between the form element (table column) and the dynamic list field, and it disappears from the table on the form.

In form files, when unloaded to XML, the value of the "Data path" property starts with a "~" character, for example, for the "Description" field: <DataPath> ~ List.Description </DataPath>.

For command bar buttons associated with the "Data" property with a standard dynamic list field, for example, for a button with a filled "Ref" value in the "CurrentData" property: <DataPath> ~ Items.List.CurrentData.Ref </DataPath>.

Examples

Sources

• General requirements - Standards 1C (RU)

Snippets

Diagnostic ignorance in code

// BSLLS:WrongDataPathForFormElements-off
// BSLLS:WrongDataPathForFormElements-on

Parameter for config

"WrongDataPathForFormElements": false