Common Data Source Choices in ConnectWise Report Writer
Prefer the v_rpt views over raw tables wherever they exist — ConnectWise commits to keeping these views stable across releases, whereas table structures can change.
Companies
| Views | Tables |
|---|---|
v_rpt_Companyv_rpt_Contactsv_rpt_CompanyAddressv_rpt_Configsv_rpt_Configuration | Company — Primary table for company data. Company_RecID is the primary key; join it to service tickets, contacts, projects, invoices, and more.Company_Status — Status field on the Company screen. Join to Company using Company_Status_RecID.Company_Type — Type field on the Company screen. Join to Company using Company_Type_RecID.Contact — Primary table for contact data. Join to Company using Contact_RecID.Contact_Type — Type field on the Contact screen. Join to Contact using Contact_Type_RecID.Company_Address — Primary table for company addresses. Company_Address_RecID is the primary key; join it to opportunities, orders, and service tickets.Company_Team — Primary table for company team records. Join using Company_Address_RecID. |
Sales
| Views | Tables |
|---|---|
v_rpt_opportunityv_rpt_Activityv_rpt_Sales_Team | SO_Opportunity — Primary table for opportunities. Opportunity_RecID is the primary key; join it to activities, service tickets, and time entries.SO_Activity — Primary table for activities. SO_Activity_RecID is the primary key; join it to members, time entries, and reminders. |
Marketing
| Views | Tables |
|---|---|
v_rpt_MarketingCampaign | Marketing_Campaign — Primary table for marketing campaign data. Marketing_Campaign_RecID is the primary key; join it to activities and opportunities. |
Procurement
| Views | Tables |
|---|---|
v_rpt_Productv_rpt_ProductDetailv_rpt_SalesOrderv_rpt_PurchaseOrder | IV_Product — Primary table for product data. IV_Product_RecID is the primary key; join it to product records, GL entries, and shipment information. |
Project
| Views | Tables |
|---|---|
v_rpt_Project | PM_Project — Primary table for project data. PM_Project_RecID is the primary key; join it to time entries, phases, and opportunities.PM_Phase — Project phases. Join to PM_Project using PM_Project_RecID.PM_Contact — Project contacts. Join to PM_Project using PM_Project_RecID. |
Service Desk
| Views | Tables |
|---|---|
v_rpt_Servicev_rpt_Service_Summary | SR_Service — Primary table for ticket data. TicketNbr is the primary key; join it to opportunities, activities, configurations, and time entries. |
Time & Expense
| Views | Tables |
|---|---|
v_rpt_time | Time_Entry — Primary table for time records. Time_RecID is the primary key. |
Finance
| Views | Tables |
|---|---|
v_rpt_Invoicesv_rpt_Expensev_rpt_AgreementListv_rpt_AgreementAdditions | Billing_Log — Primary table for invoicing. Billing_Log_RecID is the primary key. |
System
| Views | Tables |
|---|---|
v_rpt_memberv_rpt_OwnerLevel | Member — Primary table for member (technician/user) data. Member_RecID is the primary key; join it to company teams, schedules, time entries, and commissions. |
Custom Fields
| Views | Tables |
|---|---|
v_tablename_Custom_Fields | Custom_Fields — Each record type (companies, tickets, opportunities) has its own custom field view named v_tablename_Custom_Fields. Replace tablename with the actual table name — for example, v_Company_Custom_Fields for company custom fields. Each view includes the RecID column for that record type (e.g. Company_RecID), which you can join to any table or view that shares that column. |