Report Data Warehouse

Transcription

1 Report Data Warehouse Last updated on Monday, July 08, 2013 Copyright Autotask. All Rights Reserved. Trademark Information All Autotask products are trademarks or registered trademarks of Autotask. All other brand and product names mentioned herein are trademarks or registered trademarks of their respective holders.

2 Table of Contents Autotask Report Data Warehouse 3 About Report Data Warehouse Views 1 Report Data Warehouse View Descriptions 2 Report Data Warehouse Updates 14 Index 44 Page 2 of 8

3 Autotask Report Data Warehouse About Report Data Warehouse NOT E : The R e port Da t a W a re house is a cont ra ct -ba se d se rvice a nd a cce ss re quire s a unique Use rna me a nd Pa ssword. Cont a ct Aut ot a sk t o e na ble your R e port Da t a W a re house. R e fe r t o "Acce ssing t he Aut ot a sk R e port Da t a W a re house Se rve r" on pa ge 3. The Autotask Report Data Warehouse provides access to key areas of your organization's Autotask data. You can then use your preferred report creation tool. The Data Warehouse does not provide direct access to the Autotask database base tables; instead it provides views that map to one or more tables. These views are designed to allow for more efficient retrieval of selected data most commonly used by Autotask customers for reporting purposes. By exposing views instead of the base tables, the Report Data Warehouse prevents the need to update your reports any time a change is made to the tables. NOT E : Alt hough t he vie ws provide e xt e nsive a cce ss t o t he da t a in your Aut ot a sk da t a ba se, t he y do not provide a cce ss t o a ll da t a. Any reporting tool that can access Microsoft SQL Server views can use the Autotask Report Data Warehouse. Because a wide variety of these tools exist, and we cannot predict our customers' tool preferences, Autotask does not support any specific tools or provide information specific to any tool. The Report Data Warehouse documentation set includes additional topics to accompany this overview: Autotask Report Data Warehouse View Descriptions: Provides an alphabetic listing of all views included in the Report Data Warehouse data model along with a description of each view. "Report Data Warehouse View Descriptions" on page 2. Autotask Report Data Warehouse Updates: This topic provides a chronological list of all updates made to the Report Data Warehouse. Refer to "Report Data Warehouse Updates" on page 14. Autotask Report Data Warehouse ERD.vsd: An interactive Entity Relationship Model diagram that allows you to click a view or relational connector to display selected properties of the view and its relationships. To access this document, click Autotask Report Data Warehouse ERD. NOT E : The Aut ot a sk R e port Da t a W a re house is a cont ra ct -ba se d se rvice ma de a va ila ble for t he conve nie nce of a ut horized Aut ot a sk cust ome rs. Unautho r iz ed use o f the Report Data War eho use o r attempts to c o mpromise Report Data War eho use ser vic es will be in dir ec t vio latio n o f the c usto mer 's Auto task c o ntr ac t. T IP: T o find o ut the latest Report Data War eho use updates a nd t o sha re informa t ion wit h ot he r use rs, we re comme nd t ha t you subscribe t o t he Aut ot a sk Communit y R e port Da t a W a re house forum. Accessing the Autotask Report Data Warehouse Server Any reporting tool that can access Microsoft SQL Server views can access the Report Data Warehouse server. Report Data Warehouse is a contract service. Please contact Autotask to arrange access. When Autotask enables your Report Data Warehouse, Customer service provides the following information: Page 3 of 8

4 The zone specific URL where your reporting tool can access the server A unique Report Data Warehouse user name and password. Your usual Autotask login information will not provide access. For access, use port Because there are numerous reporting tools in use, Autotask cannot provide specific instructions on how to configure reporting tool access to the server. To achieve the best results, read "General Information and Considerations" on page 4. General Information and Considerations Data Updates Each Report Data Warehouse database is refreshed every day at 4 AM Eastern Time for North American customers and 4 PM Eastern Time for Global Customers from a backup of the customer's production database. Be aware that when the database is being refreshed, the following will occur: Any currently-running queries will be aborted. Any connected user will be disconnected. Refresh time depends on the size of the customer's database. Typical refresh time will be less than 10 minutes. Considerations The Autotask Report Data Warehouse is designed for reporting purposes and provides read-only access to data. The Report Data Warehouse views do not provide access to all the data in your Autotask database. The views were constructed to provide efficient access to key data used for reporting purposes. T IP: "R e port Da t a W a re house Vie w De script ions" on pa ge 2 provide s a list of t he curre nt ly a va ila ble vie ws a nd a brie f de script ion of t he t ype of da t a provide d by e a ch vie w. You cannot create indexes or additional views for the data model. If you have a need that cannot be met by the available design, contact Autotask Support with your suggestions. Autotask has designed the Report Data Warehouse to provide fast and efficient access to data; however, as in any reporting environment, the more complex the query, the longer it will take to run. Unauthorized use of the Report Data Warehouse, or attempts to compromise Report Data Warehouse services, will be in direct violation of the customer's Autotask contract. Page 4 of 8

5 Collation Settings The database collation setting controls the sort order for text fields. The Report Data Warehouse uses different collation settings for localized language versions so words are sorted properly based on the alphabet of the localized language. The following table lists the collation setting for each language version of Autotask. Language English Spanish French Italian Chinese German Japanese Collation Setting SQL_Latin1_General_CP1_CI_AS Spanish_Modern_CI_AS French_CI_AS SQL_Latin1_General_CP1_CI_AS Chinese_PRC_CI_AS SQL_Latin1_General_CP1_CI_AS Japanese_CI_AS About the Report Data Warehouse ERD Interactive Visio Model With nearly one-hundred-sixty views with extensive interdependencies, a single, static map of the Report Data Warehouse model would be too cumbersome to be useful, as would any listing of views that attempted to incorporate all view properties and fields. The Report Data Warehouse ERD is an interactive Visio model of the Report Data Warehouse data structure. It allows you to zoom in on a view, click to select the view or a connector between two views, and see the database properties of the selected item. Page 5 of 8

6 The properties appear in the Database Properties window at the bottom of the screen. You can select which property options to display from a list on the left side of the Database Properties window. The content of the Properties window varies depending on whether you click on a view or a connector. NOT E : To a cce ss a ll of t he ER D int e ra ct ive fe a t ure s, t his docume nt re quire s Microsoft Visio. You ca n vie w t he ER D wit h fe we r int e ra ct ive fe a t ure s using t he fre e Visio Vie we r a va ila ble from Microsoft. F or a ddit iona l informa t ion on t he fre e Visio Vie we r, re fe r t o "Using t he F re e Microsoft Visio Vie we r" on pa ge 8. Accessing View and Relationship Properties in the ERD Using Visio Users with Microsoft Visio installed on their computer can use the Autotask Report Data Warehouse ERD Interactive Visio Model Document to view a representation of any individual data warehouse view, including the available columns and the relational properties. T IP: If you a re unsure of which vie w is like ly t o cont a in t he da t a you ne e d, che ck t he "R e port Da t a W a re house Vie w De script ions" on pa ge 2 t opic. 1. To view the properties of a view or relationship, locate the view of interest in the model diagram. Use the Visio Find feature (Edit > Find) to locate the view by name. Note that all view names begin with wh_ and all words in a view name are separated by an underscore (_). If part of the view name appears in multiple views, use Find Next to move through the views until you locate the correct view. For example, when you search for wh_account, the Find feature may take you to wh_account_location; click Find Next until you reach the correct view. Page 6 of 8

7 T IP: You must se a rch by t he e xa ct na me. If you a re unsure of t he vie w na me, use t he "R e port Da t a W a re house Vie w De script ions" on pa ge 2 t opic t o de t e rmine t he na me. 2. To display the properties of a view, click to select the View. 3. To display the relationship between views, click the Connector between two views. Note that in Relational notation, the arrow at the end of the relationship line points to the parent view. 4. If the Database Properties window is not open at the bottom of the screen, right-click the selected view or relational connector and select Database Properties. 5. In the Database Properties window, select the desired category from the left hand Categories list. The property categories for views and relational connectors are described below. NOT E : Be ca use t he ER D is re a d only, most of Cha nge s t o t he cont e nt of t he origina l docume nt a nd a ddit ions ma de t o t he Inde xe s, Trigge rs, Che ck opt ions, or vie w re la t ionships will not ha ve a ny e ffe ct on t he R e port Da t a W a re house. About the View Property Categories When you click to select a view in the Report Data Warehouse, the Report Data Warehouse ERD Properties Dialog box displays information about the selected view. You can select from the list of Categories to view different types of information. The categories include the following: Definition - The Definition category provides the physical and conceptual name for the selected view. Columns - The most informative Category for views in the Report Data Warehouse is the Columns category. This category displays a list of all columns, that is, data fields, in the view and indicates the data type, whether the field is required, and whether it is a primary key. NOT E : The Add, R e move, Edit, a nd Move Down opt ions will not a ffe ct t he R e port Da t a W a re house Mode l. Page 7 of 8

