Hello Robert, As explained, you will find the reduced report "Dialog Test" in the appendix. It only contains the input dialog of the report. No further processing is done. Nothing is written to the database or in files. You can start the report on any model or group in the ARIS database. The error occurs in the report in the same way as in the original report. Briefly to the function: For the process description you can select or deselect options by clicking the corresponding checkboxes. Illogical and impossible combinations are largely avoided by deactivating checkboxes. Preconfigured combinations of options can be called up via 4 buttons. So that a combination can be restored for a later report an option code is formed from the selected options and is displayed in a text field. And finally also printed in the document. This option code, copied from the field, can be entered in the "Option code" field later and all options are then set back to the way they were set. This also works well, but with the exception of the combo boxes (or DropListBoxes). For example, the code: v6f21a0aji1b2c3d5anl should set the zoom factors as follows: VCD "individual" 86%, EPC 100%, FAD 70%; KAD 37%, matrix "automatic", organigram "individual" 37% and repository "automatic". The most right column is only displayed for test purposes and contains a text field at the top with the length of the combo box array and the contents of the list of zoom factors. The text field below contains nSelection for the zoom factor of the EPC. In the script in line 200 (search for"/////") setSelection is executed inside the this.init function. The selection is fix set to index 3. That works fine. The relevant section in the script starts with line 635 (continue searching for "/////"). The important values for the selection are determined beforehand, including nSelection. From 636 the variants of the code lines with setSelection or setDlgSelection are available, which I tried out. Then the text boxes are filled as described above. However, this only applies to the VCD. For the rest of the model types I have not driven the effort. But if this works for the VCD, I can also implement it for the other model types. I hope that this description will be enough to understand the dialogue. Thanks again for your help and kind regards Holger