You can map (link) a table in a metadata model to a Data Federation object, such as a data service or a database operation, or to a table in a database. You can use mapping for both schema validation and aliasing.
When you create a mapping, you validate the mapped object’s schema against the schema of the table in the metadata model. When you deploy the metadata model, this mapping allows you to access the object using the table name in the model—probably the same name you use to access the table in the database.
-
Click the object you want to map (here, GetEmpGivenName) in Enterprise
Explorer, then drag and drop it on the EMP
table in the editor pane.
The metadata model editor checks to ensure that the schema of
the object being dropped matches that of the table. If so, the mapping is made
and the mapped object appears in the editor pane.
A mapped table looks like this:
If you’re performing the mapping for validation, you can stop here.
If the schemas do not match—for example, if the grid object and the table in the model don’t have the same number of columns, or if one or more column data types are different—the mapping is invalid and Data Federation returns an error.
Deploy the model.