Data Validation Option Best Practices

Data Validation Option Best Practices

Suggested Naming Conventions

Suggested Naming Conventions

While Data Validation Option does not require any specific naming standards for metadata objects, having standard conventions for object names makes managing repository objects easier.
The following table a suggested naming convention that has been used at some customer sites:
OBJECT TYPE
SUGGESTED NAMING STANDARD
Table Pair
tp_<project>_<TableA_name>-<TableB_name>
Single Table Constraint
st_<project>_<Table_name>
Lookup View
lv_<project>_<source_table>-<lookup_table>
SQL View
sv_<project>_alias_name
Join View
jv_<project>_alias_name
Aggregate View
av_<project>_alias_name
Prefixing objects makes it very easy to identify them in the GUI, or filter them when possible.
For example, in the folder shown in the image below, it is easy to separate the table pairs from the single tables:
This image shows tables pairs and single tables in a folder, and depicts how easy it is to seperate them
It is also easy to filter to find a view in the data source selection dialog box, as shown in the image below:
This image shows how easy it is to filter to find a view

0 COMMENTS

We’d like to hear from you!