8 Primary Key - The Primary Key category indicates the column specified as Primary Key and provides the Physical Name. Note that you cannot change the Primary Key or its specification. The Indexes, Triggers, Check, Extended, and Notes categories are not applicable to this model. About the Relational Connector Property Categories When you click to select Relational Connector line in the Report Data Warehouse, the Report Data Warehouse ERD Properties Dialog box displays information about the selected connector. The Name, Miscellaneous, and Referential Action categories are not applicable to this model and you cannot use them to alter the database model. The most informative category for relationships in the Report Data Warehouse is Definition. Definition - Click this category to display the parent-child relationship indicated by the selected relational connector, indicating the shared column (field) and the direction of the relationship. Note that for views with a large number of fields, you can scroll through the list until the association arrow aligns with the correct field. Using the Free Microsoft Visio Viewer If you do not have access to a full version of Microsoft Visio, you can download the free Visio Viewer from the Microsoft site. The viewer opens Visio documents in your web browser. It does not provide all interactive features available for the ERD through the Visio application. It does allow you to do the following when viewing the Report Data Warehouse ERD: Search for and enlarge a View in the ERD to see which columns it contains. Identify the Primary Key if the view is Parent in relation to any other views, and identify the Foreign Keys in a view. Double click a relationship line to highlight the line in order to trace the relationship between views (the connector line arrow head always points to the parent). Unlike the full featured Visio, there is no way to immediately see which columns are associated with which line. Download the viewer from the Microsoft download site. Search the site for Visio Viewer. Page 8 of 8

9 About Report Data Warehouse Views About Report Data Warehouse Views The Autotask Report Data Warehouse does not provide direct access to the Autotask database base tables; instead it provides views that map to one or more tables. These views are designed to allow for more efficient retrieval of key data for reporting purposes. By exposing views instead of the base tables, the Report Data Warehouse prevents the need to update your reports any time a change is made to the tables. NOT E : The R e port Da t a W a re house vie ws we re const ruct e d t o provide more e fficie nt a cce ss t o ke y busine ss da t a. Alt hough t he vie ws provide e xt e nsive a cce ss t o t he da t a in your Aut ot a sk da t a ba se, t he y do not provide a cce ss t o a ll da t a. To view a list of all views included in the Report Data Warehouse Data Model along with a brief description of each view, refer to "Report Data Warehouse View Descriptions" on page 2. T IP: Use t his Vie w De script ions docume nt t o find which vie ws a re like ly t o hold t he da t a you ne e d. For additional information about each view, including a list of all columns and information regarding relationships with other views, use the Autotask Report Data Warehouse ERD.vsd interactive Visio diagram. The Autotask Report Data Warehouse ERD.vsd requires Microsoft Visio or the free Visio Viewer. Note that not all interactive features are available with the free viewer, but you can search for views, see which columns are included, and double click to highlight relational connectors. For information on downloading the free viewer, refer to the Report Data Warehouse topic in the Autotask Online Help system. For additional information about the interactive Visio diagram, Report Data Warehouse access information, and considerations regarding the Autotask Report Data Warehouse, refer to "Autotask Report Data Warehouse" on page 3. Page 1 of 44

10 Report Data Warehouse View Descriptions Report Data Warehouse View Descriptions The following table lists all views currently available in the Autotask Report Data Warehouse. All view names begin with wh_ and the list is sorted alphabetically by the label following the wh_. A brief description of the view appears next to the view name. For details on which columns are available in each view, use the interactive Visio ERD model. Refer to "About Report Data Warehouse Views" on page 1 in this document for additional information about the Visio ERD model. View Name wh_account wh_account_contact wh_account_contact_ udf wh_account_location wh_account_resource wh_account_type wh_account_udf wh_address_format wh_allocation_code wh_allocation_code_ group wh_allocation_code_ rule wh_allocation_code_ type wh_allowed_time_off wh_appointment wh_approver_resource wh_approver_type wh_attachment Description Stores the base fields that describe Accounts, for example, those fields found in the Account Detail view. Userdefined fields are in wh_account_udf. Account contact fields are in wh_account_contact. Stores base fields that describe account Contacts, for example, those fields in Account Detail > Contacts and Contacts > Contact Detail. User-defined fields are in wh_account_contact_udf. Stores User-defined fields for account Contacts. Base fields are in wh_account_contact. Stores fields that describe Locations associated with an Account ID and specified in Quotes generated through the Autotask Quote Management extension. Maps Accounts to resources that are members of client teams associated with the accounts as configured through Directory > Accounts > Open Account > Team. Stores the available Account Types as displayed in the Account Type drop-down menu in the Add Account or edit Account windows. Stores User-defined fields for Accounts. Base fields are in wh_account. Stores fields that describe address formats available for display in Autotask. Stores base fields for Allocation Codes. Allocation Codes are configured through Admin/Setup and applied to resource activities. Enumerates Allocation Code Groups. Stores Allocation Code Rules as applied to Expense Categories configured through the Rules tab of the Add or Edit Expense Category window, accessed through Admin/Setup >Timesheets > Expense Reports > Expense Categories. Enumerates Allocation Code Types. Allocation code types are pre-set and assigned to an allocation code based on the Admin/Setup folder from which the code is added. For example, all Allocation Codes added through Admin/Setup > Site Configuration > Company Setup > General Allocation Codes tab are of General type. Stores maximum allowed Time Off limits, that is, PTO, vacation, etc. for each resource for the calendar year. Stores fields that describe Appointments as scheduled through the Service Desk module. Maps Resources designated as timesheet or expense approvers to their approvees. Enumerates Approver types, for example, timesheet approver. Stores fields that describe Attachments added to notes, resources, accounts, etc. Page 2 of 44

11 Report Data Warehouse View Descriptions View Name wh_attachment_ account wh_attachment_ expense_report wh_attachment_note wh_attachment_ project wh_attachment_ resource wh_attachment_task wh_attachment_type wh_billing_item wh_billing_item_type wh_billing_milestone wh_billing_milestone_ status wh_billing_preference_ type wh_business_hours wh_competitor wh_contract wh_contract_block wh_contract_block_ notification_rule NOTE: This view along with "wh_contract_ block_repurchase_rule" has been replaced by "wh_contract_repurchase_notification_rule" and "wh_contract_ repurchase_notification_rule_recipient" - - use the new views. Description Maps Attachments associated with accounts to the associated accounts. Maps Attachments associated with expense reports to the associated expense reports. Maps Attachments associated with notes to the associated notes. Maps Attachments associated with projects to the associated projects. Maps Attachments associated with resources to the associated resources. Maps Attachments associated with tasks to the associated tasks. Enumerates types of attachments, for example, URL or resource photo attachment. Stores fields that describe items that have gone through the approve & post process, that is, items submitted for billing. Enumerates Billing Item Types. Billing item types are system generated and static. Stores fields describing Billing Milestones as specified in the Contracts module and applied to contracts. Enumerates billing Milestone Statuses, for example, In Progress, as applied to fixed price contracts. Enumerates the Billing Preference Types available to associate with contracts in the Contract Wizard. Stores the fields that describe location specific preferences for location hours, for example, time zone. Stores the fields that describe Competitors, configured through Admin/Setup > CRM > Accounts and optionally associated with Accounts. Stores the fields that describe Contracts, for example, those fields that appear in the Contract Wizard and edit Contract views. Stores fields that describe Contract Blocks associated with Block Hour contracts. Stores fields that describe Notification rules for Block Hour Contracts as specified through the Rules option available when you right-click a block hour contract in the Contracts > Contracts search results grid and select Open Contract. Page 3 of 44

