Import/Paste Configuration Dialog - Configure Routine Properties Overview

Use this dialog box to configure how the routine is imported into the project.
The References folder can contain folders for referenced tags, data types, Add-On Instructions, or Components, depending on the imported routine references.
The Import Content shows the import component and any references in the References folder. The References folder appears if there is logic that references tags, data types, Add-On Instructions, or other components.
When the imported Routine is selected in the import content, the Details pane shows the routine’s properties.
If the operation is set to use existing, then the Description, Type and Number of rungs/lines/sheets/steps fields show the values from the project and appear dimmed. Otherwise, these fields show the values from the import file.
Parameters
Import Name
Shows the name of the routine as read from the import file.
Operation
Identifies what is done with this routine upon import.
The field is pre-populated; however, you can choose from a pull-down list of valid choices.
For more information, see Import Configuration Operations.
Final Name
The final name is the name of the component as it appears in the project after the import. Changing the Final Name changes the name in all places where this component’s Import Name is referenced in the import content throughout the logic, By default, it is initialized to the Import Name.
When you click in the Final Name cell, a pull-down menu appears that lets you pick from a list of all of the components that exist in the program you are importing into.
If the Final Name collides with and existing component in the project and Overwrite is selected, the existing component is overwritten with the logic content and properties of the component in the import file.
If the component in the import file is source-protected, the Final Name field is read-only.
IMPORTANT:
You may either create or avoid a collision by modifying the final name, (based on if you modify the final name to match that of another final name in the project).
Collision Details / Properties
If the imported routine collides with an existing routine in the project, then you see the Collision Details button. Clicking Collision Details causes the Collision Details dialog box to open.
If the routine does not collide with a component, then you see the Properties button. Clicking Properties causes the properties dialog box to open.
Description
Shows the description of the component.
The description can be changed, unless the Operation is Discard or Use Existing.
If the routine in the import file is source-protected, the Description field is read-only.
Type
Shows the routine type.
If the Operation field is set to Overwrite, Create, or Discard, the attribute for the import component is shown the Type field. If the Operation field is set to Use Existing, the attribute for the component in the project is shown in the Type field.
In Program or In Phase
Shows the name of the program or equipment phase in the project into which the routine is imported.
Number of (Rungs / Lines / Sheets / Steps)
Shows content based on the following:
  • If the Operation field is set to Overwrite, Create, or Discard, shows the attribute for the import component.
  • If the Operation field is set to Use Existing, shows the attribute for the component in the project.
  • If the routine is not source-protected or is source-protected and viewable, shows the number of rungs, lines, sheets, steps (whichever is applicable) in the routine, as read from the import file.
  • If the routine is source-protected (and not viewable), shows Source Not Available.
Preserve existing tag values in offline project
When an existing tag has
Operation
 set to
Overwrite
, this check box provides the option to indicate whether data table-backed tag data values are preserved (check box selected) or overwritten (check box cleared) in an offline project as a result of an import. The check box is selected by default.
Keep the following considerations in mind when using the check box:
  • Tag data values are never overwritten in the online controller, regardless of the check box state. The check box only affects values written to the offline project.
  • Data table-backed tag data values include the value of the tag as well as any force-tag values. The state of the check box (selected or cleared) applies to all data table-backed tags in the import.
  • Types for tags that are not data table-backed follow special rules for import and are unaffected by the check box state. Tag configuration data for these types is always overwritten, in both the online controller and the offline project. Tag data values for these tag types are not present in the export file and so are never overwritten anywhere. These types include:
    • ALARM_ANALOG
    • ALARM_DIGITAL
    • AXIS
    • COORDINATE_SYSTEM
    • ENERGY_BASE
    • ENERGY_ELECTRICAL
    • Message
    • MOTION_GROUP (All tags of any Motion-related type cannot be written while online)
Messages
Pay particular attention to warnings that appear in the area below the grid.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.