Not all Vocabulary entities must be mapped to corresponding database tables - only those entities whose attribute values need to be persisted in the external database should be mapped. Those entities not mapped should have their Datastore Persistent property set to No. Mapped entities must have their Datastore Persistent property set to Yes, as shown circled in orange in the following figure:
Figure 317. Automatic Mapping of Vocabulary Entity
It is also possible for an external database to contain tables or fields not mapped to Vocabulary entities and attributes - these terms are simply excluded from the Vocabulary.
In the preceding, database metadata containing a table named Aircraft was imported. Because the table’s name spelling matches the name of entity Aircraft, the Table Name field was mapped automatically. Automatic mappings are shown in light gray color, as highlighted above. Also, note that the primary key of table Aircraft is a column named tailNumber. The Vocabulary Editor detects that too, and determines that the property Entity Identity should be mapped to attribute tailNumber.
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 to select the appropriate database table to map, as shown:
