Client Mapping for Custom Datasets

Overview

This article describes how to configure client mappings for custom datasets. Client mappings ensure that data is pulled correctly from a datasource into the dataset. If you create custom datasets for client-facing reports, you must map the appropriate field to use for filtering. The field must be of the same field type (e.g., number, text) across the datasource.

Important: Datasets with different field types (e.g. numbers in one dataset and text in another) break the client mapping and may lead to data leakage in client reports.

Note: Only Admin users may view and edit datasets and client mappings.

 

Client Field by Datasource

The following table lists the mapping field for select datasources and the table BrightGauge™ pulls the data from.

Integration (Datasource) Field Table
ConnectWise Automate Name clients
ConnectWise Manage company_name company
Kaseya orgname kasadmin.org
N-Able CustomerName dim_customer
QuickBooks name customer
TigerPaw AccountName tvw_SOListView

 

Create a Custom Dataset

To create a custom dataset:

  1. Navigate to DATADatasets.
  2. Click Create Dataset.
  3. Select a Datasource
  4. Enter a Name for the dataset.
  5. Select the Dashboard Sync Frequency.

    Note: If this field is left blank, the dataset syncs at midnight and an hour before scheduled reports are scheduled to be sent.

  6. Enter a Description, if desired.
  7. Enter your SQL query.
  8. Click Test Query. Resolve any errors.
  9. Click Save. A modal appears asking to select a client mapping.
  10. Select the client mapping, then click Save

Select a Client Mapping for an Existing Dataset

To select client mapping for an existing dataset:

  1. Navigate to DATA > Datasets.
  2. Select the dataset.
  3. Select the mapping from the Client Column menu.
  4. Click Test Query. Resolve any errors.
  5. Click Save.

If you have any questions, please contact Support by selecting Help Open a Ticket from the top menu bar.

 

Was this article helpful?
2 out of 8 found this helpful

Comments

0 comments