1Ci Support Help Center home page
Submit a request
Sign in
  1. 1Ci Support
  2. 1C:Enterprise Development Standards
  3. Code conventions
  4. Using applied objects and universal value collections

Using FormAttributeToValue and FormDataToValue

  • Using applied objects and universal value collections
    • Search in value collections
    • Using the InformationRegisterRecordsManager object
    • Copying rows between value tables (tabular sections, etc.) with arbitrary structure
    • Document register records recording procedure
    • Getting presentations for reference values in a spreadsheet document
    • Creating applied objects programmatically
    • Using an object module, an object manager module, and common modules
    • Restrictions on the use of export procedures and functions
    • Setting the selection parameters and relations between them for the metadata objects
    • Using FormAttributeToValue and FormDataToValue
See more

Scope: managed applications, mobile applications, and ordinary applications.

Best practices

In most cases, FormAttributeToValue is preferable to FormDataToValue. 

Sticking to this recommendation will help you to keep the code consistent with other 1C:Enterprise applications. Also, FormAttributeToValue has simpler syntax, that is, less chance to make a code mistake.
FormDataToValue requires the data type to be specified explicitly.Example:

SignaturesTable = FormDataToValue(SignaturesTable, Type("ValueTable"));

In contrast, FormAttributeToValue doesn't require data type to be specified. Example:

SignaturesTable = FormAttributeToValue("SignaturesTable");

1C:Enterprise supports both the FormAttributeToValue and FormDataToValue methods, but the last-mentioned is considered more usable. In terms of efficiency and output, the methods are equal.

© 2020 1C INTERNATIONAL LLC www.1Ci.com Support policy