Not all Vocabulary entities must be mapped to corresponding database tables—only those entities whose attribute values need to interact with the external database should be mapped.

In this example, database metadata containing a table named Patient was imported. Because the table’s name spelling matches the name of the entity Patient, the Table Name field was mapped automatically, and displayed in light gray, as shown:
Figure 1. Smart match mapping of Vocabulary Entity

If the automatic mapping feature fails to detect a match for any reason (different spellings, for example), then you must make the mapping manually. In the Table Name field, use the drop-down list to select the appropriate database table to map. The selection is displayed in black, as shown:

Figure 2. Manual Mapping of Valid Vocabulary Entity
If the table name in the source was changed, that table is not in the Datasource's metadata. Choose Import Metadata to pick up the revised table name. But in the entity the property value displays in orange, as shown:
Figure 3. Manual Mapping of Invalid Vocabulary Entity

Click on the Table Name Property Value, and then use the drop-down list to select the appropriate database table to map.