Scope: managed applications.
Best practice
1. Users can take advantage of managed forms to add display of any object attributes in dynamic lists. To make this functionality available to users, add the Reference field to the list.
If you use various mechanisms of 1C:Enterprise platform and Standard Subsystems Library in objects, the Reference attribute in dynamic lists can be critical to functioning of these mechanisms. For example:
- If you use the characteristic mechanism of 1C:Enterprise platform (or the Properties subsystem of Standard Subsystems Library), always display the Reference attribute in dynamic lists because characteristics (additional attributes and information records) can be displayed in the list columns only using the setting in user mode.
- When developing print commands (the Print subsystem of Standard Subsystems Library), the Reference attribute with the Always use flag becomes required for these commands.
2.1. When accessing data of a dynamic list row in code (for example, in the OnActivateRow handler, the OnGetDataAtServer handler, and other), consider that data of invisible columns are not received as an optimization. Even users can control visibility.
2.2. For columns that have the "Always use" flag set in the properties of the form table that displays the dynamic list, data is always received regardless of visibility.
We do not recommend that you set the "Always use" flag for a dynamic list attribute column. The exceptions are cases when the column value is required for algorithm execution. For example, the Reference column is always required for Print command, but this column can be hidden by user.