Chapter 12. Configuring Views
We have connected to a view:
- We can save changes (as the view is updateable).
- We can use ribbon parameters to filter data.
- We see foreign key values instead of names in columns and ribbon parameters.
- We see AccountID, CompanyID, and ItemID in columns and ribbon parameters.
- We see the dbo67.viewPayments database name in the Query List.
- The table is unformatted.
- There are no predefined table views.
Let's fix the "bad news."
Replacing foreign keys values with names
Switch to the payments-configuration workbook, select the EventHandlers worksheet, copy and paste three rows of the Payment table, and change Payments to viewPayments in the TABLE_NAME field. Click Save.
It is easy. We just copied the existing Payments table configuration.
Translating column names
Select the ColumnTranslation worksheet, copy and paste three rows of the Payment table, and change Payments to viewPayments in the TABLE_NAME field. Click Save.
Translating object names
Select the ObjectTranslation worksheet and add the translation for viewPayments and uspPayments:
Now we can switch to the payments workbook, click the Reload, Reload Data and Configuration button, and the Reload Query List button in the Query List group. We see that we have fixed the first three points.
Now we can format the table, add the required table views, and save them to a database using the Table Format Wizard, as described in the previous topics.
After these steps, users will get the same preconfigured and formatted view from a database.