Supported Entities and Operations

Spectrum™ Technology Platform supports these entities and operations for each connection type:

Connection Type Table Properties
Marketo The entities are of the following types:
  1. Entity
  2. Entity Update
    Note: Entity Update is a virtual table used for Update on Lead entity. For example, Merge_Leads should be used for merging different Marketo Leads.
MS Dynamics CRM The entities are of the following types:
  1. User Owned
  2. Organization Owned
  3. Business Owned
  4. None
Netsuite The entities are of the types:
  • Standard Records
  • Custom Records
  • Joins
  • Saved Searches
On viewing the schema of the created Baseview, for each entity type, the resultant schema is displayed.
For example, for a Saved Search record, the schema of the search result is displayed. For a Join record, the schema of the join's result is displayed.
Note: In a NetSuite connection table, the primary key column is internalId.
SAP
  1. The entity columns are of two types:
    • Native: Columns with native datatypes are displayed with their respective datatypes.
    • Custom-defined: Columns with custom-defined datatypes are displayed with a blank datatype.
    To deploy a Virtual Data Source derived from an SAP connection, ensure its Metaviews and Baseviews include only such entities whose columns are of native datatypes. If the Baseviews and Metaviews have entities of custom-defined datatypes, the Virtual Data Source cannot be deployed.
Siebel The business components are displayed in the format Business Object.Business Component.
Splunk
Supported Operations
LIKE, ORDER BY, LIMIT, IN, BETWEEN, !=, <=, >=, <, >, multiple AND/OR operators
Supported Functions
String Functions
upper, lower, length, len, ltrim, rtrim, substring, max, min
Mathematical Functions
abs, ceil, exp, floor, sqrt, round
Note: For all other query operations, use the Splunk search column as explained below.
Spectrum™ Technology Platform provides a column search in the Splunk table using which you can look up the required data in the Splunk connection.
While executing a select query on the SplunkTable, use the search column in the where clause in any of the below scenarios:
  1. To include such search criteria which cannot be specified using ANSI SQL syntax.
  2. To include such Splunk-specific search criteria which cannot be included as part of the main SQL query.
For example, the below query looks for such a _raw value which contains the key opp with the value ACC.
select "_raw" from SplunkTable where "search"='search opp=ACC'
SuccessFactors The entities are of two types:
  1. Entity: Represents a table representing a business entity.
  2. Join: Represents a mapping between any two Entity type tables: a parent table and any of its child tables.
    Note: Links are not present between tables in the Baseview schema derived from a SuccessFactors connection. This is because foreign keys are not present in SuccessFactors tables, and joins between tables are indicated by Join type tables in the Spectrum™ Technology Platform.
The features of Join tables are:
  1. The name of a Join table indicates the two Entity tables which have been mapped together.
  2. Each record of a Join table contains the primary key from the parent entity and the columns of the respective child entity. Thus the particular parent entity's primary key is mapped to the child entity's details.

    For example, User#HR is a Join table in which User is the parent entity and Hr is the child entity. This join represents all the users and their respective HR representatives. The join table User#HR, therefore, has the parent table User's primary key UserId, which is mapped to the columns of the child table HR, like hr_userId, hr_username, hr_email, and so on.

  3. In case of Join tables, the insert and update functions work like the upsert function. This is because Join tables are not actual entities in SuccessFactors, but are mappings between entities and their navigation properties or child tables.

    To insert/update any Join table, the parent entity is updated, while in child table a new record is inserted or the existing record is updated corresponding to the parent record.

    Note: While updating, the mapping between a parent and a child is modified. It is also possible to modify the individual attributes of the child as required.
SugarCRM Supported operations:

LIKE (its operation is limited to picking up options starting with the specified value, such as in the statement WHERE name LIKE 's%', which picks up all the names starting with the alphabet S.), IS NULL, IS NOT NULL, IN, NOT IN, >,>=,<,<=, =, <>, AND, OR
Oracle Eloqua Supported Operations

Three entity types are supported:

  1. Entity: Denotes a table representing business entity.
  2. Activity: Denotes a table representing a business entity where data is generated based on some activity.
  3. Custom Entity: Denotes entities that are used as part of special operations provided with the Connector.