12 Report Data Warehouse View Descriptions View Name wh_contract_block_ repurchase_rule NOTE: This view along with "wh_contract_ block_ notification_rule " has been replaced by "wh_contract_repurchase_notification_rule" and "wh_contract_ repurchase_notification_rule_recipient" -- use the new views. wh_contract_category wh_contract_rate wh_contract_repurchase_notification_rule wh_contract_repurchase_notification_rule_ recipient wh_contract_service wh_contract_service_ adjustment wh_contract_service_ bundle wh_contract_service_ bundle_adjustment wh_contract_service_ bundle_period wh_contract_service_ period wh_contract_type wh_country wh_crm_note wh_crm_note_type wh_crm_todo Description Stores rules for repurchase of Block Hour Contract blocks as specified through the Rules option available when you right-click a block hour contract in the Contracts > Contracts search results grid and select Open Contract. Enumerates Contract Categories as configured through Admin/Setup > Contracts > Contract Categories and available to assign to a contract. Stores the fields that describe Rates configured for contracts. Stores the fields that describe all Repurchase/Notification rules created for Block, Retainer, and Per Ticket contracts. Rules are added from Contract Summary view (Search Contracts > Open Contract) > Notification Rules. All rule types do the following: When a contract unit (block, retainer, or Per Ticket purchase) gets below the rule threshold it will automatically repurchase the number of units at the rate specified in the rule and send an to all the specified recipients. Refer to "wh_contract_repurchase_notification_rule_ recipient". Stores the contacts and resources specified to receive notification when a contract repurchase/notification rule is triggered. Either resource_id or account_contact_id will always be null. Note that "additional_ _ addresses" are stored in "wh_contract_repurchase_notification_rule". Maps Contracts to Services associated with the contracts. Stores fields that describe Adjustments made to contract service charges. Maps Contracts to associated service bundles. Stores fields that describe Adjustments made to Charges for Service Bundles associated with contracts. Maps Contracts to time periods set for Service Bundles associated with the Contracts. Maps Contracts to time periods set for Services associated with the Contracts. Enumerates Contract types, for example, Fixed Price or Block Hour. Stores the countries available in the Country lists in the Autotask interface along with their display name and assigned address format. Stores fields that describe Notes associated with the CRM module. Enumerates the Note Types available to assign to CRM Notes. Stores the fields that describe CRM To-dos and appear in New or Edit To-do windows in the CRM module. Page 4 of 44

13 Report Data Warehouse View Descriptions View Name wh_crm_todo_type wh_currency wh_department wh_department_ resource wh_ _type wh_expense_item wh_expense_item_type wh_expense_payment_ type wh_expense_report wh_expense_status wh_export_batch wh_export_type wh_gender wh_general_ledger wh_holiday wh_holiday_set wh_hours_of_operation wh_installed_product wh_installed_product_ udf Description Enumerates the Types available to assign to CRM To-do. Stores fields that describe Currency types associated with expense line items that appear in Expense Reports. Stores fields that describe the Departments configured through Admin>Setup > Site Configuration > Company Setup and associated with Locations, Roles, and Resources. Maps Departments to the Resources associated with the departments. Enumerates the types available to associate with Resource addresses. Stores the fields that describe Expense Line Items that are added to an expense report. Data for the overall expense report is in wh_expense_report. Enumerates the Expense Types available to associate with an expense line item. Enumerates the Payment Types available to associate with an expense line item. Stores the fields that describe Expense Reports. The fields that describe individual line items added to the expense report are in wh_expense_item. Enumerates the Statuses available to apply to expense reports. Stores the fields that describe Exported Data. Enumerates Export Types available to associate with an export. Enumerates gender choices to assign to resources. Stores the fields that describe General Ledger Names and Codes as configured through Admin/Setup > Contracts (and Billing) > Financials and applied to cost allocations. Stores the fields that describe individual Holidays. Holidays are grouped into holiday sets, which are stored in wh_holiday_set. Stores the fields that describe Holiday Sets. Holiday Sets are configured groups of the selected individual holidays stored in wh_holiday. Stores the fields that describe hours during which service is available for a location, including regular business hours and extended hours, as specified in the Edit Location page, Hours tab. Stores base fields that describe Configuration Items (that is, Installed Products). Configuration Items are Products that are associated with an Account and managed through CRM >Configuration Items. General Configuration Item User-defined Fields (UDFs) are stored in wh_installed_product_udf. Configuration Item site configuration User-defined Fields are stored in wh_site_configuration_udf. Pivoted view. Stores User-defined Fields for Configuration Items (Installed Products). Base fields for Configuration Items are stored in wh_installed_product. For non-pivoted view of Installed Product UDF data, refer to wh_udf_value_installed_product. wh_installed_product_ udf_group wh_installed_product_ udf_group_detail Enumerates Installed Product UDF Groups. Groups are unique to Installed Product UDFs. Stores the fields that describe Installed Product UDF Groups. Page 5 of 44

14 Report Data Warehouse View Descriptions View Name wh_inventory_item wh_inventory_item_ serial wh_inventory_location wh_inventory_order wh_inventory_order_ product wh_inventory_order_ status wh_inventory_receive wh_inventory_receive_ serial wh_inventory_transfer_ serial wh_inventory_transfer wh_inventory_transfer_ type wh_invoice wh_issue_type wh_key_account_icon wh_line_of_business wh_location wh_login_log_autotask wh_login_log_client_ access wh_market_segment wh_name_salutation wh_name_suffix wh_note Description Stores the base fields that describe the inventory and the current on hand quantity. Stores the serial numbers that are assigned to inventory items. The relationship between the item and the serial numbers is a one-to-many relationship. Stores the base fields that describe inventory locations. Stores base fields that describe the inventory orders. Stores the product fields in an inventory order including the quantity ordered and the location it is ordered for. Enumerates the statuses available to assign to inventory orders. Stores the fields that describe items received on inventory orders. Records the serial numbers of received items. Maps serial numbers to multiple inventory item instances on an inventory transfer. Stored base fields that describe the transfer of the inventory items between inventory locations, projects or tickets. Describes the type of the inventory transfer. The type could be between inventory locations, projects or tickets. Stores the fields that describe Invoices generated through the Approve and Post process. Stores the fields that describe the Issue Types configured through Admin/Setup > Service Desk > Issue and Subissue Types and available to assign to Service Desk tickets. Stores the fields that describe Autotask Key Account Icons, icon images that provide a visual identifier to classify Accounts. Stores fields that describe company Lines of Business that are configured through Admin/Setup > Site Configuration > Company Setup and used to categorize Projects. Stores fields that describe company Locations configured through Admin/Setup > Site Configuration > Company Setup and associated with Resources. Stores the fields that track login activity for the Autotask application. Stores the fields that track login activity for the Client Access application. Client Access is an Autotask add-on that allows clients to be assigned project tasks and to access project information. Stores the fields that describe Market Segments, configured through Admin/Setup > CRM > Accounts and associated with Account detail information. Stores the fields that describe the salutations available to precede a contact or resource name. Stores the fields that describe suffixes available to follow a contact or resource name. Stores the fields that describe Notes that users can add to several Autotask entities, for example, Account, Task, Contract. Page 6 of 44

15 Report Data Warehouse View Descriptions View Name wh_note_account wh_note_account_contact wh_note_contract wh_note_parent_type wh_note_project wh_note_publication_ type wh_note_task wh_note_type wh_opportunity wh_opportunity_ advanced_fee_label wh_opportunity_stage wh_opportunity_stage_ change wh_opportunity_status wh_opportunity_udf wh_overdraft_policy wh_payment_term wh_payment_type wh_payroll-type wh_pending_overall wh_performance_metric Description Maps Account Notes to the associated accounts. Maps Contact Notes to the associated account contact. Maps Contract Notes to the associated contracts. Enumerates the Note Type Categories available to assign to a Note Type. The Note Parent Type determines where a note type is available in Autotask and what entity it will be associated with. For example, a Note Type with Note Parent Type of Task is available to assign to notes added to Tasks; if the Note Parent Type is Project, the note is available to assign to notes added to Projects. Maps Project Notes to the associated project. Maps publication types to notes as specified through Publish Choice for Project notes. Maps Task Notes to the associated tasks. Enumerates Note Types configured through Admin/Setup > Site Configuration > System Note Types and assigned to notes. Stores base fields that describe the Opportunities associated with accounts and managed through the CRM module. User-defined Fields are in wh_opportunity_udf. Enumerates the Advanced Fee field labels that are configured through Admin/Setup > CRM > Dashboard and appear in CRM > Opportunity add and edit views. Enumerates Opportunity Stages configured through Admin/Setup > CRM > Opportunities and assigned to opportunities. Stores the fields that specify dates when Stage changes occur for Opportunities. Enumerates Opportunity Statuses available to assign to opportunities. Pivoted view. Stores User-defined Fields for Opportunities. Base fields are in wh_opportunity.for non-pivoted view of Opportunity UDF data, refer to wh_udf_value_opportunity. Enumerates Overdraft policies available to assign as a Rule to the Expense Categories that are configured through Admin/Setup > Timesheets > Expenses >Expense Categories (Overdraft Policies appear on the Rules tab). Expense Categories are applied to Expense Reports. Stores fields that describe Payment Terms as configured through Admin/Setup > Contracts (and Billing) > Financials and applied to Invoices. Stores fields that describe Payment Types as configured through Admin/Setup > Contracts (and Billing) > Financials and applied to some Contract types. Enumerates the type of payroll configurations, for example, salary, available to assign to a resource through Admin/Setup > Site Configuration > Resources > Resources > HR tab. Stores fields that describe all pending billing items, that is, items submitted for billing but not yet posted. Stores fields that describe Performance Metrics for service desk and CRM sales quotas as configured in Admin/Setup > CRM > Dashboard and displayed on the Dashboard. Page 7 of 44

