CapitalKnowledge

Projects and Designs > Shared Objects > Batch Sharing

Matching Criteria

During batch sharing, the batch sharing matching criteria are used to determine which non-shared objects should become instances of the same shared object, and also to determine which non-shared objects should become instances of existing shared objects.

You specify the matching criteria in the Project Preferences Dialog Box. The two main types of matching criteria are object attributes and object properties. For each type of object, you can specify which attributes and properties should be used as matching criteria. For wires, you can, alternatively, specify that matching should be carried out according to connectivity.

This video demonstrates how to specify matching criteria:

Note

When sharing multicores or overbraids using batch sharing, sharing will only proceed if the matched objects also have matching type, inner core structure, and inner core names. See Batch Sharing.

Matching Wires According to Connectivity

When you select the “Match using connectivity” option, wires are considered to match if the ends terminate at the same pins. For example, if Wire A and Wire B both terminate at Pin 1 on Device 1 at one end, and both terminate at Pin 1 on Device 2 at their other ends, the wires match.

Use

of Matching Criteria During Batch Sharing

When you use batch sharing, the matching criteria are used to:

  • Match non-shared objects with each other: When matching is performed, for each object type, objects that have the same values for each of the matching criteria are grouped together, and will become instances of the same shared object if you complete the batch sharing procedure.

  • Match non-shared objects with existing shared objects: If any existing shared objects have the same values for each of the matching criteria as one or more non-shared objects, only the Share Into option will be available for those non-shared objects in the Action column in the Batch Share Dialog Box. If you complete the batch share procedure, those non-shared objects will become new instances of the existing shared object.

Note

When matching is performed, all the shared objects in the project are considered, including shared objects that do not have instances placed on designs in the build list that you are performing batch sharing on.

When properties are used as matching criteria, property type is not considered. For example, an integer property with value 1 and a string property with value “1” are considered to match.

Parent Topic:

Batch Sharing

Related Topics

  • Using Batch Sharing

  • Batch Share Dialog Box

  • Batch Sharing Overview

Capital Logic Designer User Guide, 2512

Unpublished work. © 2025 Siemens

Source: https://docs.sw.siemens.com/en-US/doc/861057055/202410078.capital_ld_user/id471fda02-1e4d-1456-3676-47d03f9536b · retrieved 2026-07-18