After you have designed a form, you must save and compile it before it can be run. Usually, you do this when you have finished designing the form. However, you may want to save a form that is not yet finished and before it can be compiled, particularly if the form contains C/AL code. You can also test compile and test run a form without closing or saving it.
Saving and Closing a Form
A designed form is closed when Form Designer is closed. When you close a form, you need to decide whether you want to save the form. If the form has not yet been saved, you must assign it an ID and a name. The ID must be unique and follow the rules for numbering objects. Your local Microsoft Certified Partner will provide you with this information.
The Compiled option field is selected by default. If your form is not ready to be compiled, remove the check mark. Click OK to save the form. To save a form without closing it, click File, and click then Save or Save As. You can also use Save As to give a form a new name.
Compiling a Form
Forms, like the other objects in C/SIDE, must be compiled before they can be run. As described earlier, you can compile a form when you save it. While you are designing a form, you may want to test compile it to find possible errors. This is useful when the form contains C/AL code in triggers. To test compile a form when you are designing, click Tools, and then click Compile.
Running a Form
In a finished application, your forms are incorporated into menus or they are called from other forms. However, when you are designing forms, you will often want to run them before they are integrated into an application. You can run a form from the list of forms in Object Designer. To do this, select the form and then click Run. To run forms from inside Form Designer, click File, and then click Run.