16 Report Data Warehouse View Descriptions View Name wh_performance_metric_type wh_phase_budget wh_posted_overall Description Enumerates Performance Metric Types available to assign to performance metrics. Maps Project Phases to Contract Rates to model phase budgets. Contains data used for profitability reporting. Use this view to sum up revenue and cost for a contract. NOTE: There may not be a row for each individual billing item in this view. Time entries that were "split" in Approve and Post are combined back into a single row in this view. wh_priority wh_product wh_product_category wh_product_udf wh_project wh_project_account_ contact wh_project_calendar wh_project_calendar_ display_type wh_project_category wh_project_cost wh_project_cost_type wh_project_phase wh_project_resource wh_project_status wh_project_type wh_project_udf Stores fields that describe Priorities as configured through Admin/Setup > Service Desk and assigned to tickets and tasks. Stores base fields that describe Products as defined through Admin/Setup > Products and Services > Products. User-defined Fields are in wh_product_udf. Stores Product Categories as configured through Admin/Setup > Products and Services > Products and assigned to Products. Pivoted view. Stores product User-defined Fields. Base fields are in wh_product.for non-pivoted view of Product UDF data, refer to wh_udf_value_product. Stores base fields that describe Projects as defined through the Projects module. User-defined Fields are in wh_ project_udf. Maps Projects to account contacts to store the project's client team. Stores the fields that describe Project Calendar items. Enumerates the Display Types available for the project calendar. Enumerates the Project categories available to associate with a Business Objective configured through the Business Objective wizard in Projects module > New > Business Objective or Projects module > Projects > Business Objectives > New > Business Objective. Stores the fields that describe Costs associated with a Project. Enumerates Cost Types available to assign to projects through Costs in the Project Summary view. Stores the fields that describe Project Phases. Maps Projects to Resources to store the project's internal resource team. Enumerates the Project Statuses configured through Admin/Setup > Projects and assigned to projects. Enumerates the Project Types available to assign when creating a project. Pivoted view. Stores User-defined Fields for projects. Base fields are in wh_project. For non-pivoted view of Project UDF data, refer to wh_udf_value_project. wh_queue wh_queue_resource Stores the fields that describe service desk Queues as configured through Admin/Setup > Service Desk > Queues and associated with Resources and assigned to service desk tickets. Maps service desk Queues to their associated Resources. Page 8 of 44

17 Report Data Warehouse View Descriptions View Name wh_quote wh_quote_item wh_rate_modification_ type Description Stores the fields that describe Quotes that are generated through the Autotask Quote Management extension. Individual quote line items are in wh_quote_item. Stores the fields that describe Line Items associated with Quotes generated through the Autotask Quote Management extension. The overall quote is in wh_quote. wh_recurring_ticket Stores the fields that describe Recurring Service Desk Ticket Masters as created through Service Desk > Tickets > New > Recurring Ticket. wh_reference_attribute wh_resource Enumerates Modification Types available for selection in the Contracts module right-click menu option, Copy Contract Wizard. The Modify Type field appears in the Add Rate view accessed through the Roles view in the wizard. wh_resource_rate_history wh_resource_type wh_role wh_sales_lead wh_sales_order wh_sales_quota wh_sales_region For workflow rules, enumerates the available Condition and Action attributes. Stores the fields that describe the company's Autotask Resources, that is, all users with an Autotask License, as added and managed through Admin/Setup > Site Configuration > Resources. Stores the Rate History for resources as new rates are applied through Admin/Setup > Site Configuration > Resources. Enumerates the types that can be assigned to Autotask Resources, for example, employee or contractor through Admin/Setup > Site Configuration > Resources > Resources > HR tab. Stores the fields that describe the Roles that represent resource activities and are associated with Resources and Departments. Stores the fields that describe Sales Leads as configured through Admin/Setup > CRM > Opportunities and applied to Opportunities in the CRM module. Store the fields that describe a Sales Order, a Procurement module feature that is created when the Won Opportunity Wizard is used to close an Opportunity. Can be edited in the CRM module. Stores the fields that describe Sales Quotas specified for Resources through Admin/Setup > CRM > Dashboard and displayed in the Resources' CRM Dashboards. Stores information that describes Sales Regions configured through Admin/Setup > CRM > Accounts > Regions and associated with Territories as a Parent Region. wh_salutation This view has been removed. Refer to "wh_name_salutation" on page 6. wh_service Stores the fields that describe Services as configured through Admin/Setup > Products and Services > Services > Services and applied to contracts. wh_service_bundle Stores the fields that describe Service Bundles as configured through Admin/Setup > Products and Services > Services > Service Bundles and applied to contracts. wh_service_bundle_service wh_service_call wh_service_call_task wh_service_call_task_ resource Maps Services to Service Bundles that include the service. Stores the fields that describe service desk Service Calls that are generated through the Service Desk module and can be associated with tickets, tasks, and resources. Maps Service Calls to associated project tasks and service desk tickets. Maps Service Calls to resources associated with tasks assigned to the Service Call. Used to determine whose calendar shows service calls for multi-resource project tasks. Page 9 of 44

18 Report Data Warehouse View Descriptions View Name wh_service_level_agreement wh_service_level_agreement_event_dates wh_service_level_agreement_objective wh_service_level_agreement_event_type wh_service_period_type wh_shipping_type wh_site_configuration_ udf Description Stores the fields that describe Service Level Agreements (SLAs), for example, those fields that appear in the Add/Edit Service Level Agreement page. Stores the fields that specify date/ time information for the occurrence of Service Level Agreement events. Stores the fields that describe Service Level Agreement (SLA) objectives, for example, those fields that appear in the Add/Edit Service Level Agreement page under Objectives. Enumerates the Service Level Agreement Event Types available to map to ticket statuses when using service level agreements in Autotask. Enumerates Service Period types available to assign to Services configured through Admin/Setup > Products and Services > Services > Services and applied to contracts. Stores the fields that describe Shipping Types configured through Admin/Setup > CRM > Opportunities > Shipping Types and applied to quotes generated through the Autotask Quotes Management module. Pivoted view. Stores User-defined Fields for site configuration information for Configuration Items (Installed Products). Base fields are in wh_installed_product.for non-pivoted view of Site Configuration UDF data, refer to wh_ udf_value_site_configuration. wh_skill Stores the fields that describe Skills that are configured through Admin/Setup > Site Configuration > Resources > Skills and can be associated with resources. wh_skill_category wh_skill_resource wh_subissue_type wh_subscription wh_subscription_period wh_subscription_ period_type wh_survey: wh_survey_question wh_survey_question_ response_type Enumerates the Subscription Period Types available to assign to subscriptions associated with an installed product. wh_survey_result_notification wh_ survey_result_question Stores the fields that describe the Categories configured through Admin/Setup > Site Configuration > Resources > Skills Categories and used to group Skills. Note the all skills must be associated with a Skill Category. Maps Skills to Resources associated with the skills. Stores Subissue Types added to Issues configured through Admin/Setup > Service Desk > Issue and Subissue Types and available to assign to service desk tickets. Stores the fields that describe Subscriptions as configured through the Subscriptions tab in the Add or Edit Installed Product window, displayed in the Search grid under CRM > Installed Products > Subscriptions, and passed through to billing. Stores the fields that describe Subscription Periods for subscriptions associated with installed products. Stores all basic information for each survey created and provides the survey information that is used to join to all of the other survey views. Stores all survey questions included in each survey in wh_survey. Enumerates the survey question response types available for use with questions stored wh_survey_question Stores information that determines when notifications should be sent out with respect to survey responses, and to whom. Stores all answers for questions stored in wh_survey_question Page 10 of 44

