Oracle Service Cloud Connection Details¶

Introduction¶

Connector Version

This documentation is based on version 23.0.8895 of the connector.

Get Started¶

Oracle Service Cloud Version Support

The connector leverages the Oracle Service Cloud API to enable bidirectional access to Oracle Service Cloud.

Establish a Connection¶

Connect to OracleServiceCloud¶

You must set the following to authenticate to Oracle Service Cloud:

• URL: The Url of the account to connect to.
• User: The username of the authenticating account.
• Password: The password of the authenticating account.

Important Notes¶

Configuration Files and Their Paths¶

• All references to adding configuration files and their paths refer to files and locations on the Harmony Agent where the connector is installed. These paths are to be adjusted as appropriate depending on the agent and the operating system. If multiple agents are used in an agent group, identical files will be required on each agent.

Data Model¶

Overview

This section shows the available API objects and provides more information on executing SQL to Oracle Service Cloud APIs.

Key Features

• The connector models Oracle Service Cloud entities like documents, folders, and groups as relational views, allowing you to write SQL to query Oracle Service Cloud data.
• Stored procedures allow you to execute operations to Oracle Service Cloud
• Live connectivity to these objects means any changes to your Oracle Service Cloud account are immediately reflected when using the connector.

Views

Views describes the available views.

Tables

Tables describes the available tables.

Stored Procedures

Stored Procedures are function-like interfaces to Oracle Service Cloud. Stored procedures allow you to execute operations to Oracle Service Cloud, including downloading documents and moving envelopes.

Tables¶

The connector models the data in Oracle Service Cloud as a list of tables in a relational database that can be queried using standard SQL statements.

Oracle Service Cloud Connector Tables¶

AccountGroups¶

The language-specific strings used for localization of fields.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM AccountGroups id = 12
SELECT * FROM AccountGroups id > 15
SELECT * FROM AccountGroups lookUpName LIKE '%test'
SELECT * FROM AccountGroups id IN (12, 23, 123)
SELECT * FROM AccountGroups lookUpName IS NOT NULL

INSERT¶

Insert can be executed by specifying the acceptCount,respondCount and names column. The columns that are not read-only can be inserted optionally. Following is an example of how to insert into this table.

