Database views and application modeling
You can create forms, Web services, and report data entities from database views when using the Business Application Modeler; however, there are additional steps and limitations to be aware of.
If a view exists in a database, the view will be extracted into the database meta-schema. Views are identified by an icon displayed to the left of the view name in the meta-schema diagram and have the View property selected when you select the view object and look at the Properties view. Unlike tables, you cannot modify a view or its columns by changing values in the Properties view.
When you implement a form, Web service, or report data entity, you can select a view when completing the data control wizard, just as you would select a table. You will not notice any difference between selecting a table or a view when you first implement the entity.
- For a form, you will need to click on the Records tab to access the business record.
- For a Web service, the business record displays.
- The active property is checked (by default.)
- The masterTable property lists the name of the view (by default.)
- The unique key must be set. Click the completion icon (three dots) to open a dialog for specifying the column or columns that comprise the unique key for a row in the view.
Views are treated as read-only by the generated application. Regardless of the functionality settings of the relation leading to a form or Web service entity based on a view, the Business Application Modeler will not generate add, modify, or delete functionality.