Skip to main content
Adaptive Insights
Knowledge and Support - Adaptive Insights

Manage Transaction Tables

Only available with Adaptive Insights for Sales

Your customer relationship management system (CRM) can generate a variety of transaction data about your sales operations, including sales pipeline progress, opportunity count, customer count, or bookings. The Transaction Tables Overview page lets you edit and manage five different sales transaction tables to import that data for use in sales planning.

Before You Begin

  • This article is for administrators who build or manage the model in the Adaptive Insights. See Transactions for descrptions of the transaction fields.
  • To access the Transaction Tables Overview, you need the Access Transactions, Model Management Access, Model Management Access > Model, and Model Management Access > Transactions permissions.
  • The Transaction Tables Overview is available only for Adaptive Insights for Sales.

Where to Go

To get to the Transaction Tables Overview, click navicon.gif and Modeling. In the Others menu, choose Transactions.

From here, you can manage your Transaction Tables.

Transactions Tables

Transaction Tables Overview

With the Transaction Tables Overview page you can:

1 Edit or Rename a transaction table. The DEFAULT transaction table cannot be renamed.

2 Click a table's name to edit its transaction definition fields in the transaction builder.

Each transaction table you edit represents a transaction type you might need to import from a CRM like Salesforce or HubSpot. The tables you define become available in the Object Modeling settings so that you can tie sales operations data to territories and sales representatives as part of territory planning.

Transaction table names cannot contain special characters ~!@#$%^&()_. They prevent transaction data import.

Special Transaction Field Definitions for Sales Planning

Transaction tables in sales planning need field definitions for:

  • A dimension field for Geography used for territory assignments and generating territory boundaries if you plan on creating territory map charts.
  • A number field named after each cube account code this transaction data imports to. For example, a field called OC.OpportunityCount in an opportunities cube sheet would load sales opportunities and let you make that data visible for a territory in a territory map chart.

Sales Transaction Field Definitions Example: Sales Opportunities

The example below shows the transaction field definitions for a Sales Opportunities transaction table intended for importing data to an Opportunities cube sheet:

Sales Transaction Definition Example

1 A Geography field as a dimension, so that the transactions fields can contribute to the territories in a territory map chart.

2 A SalesRep field as text, so that the transactions get associated with a sales representative for territory assignments.

3 An OC.FARR number field for loading data to a cube account code OC.FARR in an Opportunities cube sheet.

4 An OC.OpportunityCount number field for loading data to a cube account code OC.OpportunityCount in an Opportunities cube sheet.

Below, the cube sheet builder shows how the transaction fields of OC.FARR and OC.OpportunityCount are named for cube account codes:

Opportunities Transactions Example - Cube Accounts

  • Was this article helpful?