Application notes

The following information is provided to help you better understand the behavior of
FactoryTalk Design Studio
 in other applications or under certain circumstances.
  • The import log file is not updated when the same L5X file is imported multiple times
    An inconsistency occurs that causes the Import log file not to be updated when the same L5X file is imported multiple times.
  • External configuration change dialog opens in error
    Latency sometimes occurs for users connecting from outside of North America when changing device connections. The latency causes the
    External configuration change
     dialog to open in error after selecting
    OK
    .
  • Tag values in the Structured Text Editor
    In some instances, you must use the Tag Editor to view tag values in the Structured Text Editor.
    To open the Tag Editor, in the
    System
     explorer, expand the Program and then expand
    Tags & Parameters
    .
  • Converting User-Defined Libraries to .l5x Files
    AOIs and UDTs defined in User‑Defined Libraries (UDL) are included in the generated
    .l5x
     file from the Convert functionality; however, the fully qualified name (FQN) is not preserved during conversion.
    When multiple objects share the same name but originate from different UDLs, behavior differs by object type:
    • AOIs:
       Only the first AOI found in the controller is included in the
      .l5x
       file; additional AOIs with the same name are not included.
    • UDTs:
       All UDTs are included in the
      .l5x
       file.
      Studio 5000 Logix Designer
       automatically resolves naming conflicts by appending a sequential suffix to duplicate names during import.
  • Copy and Paste Limitations Between Project Libraries and User‑Defined Libraries
    Copying and pasting object definitions from the
    Project Library
     into User‑Defined Libraries (UDLs) is not supported.
    This restriction is intentional to prevent conflicts and broken object references when a library is shared and imported into other projects. Objects defined in the Project Library cannot be shared outside the originating FTDS project; allowing them to be copied into a UDL could result in invalid or unresolved references once the UDL is consumed elsewhere.
  • Conflict Resolution Behavior with Shared Libraries
    In some scenarios where a UDL is being worked by more than one user and changes involve deleting a UDL or updating its metadata (such as, name, description or version) , conflicts may not prompt a resolution dialog during synchronization. In these cases, the latest accepted changes are applied automatically. This behavior is consistent with how FTDS detects conflicts, which is based on file‑level changes rather than individual object states.
    Version history can be used to review past changes, but it cannot recover deleted objects.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal