Rockwell Automation 20D-DL2-CKS1 Import/Export Project Components - Manual (Page 33)

Import and export logic components Chapter 1
are excluded from the import file and they also appear with an Operation of
Undefined if the component does not exist in the project.
During import configuration, these undefined references can be configured as
well. Since there is no definition for these components in the .l5x file, you cannot
overwrite a project component or create a component during the import process,
but you can use an existing component for that reference. You configure which
component in the project you want to connect the reference to, or leave the
reference undefined. An undefined reference that collides with an existing
component defaults to using the project component.
Attention flags
Attention (red) flags alert you to import situations that may be unintended or may
lead to a project that does not verify successfully after import. What they describe
may or may not prevent the import from proceeding. If online, and the project
does not verify successfully when accepting or finalizing edits, the import fails. Not
all attention flags cause a project to fail verification. The red flag indicates the
potential problem and you must decide what you want to do. You can ignore the
attention message or try to change the Final Name or Operation of the
component to resolve the issue.
Tip: Hover the cursor over the attention flag to open a tooltip that explains the issue.
Errors and warnings on import
When an import fails or is canceled, all changes caused by the import are
discarded, leaving the project in the same state it was in before the import, even if
the project is online with the controller. If the import fails, the Import
Configuration dialog box opens with Errors/Warnings selected. To attempt to
import again, inspect the errors and warnings, reconfigure the import, and click
OK.
The Logix Designer application provides the option to set the display language for
project documentation, such as tag descriptions and rung comments, using any of
the supported localized languages. You can store project documentation for
multiple languages in one project file rather than in language-specific project files.
You define the localized languages that the project supports and set the current,
default, and optional custom localized language. The software uses the default
language if the current language's content is blank for a particular component of
the project. You can use a custom language to tailor documentation to a specific
type of project file user. When you configure project documentation in the Logix
Project documentation
Rockwell Automation Publication 1756-PM019E-EN-E - October 2014 33