MultiBinder - SEAL Script

[StefanLundin]

The Concept

The MultiBinder script automates binding properties between objects in source and target folders in EcoStruxure Building Operation. It supports many-to-many relationships by binding multiple source objects to multiple unique target objects, ensuring each source object binds to exactly one matching target object based on their names (1:1 relationship per object pair). For example, it can bind 100 objects from a source folder to 100 corresponding objects in a target folder, preventing ambiguous bindings when multiple matches are found.

Key Features:

1. Single Path Binding:
   • Specify one source and one target path to bind objects.
   • Example: Bind properties of multiple objects from one folder to another.
2. Multiple Paths Binding:
   • Supports binding properties from multiple paths using a CSV file.
   • The CSV file should contain pairs of source and target paths for binding.
   • Example: Bind properties from multiple folders to corresponding target folders.
3. Matching Rules:
   • Choose how to match object names (directly under the specified paths)
     • Identical Names: Bind objects with the same names (e.g.,/Server 1/Folder 1/Object A  to /Server 1/Folder 2/Object A )
     • To Name Ends with From Name: Bind a target object whose name ends with the source object’s name (e.g.,/Server 1/Folder 1/Prefix.Object A  to /Server 1/Folder 2/Object A)
     • From Name Ends with To Name: Bind a source object whose name ends with the target object’s name (e.g.,/Server 1/Folder 1/Object A  to /Server 1/Folder 2/Object A)
   • Bindings occur only for a single match; multiple matches trigger a warning and are skipped to ensure a 1:1 relationship per object.
4. Object Types:
   • Specify the types of objects to process.
   • Currently only processes "Value" objects (e.g., server.point., bacnet.mpx.point.)
     .
5. Property Types:
   • Specify the types of properties to affect.
   • Currently only affects "Value" property.

How It Works:

1. Mapping:
   • The script creates a mapping of source and target paths based on user input or a CSV file.
2. Crawling Paths:
   • The Script crawls through the specified paths to gather all relevant objects.
3. Binding Process:
   • For each source-target path pair, the script matches objects based on the selected matching rule (identical names, To ends with From, or From ends with To).
   • Each source object is bound to a single matching target object:
     • If a single match is found, the source object’s Value property is bound to the target object’s Value property.
     • If multiple matches are found, the script logs a warning (e.g., “Multiple matches found for Object A, skipping binding”) and skips binding to ensure a 1:1 relationship.
     • If no match is found, it logs “No match found” and continues.
   • Example: Binds 100 source objects to 100 unique target objects, ensuring each binding is unique.
4. Saving Changes:
   • After completing the binding process, the script saves the changes to the system.

Example Use Case:

• You have a set of common signals located in the folder /Server 1/Common signals and you want to bind their values to corresponding objects in  the folder ../External signals in various rooms. The MultiBinder script can automate this process, ensuring that each common signal's value is correctly bound to its corresponding external signal in the specified rooms.
  
  See the attached CSV as an example. 
  In the CSV example, the script will bind the properties from the common signals folder on the server to the external signals folder in rooms R101 to R106, ensuring that each room's external signals are correctly bound to a matching object in common signals folder.
  

[StefanLundin]

Update - MultiBinder Version 1.2

An option for a selection of matching rules was added 

Matching Rules:

• Choose how to match object names (directly under the specified paths)
  • Identical Names: Bind objects with the same names (e.g.,/Server 1/Folder 1/Object A  to /Server 1/Folder 2/Object A )
  • To Name Ends with From Name: Bind a target object whose name ends with the source object’s name (e.g.,/Server 1/Folder 1/Prefix.Object A  to /Server 1/Folder 2/Object A)
  • From Name Ends with To Name: Bind a source object whose name ends with the target object’s name (e.g.,/Server 1/Folder 1/Object A  to /Server 1/Folder 2/Prefix.Object A)
• Bindings occur only for a single match; multiple matches trigger a warning and are skipped to ensure a 1:1 relationship per object.