19 Report Data Warehouse View Descriptions View Name wh_survey_result_total wh_survey_sent wh_task Description Stores the aggregate survey results broken up by questions relating to resources, contacts, and accounts. Joins to the wh_survey_sent view on survey_sent_id. Stores a record of all instances of surveys sent, including the details of each survey and when it was sent. Stores base fields that describe Project Tasks and Service Desk Tickets. User-defined Fields are in wh_task_udf (for tasks) or wh_ticket_udf (for service desk tickets). For non-pivoted view of Task UDF data, refer to wh_udf_value_task. Fields that describe project phases are stored in "wh_project_phase" on page 8. wh_task_dependency wh_task_account_contact wh_task_billing_milestone wh_task_library_category wh_task_library_item wh_task_resource wh_task_status wh_task_tracking wh_task_type wh_task_udf wh_tax_category wh_tax_group wh_tax_item wh_tax_region wh_tax_region_category wh_tax_region_category_tax Maps Client Tasks generated with the optional Client Access add-on to Account Contacts. Maps project Tasks to associated billing milestones. Stores fields that define dependencies between predecessor and successor tasks as configured through the Add Task or Edit Task views in the Project module. Stores fields that define Task Library Categories as configured through Admin/Setup > Projects > Tasks > Task Library. Stores fields that describe items added to the Task Library and available through the new or edit Task views. Maps Tasks to secondary resources assigned to the task. Primary resources are stored in wh_task as assigned_ resource_id or assigned_account_contact_id. Enumerates the Statuses configured through Admin/Setup > Projects > Tasks > Task Statuses and available to assign to tasks. Stores the fields that track ticket and task activities, that is, ticket and task history. Enumerates the Task Types available to assign to tasks through the Add Task or Edit Task windows. Pivoted view. Stores User-defined Fields for project tasks. Base fields are in wh_task.for non-pivoted view of Task UDF data, refer to wh_udf_value_task. Stores the fields that describe a tax category in Autotask. Used with tax regions to determine total tax to charge a customer. This view has been removed. Tax charged to a customer is now based on the customer's Tax Region ("wh_tax_ region" on page 11) and the Tax Category assigned to the cost items ("wh_tax_category" on page 11). This view has been removed. Tax charged to a customer is now based on the Total Effective Tax Rate as determined by the Tax Category ("wh_tax_category" on page 11)and the Tax Region ("wh_tax_region" on page 11) and stored in "wh_tax_region_category" on page 11. Stores the fields that describe an area, usually geographic, that shares a common tax rate for specified cost items. Stores the fields that describe the intersection of a tax region with a tax category to determine the total effective tax rate. Stores the fields that describe the tax charged to an account, located in the specified tax region, for purchased items that are assigned the specified tax category. Indicates whether tax_region_category_tax is compounded. Page 11 of 44

20 Report Data Warehouse View Descriptions View Name wh_territory wh_territory_resource wh_ticket_source wh_ticket_udf Description Stores Sales Territories configured through Admin/Setup > CRM > Accounts > Territories and associated with Accounts. Maps Resources to associated Sales Territories. Stores fields that describe service desk Ticket Sources as configured through Admin/Setup > Service Desk > Tickets > Ticket Sources and assigned to service desk Tickets. Pivoted data. Stores User-defined Fields for service desk tickets. Base fields are in wh_task. For non-pivoted view of Ticket UDF data, refer to wh_udf_value_ticket. wh_tier_approval wh_time_item wh_time_item_type wh_time_off_request wh_time_report wh_time_status wh_time_subitem wh_time_zone wh_travel_restriction wh_udf_category wh_udf_field_definition Enumerates the UDF categories, for example, Accounts, Tasks, Tickets, etc. Every UDF is associated with one category. wh_udf_list_definition wh_udf_value_installed_ product wh_udf_value_ opportunity Stores the fields that describe the approver and approval tier for a time off request or timesheet. Stores the fields that describe timesheets time record rows. Individual hours are in wh_time_subitem. Enumerates Types of Time Items, specifically Straight Hours or Start/Stop Time. Stores the fields that contain data for Time Off Requests. Stores the fields that contain timesheet data. Individual time record rows are in wh_time_item. Individual hours are in wh_time_subitem. Enumerates Time Entry Statuses available for association with time entries when entering time from a task or ticket or in a weekly time sheet. Stores the fields that contain the data for timesheet hours. Timesheet record rows are in wh_time_item. Stores fields that describe Time Zone information. Enumerates the categories for specifying restrictions on a resource's travel availability, as assigned through Admin/Setup > Site Configuration > Resources > Resources > HR tab. Stores the fields that describe the User-defined Fields. Stores the fields that describe the list options available for UDFs that are list type. Non-pivoted view. Stores User-defined Fields for Configuration Items (Installed Products). Base fields for Configuration Items are stored in wh_installed_product. This view maps to the UDF table without pivoting data. For pivoted Product UDF data, refer to wh_installed_product_udf. Non-pivoted view. Stores User-defined Fields for Opportunities. Base fields for Opportunities are stored in wh_ opportunity. This view maps to the UDF table without pivoting data. For pivoted Product UDF data, refer to wh_opportunity_udf. Page 12 of 44

21 Report Data Warehouse View Descriptions View Name wh_udf_value_product Description Non-pivoted view. Stores product User-defined Fields for Products. Base fields are in wh_product. This view maps the UDF table without pivoting data. For pivoted Product UDF data, refer to wh_product_udf. wh_udf_value_project Stores User-defined Dields for projects. Base fields are in wh_project. This view maps to the UDF table without pivoting data. For pivoted Product UDF data, refer to wh_project_udf. Stores User-defined Dields for site configuration information for Configuration Items (Installed Products). Base fields are in wh_installed_product. This view maps to the UDF table without pivoting data. For pivoted Product UDF data, refer to wh_site_configuration_udf. wh_udf_value_task Stores User-defined Fields for project tasks. Base fields are in wh_task. This view maps to the UDF table without pivoting data. For pivoted Product UDF data, refer to wh_task_udf. wh_udf_value_ticket Stores User-defined Dields for service desk tickets. Base fields are in wh_task. This view maps to the UDF table without pivoting data. For pivoted Product UDF data, refer to wh_ticket_udf. wh_workflow_rule wh_workflow_rule_ action wh_udf_value_site_configuration wh_workflow_notification_recipient wh_workflow_rule_condition Describes workflow rule notification recipients that are not role based (implicit). Stores the fields that describe workflow rules created under Site Setup in the Admin module, including name, description, entity type, event details, and role based (implicit) notification recipients. Defines the actions available to apply to workflow rules. Defines the condition available to apply to workflow rules. wh_workgroup Stores fields that describe workgroups as configured through Admin/Setup > Site Configuration > Resources > Workgroups and displayed through the Dispatcher's Workshop. wh_workgroup_ resource Maps Workgroups to the Resources associated with the Workgroup. Page 13 of 44

22 Report Data Warehouse Updates April 2008 Updates: The following views have been added to the list of views: wh_attachment_type wh_payroll_type wh_resource_type wh_travel_restriction wh_gender wh_tier_approval August 2008 Updates: The following views have been added to the list of views: wh_inventory_item wh_inventory_item_serial wh_inventory_location wh_inventory_order wh_inventory_order_product wh_inventory_order_status wh_inventory_receive wh_inventory_receive_serial wh_inventory_transfer_serial wh_inventory_transfer wh_inventory_transfer_type November 2008 Updates: wh_invoice: The following column has been added to this view create_time now appears after the existing creator_resource_id column. January 2009 Updates: The following views have been added to the list of views: wh_expense_payment_type wh_expense_item Page 14 of 44

23 wh_posted_overall wh_pending_overall wh_service_level_agreement wh_service_level_agreement_event_dates wh_service_level_agreement_objective wh_hours_of_operation wh_business_hours The following columns in existing views have been added or changed. NOT E : To fa cilit a t e da t a re t rie va l, se le ct e d R e port Da t a W a re house columns ha ve be e n re na me d t o cla rify t he ir cont e nt or t o show t he a ppropria t e re la t ionship be t we e n vie ws. W he n cre a t ing ne w re port s, use t he ne w column na me s. The old columns will re ma in in t he a ffe ct e d vie ws a long wit h t he ne w columns for a pe riod of t ime t o a llow you t o upda t e your e xist ing script s or ot he r re port ing t ools a s ne e de d. In t ime, t he old columns will be re move d. Aut ot a sk will provide a dva nce not ice be fore re moving a ny columns. Updated Views Old Column New Column Other Changes wh_billing_item, wh_pending_overall wh_posted_overall work_ entry_id time_subitem_id Page 15 of 44

