Chapter 12. Configuring Views

Chapter 12. Configuring Views

We have connected to a view:

Sample of a table with foreign keys

Good news:

  1. We can save changes (as the view is updateable).
  2. We can use ribbon parameters to filter data.

Bad news:

  1. We see foreign key values instead of names in columns and ribbon parameters.
  2. We see AccountID, CompanyID, and ItemID in columns and ribbon parameters.
  3. We see the dbo67.viewPayments database name in the Query List.
  4. The table is unformatted.
  5. 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.

Sample of validation lists in the EventHandlers configuration table

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.

Sample of column translation

Translating object names

Select the ObjectTranslation worksheet and add the translation for viewPayments and uspPayments:

Sample of object name translation

 

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.

Configured table with foreign keys

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.

Configured and formatted table with foreign keys in Microsoft Excel