Difference between revisions of "Aggregation UTA"
From SmartWiki
| Line 9: | Line 9: | ||
==Configuration Steps for an Aggregation UTA== | ==Configuration Steps for an Aggregation UTA== | ||
| + | ===Create Templates/Statuses and Fields=== | ||
| + | Determine the [[status]]es, [[templates]] and common fields from both UTAs that you wish to include in the report. Create the statuses, templates and common fields in the Aggregation UTA in the usual manner. The fields can be either [[standard fields]] or [[custom fields]]. | ||
| + | |||
| + | |||
[[Category:UTA Settings]][[Category:Universal Tracking Application]] | [[Category:UTA Settings]][[Category:Universal Tracking Application]] | ||
Revision as of 11:59, 3 October 2013
Contents
An Aggregation UTA facilitates creating reports that span multiple related Universal Tracking Applications™ (UTAs) by defining the association between equivalent fields in each UTA.
Important aspects of the Aggregation UTA
- The information residing in the Aggregation UTA is a copy of the information from the source UTAs.
- If information in the Aggregation UTA is modified, it does not modify the information in the source UTAs.
- The information in the Aggregation UTA is saved as text.
- Although the fields may be named differently in each UTA, they can map to the same field in the Aggregation UTA.
Configuration Steps for an Aggregation UTA
Create Templates/Statuses and Fields
Determine the statuses, templates and common fields from both UTAs that you wish to include in the report. Create the statuses, templates and common fields in the Aggregation UTA in the usual manner. The fields can be either standard fields or custom fields.
