Possible Cause:
The DDT structure in the new application might differ from the one in the older application. This can happen when types are automatically generated by DTMs, as DTM evolutions may introduce changes.
Additionally, the DDT structure could include hidden variables, causing Control Expert to detect a mismatch between the types and raise an error.
To confirm whether you encounter the same issue:
- Export both DDTs in .XSY format (the one generated from the new DFB and the one already present in the application).
- Open the exported files in Notepad and compare the variable types and names to ensure they are identical.
Example:
If the comparison shows differences:
Update the DDT type used in the DFB so that it matches the one already defined in the application.
Recommendation:
Avoid using DDTs that are automatically generated by DTMs within a DFB, as these can lead to inconsistencies due to DTM evolutions.