24 Updated Views Old Column New Column Other Changes wh_inventory_order order_cancel_date inventory_order_ addressee inventory_order_ addressee_line_1 inventory_order_ addressee_line_2 inventory_order_ address_city inventory_order_general_memo vendor_invoice_number external_purchase_ order_number account_id shipping_type_id expected_ship_date freight_cost tax_group_id payment_term_id inventory_order_ address_zip_code phone_number fax_number wh_inventory_order_product quantity_ordered was_auto_filled memo product_unit_cost has_been_exported exported_time wh_inventory_receive has_been_exported exported_time receive_by_resource_id wh_invoice invoice_id Datatype changed from decimal to integer wh_resource payroll-identifier Page 16 of 44

25 March 2009 Updates: The following view has been added to the list of views: wh_site_configuration_udf wh_installed_product: The following columns (fields) have been added to this view installed_product_type location contact_first_name contact_last_name vendor_name Impact of Autotask UDF Restructuring on Report Data Warehouse In order to improve the speed of database queries that involve UDFs Autotask has restructured how the database handles UDFs. With the new data model, a UDF record will not be created until a value is provided for that UDF. This change affects only UDF records where the parent entity, for example, a ticket, has been saved but no value has been provided for the UDF. For Report Data Warehouse users, this restructuring will impact how the data is returned for queries that include these UDFs. For example, you might add a ticket UDF labeled Resolution to allow your users to enter information when a ticket resolved. No value will be added to the UDF until the ticket is resolved, and no record for the Resolution UDF for that ticket will be added to the database until that value is added. When you run a Report Data Warehouse query that returns data for an entity with a UDF where a value has not yet been provided, there will be no UDF record to return. Depending on how the query was built, the report will either show a NULL in the place of these values, or show no row at all. April 2009 Updates: wh_installed_product: The following columns (fields) have been added to this view contract_id service_id service_bundle_id July 1, 2009 Updates wh_installed_product: The following column has been added to this view. It contains the ID of the resource who created the installed product. installed_by_resource_id wh_time_report: the billed_hours column was removed. Correction: Noted 9/23/ the column removed was hours_billed. Page 17 of 44

26 wh_billing_item_type: a new type, Milestone Item, was added. The type id is -1. This type is for all work related to the milestone. wh_project: The following six calculated columns were added to this view billed_labor_revenue billed_expense_revenue billed_project_cost_revenue billed_milestone_revenue project_costs project_expenses July 21, 2009 Updates wh_invoice: The following three columns were added to this view is_voided voided_time voided_by_resource_id August 11, 2009 Updates wh_crm_todo: Corrected issue with data return for crm_todo_name and crm_todo_description columns. Querying these columns now returns expected data. September 10, 2009 Updates wh_time_item: The following three columns were added to this view created_by_user_id last_modified_time last_modified_by_user_id wh_project: The following two columns were added to this view department_id line_of_business_id September 23, 2009 Updates The following view has been added to the list of views: wh_line_of_business Correction: Page 18 of 44

27 The column name indicated in "wh_time_report: the billed_hours column was removed", listed under July 1, 2009, was listed incorrectly. The name of the removed column was hours_billed November 23, 2009 Updates The following varchar or nvarchar columns were made bigger to reflect changes to the Autotask interface. These changes should not require any changes for Data Warehouse users: View Column Previous New wh_service_bundle service_bundle_description nvarchar(200) nvarchar(400) wh_service_bundle service_description varchar(200) varchar(400) wh_invoice po_number varchar(20) varchar(32) wh_project project_description nvarchar(2000) nvarchar(max) wh_billing_milestone billing_milestone_name nvarchar(50) nvarchar(100) January 19, 2010 Updates wh_billing_item: The following column was added to this view tax_dollars February 16, 2010 Updates wh_invoice: The following columns were added to this view is_paid is_ ed paid_date ed_by_resource_id ed_time wh_task: The following column was added to this view resolution March 9, 2010 Updates This updated was corrected. Refer to the May 21, 2010 entry for details. wh_subscription: The following column was added to this view is_cancelled March 31, 2010 Updates This update was corrected, refer to the May 21, 2010 entry for details. Page 19 of 44