INSERT INTO AccountGroupsNames#TEMP (languageId, labeltext) VALUES ('1', 'Smartly Maestro')
INSERT INTO AccountGroups(LookupName, Name, names) VALUES ('test', 'test', AccountGroupsNames#TEMP)

UPDATE¶

Update can be executed. The columns that are not read-only can be Updated. For example:

UPDATE AccountGroups SET Name = 'SV100D' WHERE ID = 12

DELETE¶

Following is an example of how to Delete a record in this table. For example:

DELETE FROM AccountGroups WHERE ID = 12

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Accounts¶

The account represents a staff member in Oracle B2C Service.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM Accounts WHERE id = 12
SELECT * FROM Accounts WHERE id > 15
SELECT * FROM Accounts WHERE lookUpName LIKE '%test'
SELECT * FROM Accounts WHERE id IN (12, 23, 123)
SELECT * FROM Accounts WHERE lookUpName IS NOT NULL

INSERT¶

Insert can be executed by specifying the login, namefirst, namelast, profileId, staffGroupId and newpassword columns. The columns that are not read-only can be inserted optionally. Following is an example of how to insert into this table.

INSERT INTO Accounts (login, namefirst, namelast, profileId, staffGroupId, newpassword) VALUES ('testadministrator', 'abc', 'xyz', '14', '102243', 'testpw')

UPDATE¶

Update can be executed by specifying the ID in WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE Accounts SET namelast = 'abcd' WHERE ID = 1

DELETE¶

Delete can be executed by specifying ID in the WHERE Clause. For example:

DELETE FROM Accounts WHERE ID = '4'

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Answers¶

The knowledge base information that provides solutions to the common customer support questions.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM Answers WHERE id = 12
SELECT * FROM Answers WHERE id > 15
SELECT * FROM Answers WHERE lookUpName LIKE '%test'
SELECT * FROM Answers WHERE id IN (12, 23, 123)
SELECT * FROM Answers WHERE lookUpName IS NOT NULL

INSERT¶

Insert can be executed by specifying the answerTypeId, languageId, and summary newpassword columns. The columns that are not read-only can be inserted optionally. Following is an example of how to insert into this table.

INSERT INTO Answers (answerTypeId, languageId, assignedsiblingId, summary) VALUES ('1', '1', '12', 'How do I register my product?')

UPDATE¶

Update can be executed by specifying the ID in WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE Answers SET solution = 'editorContent' WHERE ID = '12'

DELETE¶

Delete can be executed by specifying ID in the WHERE Clause. For example:

DELETE FROM Answers WHERE ID = '4'

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

AnswerVersions¶

The versioned instance of an answer. Answers are solutions to common customer support questions.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM AnswerVersions WHERE id = 12
SELECT * FROM AnswerVersions WHERE id > 15
SELECT * FROM AnswerVersions WHERE lookUpName LIKE '%test'
SELECT * FROM AnswerVersions WHERE id IN (12, 23, 123)
SELECT * FROM AnswerVersions WHERE lookUpName IS NOT NULL

UPDATE¶

Update can be executed by specifying the ID in WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE AnswerVersions SET keywords = 'test' WHERE ID = 133

DELETE¶

Delete can be executed by specifying ID in the WHERE Clause. For example:

DELETE FROM AnswerVersions WHERE ID = 133

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Assets¶

The product or service associated with an organization's customers.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM Assets WHERE id = 12
SELECT * FROM Assets WHERE id > 15
SELECT * FROM Assets WHERE lookUpName LIKE '%test'
SELECT * FROM Assets WHERE id IN (12, 23, 123)
SELECT * FROM Assets WHERE lookUpName IS NOT NULL

INSERT¶

Insert can be executed by specifying the name, productid and serialNumber columns. The columns that are not read-only can be inserted optionally. Following is an example of how to insert into this table.

INSERT INTO Assets (name, productid, serialNumber) VALUES ('ABC', 12, 'SN00123')

UPDATE¶

Update can be executed by specifying the column in WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE Assets SET contacts = 'US of America' WHERE name = 'United States (US)'

DELETE¶

Delete can be executed by specifying ID in the WHERE Clause. For example:

DELETE FROM Assets WHERE ID = '4'

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

ContactMarketingRosters¶

The information about the contact lists used in audiences in Oracle Service Cloud Outreach Cloud Service.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM ContactMarketingRosters WHERE id = 12
SELECT * FROM ContactMarketingRosters WHERE id > 15
SELECT * FROM ContactMarketingRosters WHERE lookUpName LIKE '%test'
SELECT * FROM ContactMarketingRosters WHERE id IN (12, 23, 123)
SELECT * FROM ContactMarketingRosters WHERE lookUpName IS NOT NULL

INSERT¶

Insert can be executed by specifying the isProofList and name columns. The columns that are not read-only can be inserted optionally. Following is an example of how to insert into this table.

INSERT INTO ContactMarketingRosters (isProofList, name) VALUES ('true', 'Incident extract limit')

UPDATE¶

Update can be executed. The columns that are not read-only can be Updated. For example:

UPDATE ContactMarketingRosters SET Comment = 'Incident extract limit' WHERE Name = 'Analytics Lab Attendees'

DELETE¶

Following is an example of how to Delete a record in this table. For example:

DELETE FROM ContactMarketingRosters WHERE Name = 'Analytics Lab Attendees'

Columns¶

Contacts¶

The customers or end users of Oracle B2C Service site.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM Contacts WHERE id = 12
SELECT * FROM Contacts WHERE id > 15
SELECT * FROM Contacts WHERE lookUpName LIKE '%test'
SELECT * FROM Contacts WHERE id IN (12, 23, 123)
SELECT * FROM Contacts WHERE lookUpName IS NOT NULL

INSERT¶

Insert can be executed. The columns that are not read-only can be inserted optionally. Following is an example of how to insert into this table.

INSERT INTO Contacts (bannertext) VALUES ('Agent: Knowledge')

UPDATE¶

Update can be executed. The columns that are not read-only can be Updated. For example:

UPDATE Contacts SET login = 'chris.fellows' WHERE namelast = 'Chase'

DELETE¶

Delete can be executed by specifying ID in the WHERE Clause. For example:

DELETE FROM Contacts WHERE ID = '209'

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Countries¶

The details about the countries and provinces which are used to maintain accurate address information for the organizations and contacts in Oracle B2C Service.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM Countries WHERE id = 12
SELECT * FROM Countries WHERE id > 15
SELECT * FROM Countries WHERE lookUpName LIKE '%test'
SELECT * FROM Countries WHERE id IN (12, 23, 123)
SELECT * FROM Countries WHERE lookUpName IS NOT NULL

INSERT¶

Insert can be executed by specifying the abbreviation, iSOCode and names columns. The columns that are not read-only can be inserted optionally. Following is an example of how to insert into this table.

INSERT INTO CountriesNames#TEMP (languageId, labeltext) VALUES ('7', 'Vietnam')
INSERT INTO Countries (phonecode, abbreviation, iSOCode, names) VALUES ('44', 'UK', 'UK', 'countriesNames#TEMP')

UPDATE¶

Update can be executed by specifying the column in WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE Countries SET abbreviation = 'US of America' WHERE name = 'United States (US)'

DELETE¶

Delete can be executed by specifying ID in the WHERE Clause. For example:

DELETE FROM Countries WHERE ID = '4'

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

EventSubscriptions¶

The event-based subscription management object that allows external applications to discover objects that can be subscribed.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM EventSubscriptions WHERE id = 12
SELECT * FROM EventSubscriptions WHERE id > 15
SELECT * FROM EventSubscriptions WHERE lookUpName LIKE '%test'
SELECT * FROM EventSubscriptions WHERE id IN (12, 23, 123)
SELECT * FROM EventSubscriptions WHERE lookUpName IS NOT NULL

INSERT¶

Insert can be executed by specifying the class, endPoint, eventType, integrationUser, name, objectShapeXml and objectVersion columns. The columns that are not read-only can be inserted optionally. Following is an example of how to insert into this table.

INSERT INTO EventSubscriptions (class, endPoint, eventTypeId, integrationUserId, objectShapeXml, name, objectVersionId) VALUES ('Contact', 'https://abc.com', '2', '1', 'asdc', 'queryresults', '100200')

UPDATE¶

Update can be executed. The columns that are not read-only can be Updated. For example:

UPDATE EventSubscriptions SET summary = 'Test Replacement' WHERE lookupName = 'Battery Replacement'

DELETE¶

Following is an example of how to Delete a record in this table.

DELETE FROM EventSubscriptions WHERE summary IS NULL

Columns¶

Holidays¶

The list of holidays in your organization.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM Holidays WHERE id = 12
SELECT * FROM Holidays WHERE id > 15
SELECT * FROM Holidays WHERE lookUpName LIKE '%test'
SELECT * FROM Holidays WHERE id IN (12, 23, 123)
SELECT * FROM Holidays WHERE lookUpName IS NOT NULL

INSERT¶

INSERT can be executed by specifying the holidayDate and name columns. The columns that are not read-only can be inserted optionally. Following is an example of how to insert into this table.

INSERT INTO Holidays (holidayDate, name) VALUES ('2011-01-17', 'testinsert')

UPDATE¶

Update can be executed by specifying the ID column in WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE Holidays SET holidayDate = '2012-01-17' WHERE ID = '1'

DELETE¶

Following is an example of how to Delete a record in this table.

DELETE FROM Holidays WHERE holidayDate = '2012-01-17'

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Incidents¶

The question or the request for help submitted by a customer through the Ask a Question page, email, a chat session, site or answer feedback, or from an external source using the API.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM Incidents WHERE id = 12
SELECT * FROM Incidents WHERE id > 15
SELECT * FROM Incidents WHERE lookUpName LIKE '%test'
SELECT * FROM Incidents WHERE id IN (12, 23, 123)
SELECT * FROM Incidents WHERE lookUpName IS NOT NULL

INSERT¶

Insert can be executed by specifying the primaryContact columns. The columns that are not read-only can be inserted optionally. Following is an example of how to insert into this table.

INSERT INTO Incidents (primaryContactId) VALUES ('12')

UPDATE¶

Update can be executed by specifying the ID in WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE Incidents SET languageId = '1' WHERE ID = 1

DELETE¶

Delete can be executed by specifying ID in the WHERE Clause. For example:

DELETE FROM Incidents WHERE ID = '4'

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Opportunities¶

The information about a specific sale or a pending deal with a contact or an organization that is tracked and maintained in the Oracle B2C Service knowledge base.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM Opportunities WHERE id = 12
SELECT * FROM Opportunities WHERE id > 15
SELECT * FROM Opportunities WHERE lookUpName LIKE '%test'
SELECT * FROM Opportunities WHERE id IN (12, 23, 123)
SELECT * FROM Opportunities WHERE lookUpName IS NOT NULL

INSERT¶

Insert can be executed. The columns that are not read-only can be inserted optionally. Following is an example of how to insert into this table.

INSERT INTO Opportunities (recalltime) VALUES ('2012-01-17')

UPDATE¶

Update can be executed. The columns that are not read-only can be Updated. For example:

UPDATE Opportunities SET summary = 'Test Replacement' WHERE lookupName = 'Battery Replacement'

DELETE¶

Following is an example of how to Delete a record in this table.

DELETE FROM Opportunities WHERE summary IS NULL

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Organizations¶

The company, business unit of a large company, or government agency that has an organization record in the Oracle B2C Service knowledge base.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM Organizations WHERE id = 12
SELECT * FROM Organizations WHERE id > 15
SELECT * FROM Organizations WHERE lookUpName LIKE '%test'
SELECT * FROM Organizations WHERE id IN (12, 23, 123)
SELECT * FROM Organizations WHERE lookUpName IS NOT NULL

INSERT¶

Insert can be executed by specifying the name column. The columns that are not read-only can be inserted optionally. Following is an example of how to insert into this table.

INSERT INTO Organizations (name) VALUES ('Incident records')

UPDATE¶

Update can be executed. The columns that are not read-only can be Updated. For example:

UPDATE Organizations SET  login = '001o0000005xSbZAAU' WHERE parentlookUpName IS NULL

DELETE¶

Delete can be executed by specifying ID in the WHERE Clause. For example:

DELETE FROM Organizations WHERE ID = '9'

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

PurchasedProducts¶

The information about a purchased product.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM PurchasedProducts WHERE id = 12
SELECT * FROM PurchasedProducts WHERE id > 15
SELECT * FROM PurchasedProducts WHERE lookUpName LIKE '%test'
SELECT * FROM PurchasedProducts WHERE id IN (12, 23, 123)
SELECT * FROM PurchasedProducts WHERE lookUpName IS NOT NULL

INSERT¶

Insert can be executed by specifying the comment column. The columns that are not read-only can be inserted optionally. Following is an example of how to insert into this table.

INSERT INTO PurchasedProducts (comment) VALUES ('Incident extract limit')

UPDATE¶

Update can be executed. The columns that are not read-only can be Updated. For example:

UPDATE PurchasedProducts SET comment = 'Test Replacement' WHERE contactId = '2'

DELETE¶

Following is an example of how to Delete a record in this table.

DELETE FROM PurchasedProducts WHERE summary ID = '10'

Columns¶

SalesProducts¶

The items or services sold by an organization.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM SalesProducts WHERE id = 12
SELECT * FROM SalesProducts WHERE id > 15
SELECT * FROM SalesProducts WHERE lookUpName LIKE '%test'
SELECT * FROM SalesProducts WHERE id IN (12, 23, 123)
SELECT * FROM SalesProducts WHERE lookUpName IS NOT NULL

INSERT¶

Insert can be executed by specifying the acceptCount,respondCount and names column. The columns that are not read-only can be inserted optionally. Following is an example of how to insert into this table.

INSERT INTO SalesProductsNames#TEMP (languageId, labeltext) VALUES ('1', 'Smartly Maestro')
INSERT INTO SalesProducts (acceptCount, respondCount, names) VALUES ('0', '0', salesProductsNames#TEMP)

UPDATE¶

Update can be executed. The columns that are not read-only can be Updated. For example:

UPDATE SalesProducts SET partNumber = 'SV100D' WHERE folderlookupName = 'Smartly Maestro'

DELETE¶

Following is an example of how to Delete a record in this table. For example:

DELETE FROM SalesProducts WHERE folderLookupName = 'Spaces B2B'

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

SalesTerritories¶

The specific geographical sales region. Sales representatives can be assigned specific territories for opportunity assignment.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM SalesTerritories WHERE id = 12
SELECT * FROM SalesTerritories WHERE id > 15
SELECT * FROM SalesTerritories WHERE lookUpName LIKE '%test'
SELECT * FROM SalesTerritories WHERE id IN (12, 23, 123)
SELECT * FROM SalesTerritories WHERE lookUpName IS NOT NULL

INSERT¶

Insert can be executed by specifying the names column. The columns that are not read-only can be inserted optionally. Following is an example of how to insert into this table.

INSERT INTO SalesTerritoriesNames#TEMP (languageId, labeltext) VALUES ('1', 'Community Ideas')
INSERT INTO SalesTerritories (names) VALUES ('salesTerritoriesNames#TEMP')

UPDATE¶

Update can be executed. The columns that are not read-only can be Updated. For example:

UPDATE SalesTerritories SET displayorder = '2' WHERE name = 'United States'

DELETE¶

Delete can be executed by specifying ID in the WHERE Clause. For example:

DELETE FROM SalesTerritories WHERE ID = '4'

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

ServiceCategories¶

The hierarchical service category that provides an option to group answers and incidents for better organization and refined searching in the knowledge base.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM ServiceCategories WHERE id = 12
SELECT * FROM ServiceCategories WHERE id > 15
SELECT * FROM ServiceCategories WHERE lookUpName LIKE '%test'
SELECT * FROM ServiceCategories WHERE id IN (12, 23, 123)
SELECT * FROM ServiceCategories WHERE lookUpName IS NOT NULL

INSERT¶

Insert can be executed by specifying the names column. The columns that are not read-only can be inserted optionally. Following is an example of how to insert into this table.

INSERT INTO ServiceCategoriesNames#TEMP (languageId, labeltext) VALUES ('1', 'Community Ideas')
INSERT INTO serviceCategories (names) VALUES ('ServiceCategoriesNames#TEMP')

UPDATE¶

Update can be executed. The columns that are not read-only can be Updated. For example:

UPDATE ServiceCategories SET displayOrder = '1' WHERE ParentlookUpName = 'Ordering'

DELETE¶

Delete can be executed by specifying ID in the WHERE Clause.

DELETE FROM ServiceCategories WHERE ID = '83'

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

ServiceDispositions¶

The hierarchical service disposition that provides an option for classifying and recording how incidents are ultimately resolved.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM ServiceDispositions WHERE id = 12
SELECT * FROM ServiceDispositions WHERE id > 15
SELECT * FROM ServiceDispositions WHERE lookUpName LIKE '%test'
SELECT * FROM ServiceDispositions WHERE id IN (12, 23, 123)
SELECT * FROM ServiceDispositions WHERE lookUpName IS NOT NULL

INSERT¶

Insert can be executed by specifying the names column. The columns that are not read-only can be inserted optionally. Following is an example of how to insert into this table.

INSERT INTO ServiceDispositionsNames#TEMP (serviceDispositionsId, labeltext) VALUES ('16', 'Agent: Knowledge')
INSERT INTO ServiceDispositions (names) VALUES ('serviceDispositionsNames#TEMP')

UPDATE¶

Update can be executed. The columns that are not read-only can be Updated. For example:

UPDATE ServiceDispositions SET displayOrder = '1' WHERE lookupName = 'Product: Misuse'

DELETE¶

Following is an example of how to Delete a record in this table. For example:

DELETE FROM ServiceDispositions WHERE lookupName = 'abc'

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

ServiceProducts¶

The hierarchical service product that provides an option to group answers and incidents for better organization and refined searching in the knowledge base.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM ServiceProducts WHERE id = 12
SELECT * FROM ServiceProducts WHERE id > 15
SELECT * FROM ServiceProducts WHERE lookUpName LIKE '%test'
SELECT * FROM ServiceProducts WHERE id IN (12, 23, 123)
SELECT * FROM ServiceProducts WHERE lookUpName IS NOT NULL

INSERT¶

Insert can be executed by specifying the names column. The columns that are not read-only can be inserted optionally. Following is an example of how to insert into this table.

INSERT INTO ServiceProductsNames#TEMP (languageId, labeltext) VALUES ('1', 'Community Ideas')
INSERT INTO ServiceProducts (names) VALUES ('serviceProductsNames#TEMP')

UPDATE¶

Update can be executed. The columns that are not read-only can be Updated. For example:

UPDATE ServiceProducts SET displayOrder = '4' WHERE parentlookUpName IS NULL

DELETE¶

Delete can be executed by specifying ID in the WHERE Clause. For example:

DELETE FROM ServiceProducts WHERE ID = '4'

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

StandardContents¶

The preformed text or HTML content that can be sent to customers when responding to incidents, appended to responses by a business rule, or sent by an agent during a chat session.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM StandardContents WHERE id = 12
SELECT * FROM StandardContents WHERE id > 15
SELECT * FROM StandardContents WHERE lookUpName LIKE '%test'
SELECT * FROM StandardContents WHERE id IN (12, 23, 123)
SELECT * FROM StandardContents WHERE lookUpName IS NOT NULL

INSERT¶

Insert can be executed by specifying the contentValues,name and usage in WHERE Clause. The columns that are not read-only can be inserted optionally. Following is an example of how to insert into this table.

INSERT INTO standardContents (name, usagechattext) VALUES ('Battery Replacement', 'false')

UPDATE¶

Update can be executed by specifying the ID column in WHERE Clause. The columns that are not read-only can be Updated. For example:

UPDATE StandardContents SET folderid = '100146' WHERE ID = '4'

DELETE¶

Delete can be executed by specifying ID in the WHERE Clause. For example:

DELETE FROM StandardContents WHERE ID = '3'

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Tasks¶

The information about an action or an activity scheduled to be completed within a specified time.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM Tasks WHERE id = 12
SELECT * FROM Tasks WHERE id > 15
SELECT * FROM Tasks WHERE lookUpName LIKE '%test'
SELECT * FROM Tasks WHERE id IN (12, 23, 123)
SELECT * FROM Tasks WHERE lookUpName IS NOT NULL

INSERT¶

Insert can be executed by specifying the name column. The columns that are not read-only can be inserted optionally. Following is an example of how to insert into this table.

INSERT INTO Tasks (name) VALUES ('Organize PO for Initech')

UPDATE¶

Update can be executed. The columns that are not read-only can be Updated.

UPDATE Tasks SET percentComplete = '60' WHERE name = 'Organize PO for Initech'

DELETE¶

Delete can be executed by specifying ID in the WHERE Clause. For example:

DELETE FROM Tasks WHERE ID = '7'

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Variables¶

A shortcut defined for a larger string that can be inserted in the body of an answer or inserted inline during a chat session.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM Variables WHERE id = 12
SELECT * FROM Variables WHERE id > 15
SELECT * FROM Variables WHERE lookUpName LIKE '%test'
SELECT * FROM Variables WHERE id IN (12, 23, 123)
SELECT * FROM Variables WHERE lookUpName IS NOT NULL

INSERT¶

INSERT can be executed by specifying the name column. The columns that are not read-only can be inserted optionally. Following is an example of how to insert into this table.

INSERT INTO Variables (name) VALUES ('Exampleinsertname')

UPDATE¶

Update can be executed. The columns that are not read-only can be Updated. For example:

UPDATE Variables SET folderlookupName = 'variables' WHERE name = 'Exampleinsertname'

DELETE¶

Following is an example of how to Delete a record in this table. For example:

DELETE FROM variables WHERE ID = '3'

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Views¶

Views are similar to tables in the way that data is represented; however, views are read-only.

Queries can be executed against a view as if it were a normal table.

Oracle Service Cloud Connector Views¶

AccountGroupsDescriptions¶

The language-specific string used for localization.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM AccountGroupsDescriptions WHERE AccountGroupId = 12
SELECT * FROM AccountGroupsDescriptions WHERE AccountGroupId > 15
SELECT * FROM AccountGroupsDescriptions WHERE labeltext LIKE '%test'
SELECT * FROM AccountGroupsDescriptions WHERE languageId IN (12, 23, 123)
SELECT * FROM AccountGroupsDescriptions WHERE labeltext IS NOT NULL

Columns¶

AccountGroupsNames¶

The language-specific strings used for localization of fields.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM AccountGroupsNames WHERE AccountGroupId = 12
SELECT * FROM AccountGroupsNames WHERE AccountGroupId > 15
SELECT * FROM AccountGroupsNames WHERE labeltext LIKE '%test'
SELECT * FROM AccountGroupsNames WHERE AccountGroupId IN (12, 23, 123)
SELECT * FROM AccountGroupsNames WHERE labeltext IS NOT NULL

Columns¶

AccountsEmails¶

The email address and its associated information.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM AccountsEmails WHERE accountsId = 12
SELECT * FROM AccountsEmails WHERE accountsId > 15
SELECT * FROM AccountsEmails WHERE address LIKE '%test'
SELECT * FROM AccountsEmails WHERE accountsId IN (12, 23, 123)
SELECT * FROM AccountsEmails WHERE certificate IS NOT NULL

Columns¶

AccountsPhones¶

The details related to the phone number.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM AccountsPhones WHERE accountsId = 12
SELECT * FROM AccountsPhones WHERE accountsId > 15
SELECT * FROM AccountsPhones WHERE number LIKE '%test'
SELECT * FROM AccountsPhones WHERE accountsId IN (12, 23, 123)
SELECT * FROM AccountsPhones WHERE number IS NOT NULL

Columns¶

AnalyticsReports¶

The analytics report definition that provides descriptions of a report's output columns, search criteria, and other components.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM Accounts WHERE id = 12
SELECT * FROM Accounts WHERE id > 15
SELECT * FROM Accounts WHERE lookUpName LIKE '%test'
SELECT * FROM Accounts WHERE id IN (12, 23, 123)
SELECT * FROM Accounts WHERE lookUpName IS NOT NULL

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

AnalyticsReportsFilters¶

The filters used for running an analytics report.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with the following operators. AnalyticsReportsid is a required column.

analyticsReportsid supports "="

SELECT * FROM AnalyticsReportsFilters WHERE analyticsReportsid = 12

Columns¶

AnalyticsReportsNames¶

The language-specific strings used for localization of fields.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM AnalyticsReportsNames WHERE languageId = 12
SELECT * FROM AnalyticsReportsNames WHERE languageId > 15
SELECT * FROM AnalyticsReportsNames WHERE labeltext LIKE '%test'
SELECT * FROM AnalyticsReportsNames WHERE languageId IN (12, 23, 123)
SELECT * FROM AnalyticsReportsNames WHERE labeltext IS NOT NULL

Columns¶

AnswersCategories¶

The hierarchical service category that provides an option to group answers and incidents for better organization and refined searching in the knowledge base.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM AnswersCategories WHERE CategoriesId = 12
SELECT * FROM AnswersCategories WHERE CategoriesId > 15
SELECT * FROM AnswersCategories WHERE CategoriesLookUpName LIKE '%test'
SELECT * FROM AnswersCategories WHERE CategoriesId IN (12, 23, 123)
SELECT * FROM AnswersCategories WHERE CategoriesLookUpName IS NOT NULL

Columns¶

AnswersCommonAttachments¶

The file attachment shared by sibling answers.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM AnswersCommonAttachments WHERE id = 12
SELECT * FROM AnswersCommonAttachments WHERE id > 15
SELECT * FROM AnswersCommonAttachments WHERE filename LIKE '%test'
SELECT * FROM AnswersCommonAttachments WHERE id IN (12, 23, 123)
SELECT * FROM AnswersCommonAttachments WHERE filename IS NOT NULL

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

AnswersCommonAttachmentsNames¶

The language-specific strings used for localization of fields. The label text cannot be empty or null. The labels are assembled in a list associated with a particular text field.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM AnswersCommonAttachmentsNames WHERE answersId = 12
SELECT * FROM AnswersCommonAttachmentsNames WHERE answersId > 15
SELECT * FROM AnswersCommonAttachmentsNames WHERE labelText LIKE '%test'
SELECT * FROM AnswersCommonAttachmentsNames WHERE answersId IN (12, 23, 123)
SELECT * FROM AnswersCommonAttachmentsNames WHERE labelText IS NOT NULL

Columns¶

AnswersFileAttachments¶

The file attachment shared by answers.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM AnswersFileAttachments WHERE id = 12
SELECT * FROM AnswersFileAttachments WHERE id > 15
SELECT * FROM AnswersFileAttachments WHERE filename LIKE '%test'
SELECT * FROM AnswersFileAttachments WHERE id IN (12, 23, 123)
SELECT * FROM AnswersFileAttachments WHERE filename IS NOT NULL

Columns¶

AnswersNotes¶

The note text associated with the objects such as contacts and organizations.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM AnswersNotes WHERE id = 12
SELECT * FROM AnswersNotes WHERE id > 15
SELECT * FROM AnswersNotes WHERE text LIKE '%test'
SELECT * FROM AnswersNotes WHERE id IN (12, 23, 123)
SELECT * FROM AnswersNotes WHERE text IS NOT NULL

Columns¶

AnswersProducts¶

The hierarchical service product that provides an option to group answers and incidents for better organization and refined searching in the knowledge base.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM AnswersProducts WHERE answersId = 12
SELECT * FROM AnswersProducts WHERE answersId > 15
SELECT * FROM AnswersProducts WHERE answerslookUpName LIKE '%test'
SELECT * FROM AnswersProducts WHERE answersId IN (12, 23, 123)
SELECT * FROM AnswersProducts WHERE answerslookUpName IS NOT NULL

Columns¶

AnswersRelatedAnswers¶

The knowledge base information that provides solutions to the common customer support questions.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM AnswersRelatedAnswers WHERE manualstrength = 12
SELECT * FROM AnswersRelatedAnswers WHERE manualstrength > 15
SELECT * FROM AnswersRelatedAnswers WHERE toanswerlookUpName LIKE '%test'
SELECT * FROM AnswersRelatedAnswers WHERE manualstrength IN (12, 23, 123)
SELECT * FROM AnswersRelatedAnswers WHERE toanswerlookUpName IS NOT NULL

Columns¶

AnswersSiblingAnswers¶

The knowledge base information that provides solutions to the common customer support questions.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM AnswersSiblingAnswers WHERE SiblingAnswersId = 12
SELECT * FROM AnswersSiblingAnswers WHERE SiblingAnswersId > 15
SELECT * FROM AnswersSiblingAnswers WHERE SiblingAnswersLookUpName LIKE '%test'
SELECT * FROM AnswersSiblingAnswers WHERE SiblingAnswersId IN (12, 23, 123)
SELECT * FROM AnswersSiblingAnswers WHERE SiblingAnswersLookUpName IS NOT NULL

Columns¶

AnswerVersionsCategories¶

The hierarchical service category that provides an option to group answers and incidents for better organization and refined searching in the knowledge base.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM AnswerVersionsCategories WHERE id = 12
SELECT * FROM AnswerVersionsCategories WHERE id > 15
SELECT * FROM AnswerVersionsCategories WHERE lookUpName LIKE '%test'
SELECT * FROM AnswerVersionsCategories WHERE id IN (12, 23, 123)
SELECT * FROM AnswerVersionsCategories WHERE lookUpName IS NOT NULL

Columns¶

AnswerVersionsCommonAttachments¶

The file attachment shared by sibling answers.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM AnswerVersionsCommonAttachments WHERE id = 12
SELECT * FROM AnswerVersionsCommonAttachments WHERE id > 15
SELECT * FROM AnswerVersionsCommonAttachments WHERE filename LIKE '%test'
SELECT * FROM AnswerVersionsCommonAttachments WHERE id IN (12, 23, 123)
SELECT * FROM AnswerVersionsCommonAttachments WHERE filename IS NOT NULL

Columns¶

Pseudo-Columns¶

Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

AnswerVersionsCommonAttachmentsNames¶

The language-specific strings used for localization of fields. The label text cannot be empty or null. The labels are assembled in a list associated with a particular text field.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM AnswerVersionsCommonAttachmentsNames WHERE answerVersionsId = 12
SELECT * FROM AnswerVersionsCommonAttachmentsNames WHERE answerVersionsId > 15
SELECT * FROM AnswerVersionsCommonAttachmentsNames WHERE labelText LIKE '%test'
SELECT * FROM AnswerVersionsCommonAttachmentsNames WHERE answerVersionsId IN (12, 23, 123)
SELECT * FROM AnswerVersionsCommonAttachmentsNames WHERE labelText IS NOT NULL

Columns¶

AnswerVersionsFileAttachments¶

The file attachment shared by answers.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM AnswerVersionsFileAttachments WHERE id = 12
SELECT * FROM AnswerVersionsFileAttachments WHERE id > 15
SELECT * FROM AnswerVersionsFileAttachments WHERE filename LIKE '%test'
SELECT * FROM AnswerVersionsFileAttachments WHERE id IN (12, 23, 123)
SELECT * FROM AnswerVersionsFileAttachments WHERE filename IS NOT NULL

Columns¶

AnswerVersionsNotes¶

The note text associated with the objects such as contacts and organizations.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM AnswerVersionsNotes WHERE id = 12
SELECT * FROM AnswerVersionsNotes WHERE id > 15
SELECT * FROM AnswerVersionsNotes WHERE text LIKE '%test'
SELECT * FROM AnswerVersionsNotes WHERE id IN (12, 23, 123)
SELECT * FROM AnswerVersionsNotes WHERE text IS NOT NULL

Columns¶

AnswerVersionsProducts¶

The hierarchical service product that provides an option to group answers and incidents for better organization and refined searching in the knowledge base.

Table-Specific Information¶

SELECT¶

The connector will use the Oracle Service Cloud API to process WHERE clause conditions built with =,!=,<,>,<=,>=,IN,NOT_IN,IS,IS_NOT,LIKE operators. The rest of the filters are executed client side within the connector.

SELECT * FROM AnswerVersionsProducts WHERE productsid = 12
SELECT * FROM AnswerVersionsProducts WHERE productsid > 15
SELECT * FROM AnswerVersionsProducts WHERE productslookUpName LIKE '%test'
SELECT * FROM AnswerVersionsProducts WHERE productsid IN (12, 23, 123)
SELECT * FROM AnswerVersionsProducts WHERE productslookUpName IS NOT NULL

Columns¶