Length of configuration object codes and numbers

This article describes the standards that apply to object code or number length. All of the listed recommendations are mandatory unless noted otherwise.

This recommendation is optional

Set the length of configuration object codes or numbers based on their meaning.

  1. If a code is used as a short presentation of a data item, do not use autonumbering.
    Example: The code of the Users catalog stores short user names. The code length must be sufficient to store short string presentations of user objects.
  2. If a code or number is used as a numeric object ID, which can have a string prefix, specify the code or number length based on the estimated total number of objects stored in the database, or objects related to a specific period (for documents or business processes), or objects related to a specific owner (for hierarchical and subordinate catalogs and tasks). The number length includes prefix length (such as Infobase or organization prefix, if specified).

    The following code or number length values are recommended for standard configurations: 3, 5, 9, 11 (including prefix length).

    If your configuration includes the Object prefixation subsystem from 1C:Subsystems library, the recommended document number or catalog code length (including prefix length) is 11 or more (11, 13, 15...)
  3. If an object does not require a code or number, set the code or number length to 0.

We recommended that you set variable code or number length.

Next page: Limitations to usage of composite-type attributes

Be the first to know tips & tricks on business application development!

A confirmation e-mail has been sent to the e-mail address you provided .

Click the link in the e-mail to confirm and activate the subscription.