When Screen Designer is opened for a display file that was previously edited with CODE Designer, the source is analyzed and information about CODE Designer record groups and indicator sets is stored in XML format as comment at the end of the source code. A record group in CODE Designer is equivalent to a screen in Screen Designer. Any screens, indicator sets and data values that you specify in Screen Designer are added to the XML. You need to save the file in order to save any newly defined screens and preview related information, even if the DDS code has not changed.
When Screen Designer opens a file, it checks for the existence of XML comment lines. If the XML exists, CODE Designer record groups and indicator sets are ignored, since it is assumed that they were previously imported when the XML was created.
The XML information will not be interpreted by CODE Designer. This might cause a problem in the situation where you switch from CODE Designer to Screen Designer (where the XML gets created), switch back to CODE Designer and create new record groups or indicator sets there. If you now, switch back to Screen Designer, the XML already exists and the new record groups and indicator sets will not be added. To work around this problem, open the file with Remote System LPEX Editor, delete the XML, save, and then open with Screen Designer. Since there is no XML, all record groups and indicator sets are interpreted by Screen Designer and added to the XML.