It could be linked to the following reason :
The DDT structure of the new application may not have exactly the same type as the one in the older application (This can occurs with types automatically created by DTMs, due to DTM evolutions)
The DDT structure may contains hidden variables, thus, Control Expert detects that the types are no more identical and the error is raised.
To verify you encounter the same issue, please do export the both DDT in .XSY format (the one coming from the new DFB, and the one already created in the application):
Open the exported files with Notepad and verify both variables types and names are identicals.
For instance:
If it’s not the case, please change the DDT type in the DFB to match the one already created in the application.
Recommended : avoid to use in a DFB, the DDDTs self-generated by the DTMs
The DDT structure of the new application may not have exactly the same type as the one in the older application (This can occurs with types automatically created by DTMs, due to DTM evolutions)
The DDT structure may contains hidden variables, thus, Control Expert detects that the types are no more identical and the error is raised.
To verify you encounter the same issue, please do export the both DDT in .XSY format (the one coming from the new DFB, and the one already created in the application):
Open the exported files with Notepad and verify both variables types and names are identicals.
For instance:
If it’s not the case, please change the DDT type in the DFB to match the one already created in the application.
Recommended : avoid to use in a DFB, the DDDTs self-generated by the DTMs
發佈於: 施耐德電機Taiwan
