Difference between revisions of "Table/Column Alias"
| Line 6: | Line 6: | ||
|- valign="top" | |- valign="top" | ||
|style="width:73%"| | |style="width:73%"| | ||
| − | The following is a complete list of the | + | The following is a complete list of the Reporting "How To" guides, hints, tips and videos that have been created to aid in the configuration and usage of the system. |
|style="width:5%"| | |style="width:5%"| | ||
| | | | ||
| Line 19: | Line 19: | ||
==Table/Column_Alias== | ==Table/Column_Alias== | ||
| − | + | If you happen to create a report that extracts information from different tables such as the Assets, Requests, Asset Types tables, then you would have some fields with the same column names. This in itself is ok except if you are trying to read a report, you would confuse field names. This is where table and field aliases come in. | |
| − | |||
| − | + | You could add an alias for a table such as h_cmdb_asset_types simply because the table name is very long and you wish to shorten it for reference elsewhere. | |
[[File:TableAlias.PNG|600px]] | [[File:TableAlias.PNG|600px]] | ||
| − | The | + | The job of the fieldAlias is slightly different. In tables such as h_cmdbAssets you have a column called h_name. Similarly in table h_cmdb_asset_types, you also have a column called h_name so in order to create a report with these two tables, to avoid confusion, you can use field aliases to differentiate between the two fields. |
[[File:FieldAlias.PNG|600px]] | [[File:FieldAlias.PNG|600px]] | ||
[[Category:How To - Reporting]] | [[Category:How To - Reporting]] | ||
Revision as of 12:52, 20 June 2018
|
The following is a complete list of the Reporting "How To" guides, hints, tips and videos that have been created to aid in the configuration and usage of the system. |
Related Articles |
Table/Column_Alias
If you happen to create a report that extracts information from different tables such as the Assets, Requests, Asset Types tables, then you would have some fields with the same column names. This in itself is ok except if you are trying to read a report, you would confuse field names. This is where table and field aliases come in.
You could add an alias for a table such as h_cmdb_asset_types simply because the table name is very long and you wish to shorten it for reference elsewhere.
The job of the fieldAlias is slightly different. In tables such as h_cmdbAssets you have a column called h_name. Similarly in table h_cmdb_asset_types, you also have a column called h_name so in order to create a report with these two tables, to avoid confusion, you can use field aliases to differentiate between the two fields.