28 wh_task: Added the following column start_time (exposes start date/time) April 9, 2010 Updates The following five views related to Workflow Rules have been added: wh_workflow_rule wh_workflow_rule_action wh_workflow_rule_condition wh_workflow_notification_recipient wh_reference_attribute Descriptions added to View Description document. April 27, 2010 Updates wh_opporutnity: The following columns were added to this view: one_time_revenue monthly_revenue quarterly_revenue semi_annual_revenue yearly_revenue one_time_cost monthly_cost quarterly_cost semi_annual_cost yearly_cost number_months_for_estimating_total_profit (this column stores the # entered in the "Calculate Totals based on # months" field on the New_Edit Opportunity screen) wh_time_subitem: This item for the April 27, 2010 update has been corrected. Refer tothe May 21, 2010 entry for details The following columns were added to this view: contract_id billable show_on_invoice allocation_code_id Page 20 of 44

29 April 28, 2010 Updates wh_resource: The following column was added to this view: accounting_reference_id May 21, 2010 Updates There were no updates to the Data Warehouse. Several inaccuracies were found in earlier update notations. NOTE CORRECTIONS: The generation of the current Data Warehouse ERD (entity relationship diagram) has prompted the following corrections to update entries: March 9, 2010 Update wh_subscription: The column is_cancelled was added The column is_active was not removed. The column subscription-status was not added. wh_subscription_status: this view was not added March 31, 2010 Update wh_task: Added start_time (exposes start date/time) Did not add the column start_date April 27, 2010 Update wh_time_item: There were no changes to this view wh_time_subitem: The following columns were added to this view: contract_id billable show_on_invoice allocation_code_id September 7, 2010 Updates wh_account: The following columns were added to this view: survey_account_rating number_of_surveys wh_account_contact: The following columns were added to this view: survey_contact_rating Page 21 of 44

30 number_of_surveys wh_resource: The following columns were added to this view: survey_resource_rating number_of_surveys wh_contract: The following columns were added to this view: bill_to_account_id bill_to_account_contact_id exclusion_contract_id wh_subissue_type: The following column was added to this view: is_active NOTE: For reporting purposes, Billing Items, Time Entries, and Invoice Items under a contract that specifies a Bill To Account will follow the behavior seen in the Autotask interface; that is, Billing Items and Time Entries will show under the End Client Account and Invoice Items will show under the Bill To Account. September 29, 2010 Updates Two new views added to accommodate new block, retainer, and Per Ticket contract repurchase rules. wh_contract_repurchase_notification_rule: Refer to column details below wh_contract_repurchase_notification_rule_recipient: Refer to column details below NOTE: When creating new reports, use the new views. The old views will remain available for a period of time to allow you to update your existing scripts or other reporting tools as needed. At some point they will be removed. Autotask will provide advance notice before removing any views. The two new views described below will replace two existing views: "wh_contract_block_repurchase_rule" and "wh_contract_block_notification_rule". New view details: wh_contract_repurchase_notification_rule - This new view stores the fields that describe all Repurchase/Notification rules created for Block, Retainer, and Per Ticket contracts. It contains the following columns: contract_repurchase_notification_rule_id contract_id contract_repurchase_notification_rule_name threshold number_of_units rate additional_ _addresses Page 22 of 44

31 wh_contract_repurchase_notification_rule_recipient - This new view stores the contacts and resources specified to receive notification when a contract repurchase/notification rule is triggered. It contains the following columns: contract_repurchase_notification_rule_recipient_id contract_repurchase_notification_rule_id resource_id account_contact_id October 20, 2010 Updates The following columns were added to support tickets and contracts on To-dos and Opportunities on Tasks. wh_crm_todo: The following columns were added to this view: ticket_id contract_id wh_task: The following column was added to this view: opportunity_id October 28, 2010 Updates Additional changes included in general release. wh_time_subitem: The following column was added to this view: rounded_hours_worked wh_task _status: The following column was added to this view: service_level_agreement_event_type_code The following view was added: wh_service_level_agreement_event_typeit includes the following columns: service_level_agreement_event_type_code service_level_agreement_event_type_name November 11, 2010 Updates The column "adjusted_price" was removed from two views. wh_contract_service_bundle_period wh_contract_service_period December 1, 2010 Updates The column "account_owner_resource_id " was removed from the following view: Page 23 of 44

32 wh_project January 20, 2011 Updates The latest updates will provide additional options for accessing User-defined Field information in your database. We have added twelve new UDF related views and added one UDF related column to the wh_installed_ product view. wh_installed_product: the following column was added to this view udf_group_id The following new views were added: wh_udf_category - Enumerates the UDF categories, for example, Accounts, Tasks, Tickets, etc. Every UDF is associated with one category. It contains the following columns: udf_category_id category_name wh_installed_product_udf_group - Enumerates Installed Product UDF Groups. Groups are unique to Installed Product UDFs. It contains the following columns: udf_installed_product_group_id udf_group_name wh_installed_product_udf_group_detail - Stores the fields that describe Installed Product UDF Groups. It contains the following columns: installed_product_udf_group_detail_id udf_installed_product_group_id udf_field_id is_required sort_order wh_udf_field_definition - Stores the fields that describe User-defined Fields. It contains the following columns: udf_field_id udf_name udf_description udf_category_id udf_data_type udf_default_value is_field_mapping is_protected Page 24 of 44

33 is_required is_active wh_udf_list_definition - Stores the fields that describe the list options available for UDFs that are list type. It contains the following columns: udf_list_value_id udf_field_id udf_value_for_export udf_value_for_display The following seven new views are alternatives to existing views that describe UDFs for the following Autotask entities: Installed Products (Configuration Items), Opportunities, Products, Projects, Site Configuration, Tasks, and Tickets. The existing views pivot the data; the new views map to the UDF table without pivoting. These new views are in addition to the existing views. NOTE: The pivoted views are dynamically generated, changing as UDFs are added and removed. The new views are not dynamic and require a join to the wh_udf_field_definition view. You can now choose the best option for your needs. wh_udf_value_installed_product - Non-pivoted view. Stores User-defined Fields for Configuration Items (Installed Products). Base fields for Configuration Items are stored in wh_installed_product. It contains the following columns: udf_value_id udf_field_id installed_product_id udf_list_value_id date_time_value decimal_value string_value bool_value For pivoted Installed Product UDF data, refer to wh_installed_product_udf wh_udf_value_opportunity - Non-pivoted view. Stores User-defined Fields for Opportunities. Base fields for Opportunities are stored in wh_opportunity. It contains the following columns: udf_value_id udf_field_id opportunity_id udf_list_value_id date_time_value Page 25 of 44

34 decimal_value string_value bool_value For pivoted Opportunity UDF data, refer to wh_opportunty_udf wh_udf_value_product - Non-pivoted view. Stores User-defined Fields for Products. Base fields are in wh_ product. It contains the following columns: udf_value_id udf_field_id product_id udf_list_value_id date_time_value decimal_value string_value bool_value For pivoted Product UDF data, refer to wh_product_udf wh_udf_value_project - Non-pivoted view. Stores User-defined Fields for projects. Base fields are in wh_ project. It contains the following columns: udf_value_id udf_field_id project_id udf_list_value_id decimal_value string_value bool_value For pivoted Project UDF data, refer to wh_project_udf wh_udf_value_site_configuration - Non-pivoted view. Stores User-defined Fields for site configuration information for Configuration Items (Installed Products). Base fields are in wh_installed_product. It contains the following columns: udf_value_id udf_field_id site_configuration_id udf_list_value_id date_time_value Page 26 of 44

35 decimal_value string_value bool_value For pivoted Site Configuration UDF data, refer to wh_ site_configuration_udf wh_udf_value_task - Non-pivoted view. Stores User-defined Fields for project tasks. Base fields are in wh_task. It contains the following columns: udf_value_id udf_field_id task_id udf_list_value_id date_time_value decimal_value string_value bool_value For pivoted Task UDF data, refer to wh_ task_udf wh_udf_value_ticket - Non-pivoted view. Stores User-defined Fields for tickets. Base fields are in wh_ task. It contains the following columns: udf_value_id udf_field_id ticket_id udf_list_value_id date_time_value decimal_value string_value bool_value For pivoted Ticket UDF data, refer to wh_ ticket_udf February 10, 2011 Updates wh_expense_item: the following columns were added to this view task_id allocation_code_id Page 27 of 44

36 April 13, 2011 Updates wh_posted_overall: a bug fix resulted in the following billing_type changes The value of billing_type for Contract Costs changed from 16 to 14 a bug fix resulted in the following billing_ type changes The value of billing_type for Per Ticket Purchases changed from 14 to 15 wh_installed_product: the following column was added to this view contact_id As part of the ongoing effort to meet our customers growing needs, we have changed the data type for a number of columns in our database base tables to decimal type. As a report data warehouse user, this should impact your reports only if you are running reports where the Report Data Warehouse column data type is specified. This document will provide a list of affected columns when available. April 26, 2011 Updates The following views/columns were affected by datatype changes in the Autotask base tables. All columns listed are now decimal type. wh_allocation_code.unit_price wh_allowed_time_off.floating_holiday_hours_allowed wh_allowed_time_off.sick_hours_allowed wh_billing_item.dollars wh_billing_milestone.dollars wh_contract.overage_billing wh_expense_item.exchange_rate wh_invoice.total_dollars wh_posted_overall.posted_time wh_project.original_estimated_revenue wh_project.actual_change_order_cost wh_project.payments_to_date wh_project_cost.unit_cost wh_recurring_ticket.ticket_estimated_hours wh_sales_quota.advanced_field_2 wh_sales_quota.advanced_field_4 wh_sales_quota.amount wh_task.change_order_hours wh_allocation_code.unit_cost wh_allowed_time_off.personal_hours_allowed wh_allowed_time_off.vactation_hours_allowed wh_billing_item.hours wh_contract.estimated_hours wh_contract_rate.rate_offset wh_expense_report.expense_amount wh_opportunity.total_revenue wh_posted_overall.total_amount wh_project.original_estimated_sales_cost wh_project.actual_change_order_revenue wh_project_cost.our_cost wh_project_cost.unit_price wh_sales_quota.advanced_field_1 wh_sales_quota.advanced_field_3 wh_sales_quota.advanced_field_5 wh_task.change_order_dollars wh_task.estimated_cost Page 28 of 44

37 wh_task.estimated_hours wh_task.total_billed_hours wh_task_library_item.estimated_hours wh_time_report.hours_worked wh_task.total_billed_dollars wh_task.total_worked_hours wh_time_off_request.requested_hours wh_time_subitem_id.hours_billed May 25, 2011 Updates The following changes were made to columns impacting Service Level Agreement reporting: wh_service_level_agreement_event_dates: the following column was added total_waiting_customer_hours In addition, changes were made to the base tables to deduct Hours Waiting for Customer time from SLA elapsed time. This change will impact the following columns in wh_service_level_agreement_event_dates: first_response_elapsed_hours resolution_plan_elasped_hours resolution_elapsed_hours August 15, 2011 Updates wh_service_level_agreement_objective The following columns were added: first_response_target_hours resolution_plan_target_hours resolution_target_hours first_response_target_type_id resolution_plan_target_type_id resolution_target_type_id The following columns were removed: first_response_within_hours resolution_plan_within_hours resolution_within_hours wh_expense_report The following column was added: quickbooks_reference_number wh_expense_payment_type The following column was removed: Page 29 of 44

38 sort_order column October 11, 2011 Updates A new column, purchase_order_number, was added to the following views: wh_contract wh_contract_service_bundle_period wh_contract_service_period wh_contract_service_bundle_adjustment wh_project wh_project_cost wh_task wh_recurring_ticket wh_expense_item wh_billing_item wh_billing_milestone wh_subscription wh_subscription_period In addition, for wh_project_cost The existing column, purchase_order_number, has been relabeled. It is now internal_po_number. This change was made to be consistent with the UI and to avoid confusion with the newly added purchase_order_number. November 1, 2011 Updates To provide accurate reporting on ticket history after the new Workflow Engine redesign, we removed wh_ task_event_log and added wh_task_tracking. We also added several new tables to allow you to access survey data from the Report Data Warehouse. View removed: wh_task_event_log Replaced with: wh_task-tracking The new view includes the following columns: first_response_target_hours task_tracking_id task_id action_performed_by_person_id action_time old_title Page 30 of 44

39 new_title old_description new_description old_status_id new_status_id old_priority_id new_priority_id old_source_id new_source_id old_estimated_task_time new_estimated_task_time old_primary_resource_id new_primary_resource_id old_due_time new_due_time old_allocation_code_id new_allocation_code_id old_queue_id new_queue_id old_departmnt_id new_department_id old_contract_id new_contract_id old_role_id new_role_id old_issue_type_id new_issue_type_id old_sub_issue_type_id new_sub_issue_type_id old_installed_product_id new_installed_product_id old_priority Page 31 of 44

40 new_priority old_external_billing_id new_external_billing_id old_contact_id new_contact_id old_service_level_agreement_id new_service_level_agreement_id old_opportunity_id new_opportunity_id old_resolution_target_time new_resolution_target_time old_first_response_actual_time new_first_response_actual_time old_first_response_target_time new_first_response_target_time old_sla_start_time new_sla_start_time old_resolution_plan_target_time new_resolution_plan_target_time old_resolution_actual_time new_resolution_actual_time old_resolution_plan_actual_time new_resolution_plan_actual_time old_resolution new_resolution has_sla_change_been_noted old_has_met_service_level_agreement new_has_met_service_level_agreement old_account_id new_account_id Page 32 of 44

41 Survey Views added: To allow report data warehouse users to access survey data, the following views were added wh_survey: Stores all basic information for each survey created and provides the survey information that is used to join to all of the other survey views. survey_id template_master_id created_by_resource_id last_modified_by_resource_id name display_name description no_response_resend_survey_days header_text footer_text confirmation_text created_time last_modified_time send_result_to_account_owner_always send_result_to_account_owner_only_if_below_threshold threshold_value other_ _address_below_threshold other_ _address_survey_result is_active wh_survey_question: Stores all survey questions that go with each survey in wh_survey. survey_question_id survey_id survey_question_response_type_id survey_benchmark_question_id question_text impacts_account_rating impacts_contact_rating impacts_resource_rating Page 33 of 44

42 is_multiple_line multiple_choice_option1_text multiple_choice_option2_text multiple_choice_option3_text multiple_choice_option4_text multiple_choice_option5_text multiple_choice_option6_text multiple_choice_option7_text multiple_choice_option8_text multiple_choice_option9_text multiple_choice_option10_text is_required is_active sort_order wh_survey_question_response_type: Stores the question response types available for use with questions in wh_survey_question. Defaults are Multiple-choice, Rating 1-5, and Text. survey_question_response_type_id name description wh_survey_result_question: Stores all answers for each question in wh_survey_question. survey_result_question_id survey_question_id survey_sent_id answer_text impacts_account_rating impacts_contact_rating impacts_resource_rating survey_id wh_survey_result_total: Stores the aggregate survey results broken up by questions relating to resources, contacts, and accounts. Joins to the wh_survey_sent view on survey_sent_id. survey_result_total_id survey_sent_id Page 34 of 44

43 score number_of_resource_rating_questions resource_score number_of_contact_rating_questions contact_score number_of_account_rating_questions account_score wh_survey_sent: Stores all instances of surveys that were sent out including details of each survey and when it was sent. survey_sent_id survey_id task_id account_id contact_id primary_resource_id sent_time resent_time result_received_time wh_survey_result_notification: Stores information about when notifications should be sent out with respect to survey responses. survey_result_notification_id survey_id resource_id workgroup_id send_only_if_below_threshold_result February 28, 2012 wh_expense_report: the following column was added approved_time wh_time_report: the following column was added last_submitted_time wh_time_report: the following column was added last_submitted_by_resource_id Page 35 of 44

44 wh_contract: the following column was added opportunity_id March 6, 2012 The column Country was changed from VARCHAR(25) to VARCHAR(100). This column appears in the following views: wh_account wh_account_contact wh_location June 6, 2012 In the following two views: wh_account wh_account_contact The State column was changed to 40 characters wh_installed_product: the following new column was added parent_installed_product_id May 15, 2012 Three columns were changed in wh_contract. These columns now return null when the base table column data is null. Originally, they returned 0 when the base table data was null: exclusion_contract_id bill_to_account_id bill_to_account_contact_id June 6, 2012 In the following two views: wh_account wh_account_contact The State column was changed to 40 characters wh_installed_product: the following new column was added parent_installed_product_id Page 36 of 44

45 July 24, 2012 wh_login_log_autotaskthe following column was added login_request_type This column allows users to track login types and filter out MS Exchange logins. October 2, 2012 The following view has been added: wh_sales_order id account_id sales_order_title sales_order_status owner_resource_id date promised_due_date bill_to_address_1 bill_to_address_2 bill_to_city bill_to_state bill_to_postal_code bill_to_country ship_to_address_1 ship_to_address_2 ship_to_city ship_to_state ship_to_postal_code ship_to_country opportunity_id Sales Order UDFs Columns have been added to the following views: wh_opportunity sales_order_id close_date wh_crm_note sales_order_id wh_crm_todo sales_order_id wh_project_cost Page 37 of 44

46 status wh_product May 2013 does_not_require_procurement The following views have been added: wh_address_format address_format_id name address_format_string is_active is_default wh_country country_id country_code country_name_iso_standard country_name_display is_active is_undefined_country address_format_id wh_name_salutation name_salutation_id salutation is_active wh_name_suffix name_suffix_id suffix is_active wh_tax_category tax_category_id tax_category_name tax_category_description is_active wh_tax_region tax_region_id tax_region_name is_active is_default wh_tax_region_category Page 38 of 44

47 tax_region_category_id tax_region_id tax_category_id total_effective_tax_rate wh_tax_region_category_tax tax_region_category_tax_id tax_region_category_id tax_name tax_rate is_compounded The following views were removed: wh_salutation salutation_id salutation_name wh_tax_group tax_group_id tax_group_name tax_group_description wh_tax_item tax_item_id tax_item_name tax_group_id tax_rate is_tax_compounded For information on the new system to determine tax rates in Autotask, refer to Configuring Your Tax Table in the Autotask online help. Changes were made to the following views as indicated: wh_account Column added: additional_address_information country_id wh_account_contact Columns added: additional_address_information country_id is_primary_account_contact Columns changed: Page 39 of 44

48 narrative_full_name (max characters now 250) sorting_full_name (max characters now 250) wh_allocation_code Columns added: tax_category_id tax_category_name Column removed: is_taxable wh_allowed_time _off Columns added: vacation_annual_hours personal_annual_hours sick_annual_hours floating_holiday_annual_hours Columns changed: vacation_hours_allowed (numeric precision now 38, numeric scale 3) personal_hours_allowed (numeric precision now 38, numeric scale 3) sick_hours_allowed (numeric precision now 38, numeric scale 3) floating_holiday_hours_allowed (numeric precision now 38, numeric scale 3) wh_billing_milestone Column removed: external_accounting_id wh_contract Column changed: contact_name (max characters now 150) wh_expense_item Column removed: external_expense_item_id wh_installed_product Columns changed: contact_narrative_full_name (max characters now 250) contact_sorting_full_name (max characters now 250) wh_inventory_order Column added: Page 40 of 44

49 tax_region_id Column removed: tax_group_id wh_inventory_receive_serial Column changed: wh_invoice serial_number (max characters now 100) Column added: tax_region_name Column removed: tax_group_id wh_location Column added: additional_address_information country_id wh_product Columns removed: allocation_code_id is_taxable wh_project_cost Column removed: wh_quote external_accounting_id Column added: tax_region_id Column removed: tax_group_id wh_quote_item Column added: tax_category_id Column removed: is_taxable Page 41 of 44

50 wh_resource Columns added name_salutation_id salutation name_suffix_id Column removed salutation_id Columns changed full_name (max characters now 250) narrative_full_name (max characters now 250) suffix (max characters now 50) wh_subscription Column added: subscription_cost wh_sales_order wh_task bill_to_country_id additional_bill_to_address_information ship_to_country_id additional_ship_to_address_information Columns added: problem_ticket_id ticket_type_id Columns removed: reported_by_name reported_by_ estimated_cost external_accounting_id wh_task_tracking Columns removed: old_external_billing_id new_external_billing_id wh_time_item Column removed: unique_id Page 42 of 44

51 wh_time_subitem Column removed: unique_id Page 43 of 44

52 Index: Data Warehouse, Report Reports Index Data Warehouse, Report 3 Reports Data Warehouse 3 Page 44 of 44