Main > Knowledge Base > Developer resources > Development recommendations > Configuration delivery and support > Module merging specifics > Developer resources > Development recommendations > Configuration delivery and support > Module merging specifics > Developer resources > Development recommendations > Configuration delivery and support > Module merging specifics

Module merging specifics

Mapping

1C:Enterprise merges modules by procedures. It generates the procedure mapping automatically, leaving you the option to correct it manually. Let us look into the mapping generation rules.

A 1C:Enterprise module consists of three areas:

The variable declaration areas are mapped to each other automatically, as well as the main program areas, and you cannot change that mapping. Procedures and functions are mapped based on their names, but a procedure is never mapped to a function, even if they have identical names.

To change the procedure and function mapping manually, set the "Merge prioritizing..." rule for the module. This adds the button that opens the detailed settings. In the settings window, in addition to editing the mapping, you can set a merge rule for each procedure and preview the module merge result.

Merging modules during configuration update

The "Merge..." rule is never set automatically during the configuration update. You can set it manually. If you do, note the following:

Next page: Recommendations for customizing vendor configurations




© 1C LLC. All rights reserved
1C Company respects the privacy of our customers and visitors
to our Web-site.