Performing the following steps on an XLD file causes the alias to get lost.
i.e.,
Figure 2 After editing the XLD file.
The alias gets lost because when the variable is renamed in the XLD file, the new name does not get associated in the unique
DDT variable 'ManageKet' attribute (See example below). This managed key is generated by Control Expert using the variable name that is aliased with a DDT variable.
The XLD file is not intended to be edited by the user.. The purpose of the XLD export file is intended for a user to be able export a logic section and import into another Control Expert project.
- Export the logic section from a project that contains alias to the DDT reference in the logic.
- Edit the XLD file using a text editor (i.e., WordPad, etc.) to rename a variable.
- Saving the changes.
- Importing he XLD file back into the same project results, in the renamed variable not being shown in the 'Import Trouble Report' window and the alias getting deleted from the associated Device DDT variable..
i.e.,
The alias gets lost because when the variable is renamed in the XLD file, the new name does not get associated in the unique
DDT variable 'ManageKet' attribute (See example below). This managed key is generated by Control Expert using the variable name that is aliased with a DDT variable.
The XLD file is not intended to be edited by the user.. The purpose of the XLD export file is intended for a user to be able export a logic section and import into another Control Expert project.
게시 대상:슈나이더 일렉트릭 Korea
