36.1.3. Specifics and limitations

The configuration extension does not support creation of the following native objects:

Common attributes being separators
Settings storages
Languages
Document journals
Business processes and tasks
External data sources

Extension of the following objects is not supported:

Subordinate subsystems cannot be created.
If an object cannot be a native extension object, its extension is also not supported.
Adding attributes and tables for the following objects is not supported:
- Chart of characteristic types
- Chart of accounts
- Chart of calculation types
Changing the structure of registers of all types is not supported. Only extending the list of recorders is supported.

Extension documents (native and adopted) can generate records in native extension registers. In other words, extension documents can act as recorders for native extension registers.

Aggregates are not supported for native accumulation registers.

Noted the following controlled properties:

Exchange plan components.
Predefined items for catalogs, charts of characteristic types, charts of accounts, and charts of calculation types.

When extending data, keep in mind the following specifics and limitations:

You cannot attach an extension so that it will be available in more than one instance in one infobase or data area. Names of extensions and all extension objects in the resulting configuration must be unique.
After attaching a configuration extension that extends data, no background restructuring is supported by the infobase.
Testing and patching only process the data structures of the extended configuration.
In the base configuration, you can use an extension only if it is signed with the same key as the base configuration.
Standalone mobile client supports extensions but does not support including them in a standalone configuration.

<< Prev Next >>