The CData Sync App provides a straightforward way to continuously pipeline your Google Contacts data to any database, data lake, or data warehouse, making it easily available for Analytics, Reporting, AI, and Machine Learning.
The GoogleContacts connector can be used from the CData Sync application to pull data from GoogleContacts and move it to any of the supported destinations.
The Sync App leverages V1 of the People API to enable bidirectional access to Google Contacts.
For required properties, see the Settings tab.
For connection properties that are not typically required, see the Advanced tab.
Authorize the Sync App to access Google APIs on behalf of individual users or on behalf of a domain.
Use the OAuth authentication standard to connect to Google APIs.
The Sync App supports using user accounts and GCP instance accounts for authentication.
The following sections discuss the available authentication schemes for GoogleContacts:
AuthScheme must be set to OAuth in all user account flows.
Get an OAuth Access Token
Set the following connection properties to obtain the OAuthAccessToken:
Then call stored procedures to complete the OAuth exchange:
Once you have obtained the access and refresh tokens, you can connect to data and refresh the OAuth access token either automatically or manually.
Automatic Refresh of the OAuth Access Token
To have the driver automatically refresh the OAuth access token, set the following on the first data connection:
Manual Refresh of the OAuth Access Token
The only value needed to manually refresh the OAuth access token when connecting to data is the OAuth refresh token.
Use the RefreshOAuthAccessToken stored procedure to manually refresh the OAuthAccessToken after the ExpiresIn parameter value returned by GetOAuthAccessToken has elapsed, then set the following connection properties:
Then call RefreshOAuthAccessToken with OAuthRefreshToken set to the OAuth refresh token returned by GetOAuthAccessToken. After the new tokens have been retrieved, open a new connection by setting the OAuthAccessToken property to the value returned by RefreshOAuthAccessToken.
Finally, store the OAuth refresh token so that you can use it to manually refresh the OAuth access token after it has expired.
Option 1: Obtain and Exchange a Verifier Code
To obtain a verifier code, you must authenticate at the OAuth authorization URL.
Follow the steps below to authenticate from the machine with an internet browser and obtain the OAuthVerifier connection property.
On the headless machine, set the following connection properties to obtain the OAuth authentication values:
After the OAuth settings file is generated, you need to re-set the following properties to connect:
Option 2: Transfer OAuth Settings
Prior to connecting on a headless machine, you need to create and install a connection with the driver on a device that supports an internet browser. Set the connection properties as described in "Desktop Applications" above.
After completing the instructions in "Desktop Applications", the resulting authentication values are encrypted and written to the location specified by OAuthSettingsLocation. The default filename is OAuthSettings.txt.
Once you have successfully tested the connection, copy the OAuth settings file to your headless machine.
On the headless machine, set the following connection properties to connect to data:
When running on a GCP virtual machine, the Sync App can authenticate using a service account tied to the virtual machine. To use this mode, set AuthScheme to GCPInstanceAccount.
This section details a selection of advanced features of the GoogleContacts Sync App.
The Sync App supports the use of user defined views, virtual tables whose contents are decided by a pre-configured user defined query. These views are useful when you cannot directly control queries being issued to the drivers. For an overview of creating and configuring custom views, see User Defined Views .
Use SSL Configuration to adjust how Sync App handles TLS/SSL certificate negotiations. You can choose from various certificate formats;. For further information, see the SSLServerCert property under "Connection String Options" .
Configure the Sync App for compliance with Firewall and Proxy, including Windows proxies and HTTP proxies. You can also set up tunnel connections.
For further information, see Query Processing.
By default, the Sync App attempts to negotiate TLS with the server. The server certificate is validated against the default system trusted certificate store. You can override how the certificate gets validated using the SSLServerCert connection property.
To specify another certificate, see the SSLServerCert connection property.
To authenticate to an HTTP proxy, set the following:
Set the following properties:
This section shows the available API objects and provides more information on executing SQL to GoogleContacts APIs.
The Sync App models the GoogleContacts API as relational Tables.
Views offer additional metadata information from GoogleContacts.
Stored Procedures are function-like interfaces to GoogleContacts. Stored procedures allow you to execute operations to GoogleContacts, including downloading documents and moving envelopes.
The Sync App models the data in GoogleContacts as a list of tables in a relational database that can be queried using standard SQL statements.
| Name | Description |
| ContactGroups | Create, update, delete and query Contact Groups. |
| Contacts | Set the name of this table to any of your ContactGroups(GroupName) to create, update, delete, and query Google contacts. |
Create, update, delete and query Contact Groups.
The ContactGroups table supports the Id and MemberCount columns in the WHERE clause. The supported operators are '=, in' for Id and '=' for MemberCount.
For example:
SELECT * FROM [ContactGroups] WHERE Id = 'myContacts' SELECT * FROM [ContactGroups] WHERE Id = '45a15a878be3580a' SELECT * FROM [ContactGroups] WHERE Id = '4fe7dbbd0d26cc95' AND MemberCount = 10
To create a new ContactGroup, the Name is required. You can also insert data to ClientData columns
INSERT INTO [ContactGroups] (Name) VALUES ('Contacts Group Test')
To insert ClientData for a contactGroup, you can use the #TEMP table or create the JSON structure to provide the values to insert.
INSERT INTO ClientData#TEMP (ClientDataKey, ClientDataValue) VALUES ('Client Data 1', 'sfsdfsds45rf')
INSERT INTO ClientData#TEMP (ClientDataKey, ClientDataValue) VALUES ('Client Data 2', '2jfk24g78w2jbdk')
INSERT INTO ContactGroups (Name, ClientData) VALUES ('Insert ClientData to a Contact Group 2', 'ClientData#TEMP')
INSERT INTO ContactGroups (Name, ClientData) VALUES ('Testing Insert ClientData in Contact Group via client data columns', '[{"key": "Client Data 1","value": "sdfjkbq36"},{"key": "Client Data 2","value": "df32jkbk"}]')
You can update the Name, ClientData of a ContactGroups row (except for System Groups (GroupType As SYSTEM_CONTACT_GROUP) like My Contacts, Coworkers, and Friends) by specifying the Id column.
UPDATE [ContactGroups] SET Name = 'Salsa Friends' WHERE Id = '674ddb258de3ef81'
To delete a ContactGroup, the Id is required.
DELETE FROM [ContactGroups] WHERE Id = '674ddb258de3ef81'
| Name | Type | ReadOnly | Description |
| Id [KEY] | String | True |
The Id of the contact group. |
| ResourceName | String | True |
The ResourceName of the contact group. |
| ETag | String | True |
The HTTP entity tag of the resource. |
| Name | String | False |
The name of the contact group. |
| GroupType | String | True |
The contact group type. |
| FormattedName | String | True |
The group name formatted in the viewer's account locale. |
| MemberCount | Integer | True |
The total number of contacts in the group irrespective of max members in specified in the request. |
| MemberResourceNames | String | True |
The list of contact person resource names that are members of the contact group. |
| MetadataUpdatedTime | Datetime | True |
The metadata of the contact group. |
| MetadataDeleted | Boolean | True |
The metadata of the contact group. |
| ClientData | String | False |
The group's client data. |
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.
| Name | Type | Description |
| ClientDataKey | String |
The client specified key of the client data. |
| ClientDataValue | String |
The client specified value of the client data. |
| MaxMembers | String |
Specifies the maximum number of members to return. Defaults to 0 if not set, which will return zero members. |
Set the name of this table to any of your ContactGroups(GroupName) to create, update, delete, and query Google contacts.
The Contacts table supports the Id in the WHERE clause. The supported operators are '=, IN' for Id.
For example:
SELECT * FROM [My Contacts] WHERE Id = '567931ee88efc109'
SELECT * FROM [My Contacts] WHERE Id IN ('567931ee88efc109', '79733d1ee88efc109')
SELECT * FROM [My Contacts] WHERE SearchTerms = 'Yash'
You can insert any field into the Contacts table that is not read-only. You can add multiple values for few specific fields separated by semi-colon.
INSERT INTO [My Contacts] (GivenName, FamilyName, HomeEmailAddresses, WorkEmailAddresses, WorkPhoneNumbers, HomePhoneNumbers, HomeAddresses) VALUES ('Elizabeth', 'Bennet', '[email protected]', '[email protected]', '(206)555-1212', '(206)555-1213', '1600 Amphitheatre Pkwy Mountain View')
To insert organization details for a contact, Use the #TEMP table to insert the fields of the organization. The fields of the organization is present in ContactOrganizations view.
For Example:
INSERT INTO ContactOrganizations#TEMP (Current, Department, Domain, JobDescrption, Location, Name, StartDate) VALUES (true, 'Engineering', 'QA', 'Big Data Engineer', 'Bangalore', 'Tech Mahindra', '2021-03-01')
INSERT INTO ContactOrganizations#TEMP (Current, Department, Domain, JobDescrption, Location, Name, StartDate, EndDate) VALUES (false, 'Engineering', 'QA', 'Software Consultant', 'Bangalore', 'CData', '2019-05-23', '2020-02-17')
INSERT INTO [My Contacts] (GivenName, Organizations) VALUES ('Karan', 'ContactOrganizations#TEMP')
To insert multiple contacts at once, use the #TEMP table to insert.
For Example:
INSERT INTO MyContacts#TEMP (GivenName, FamilyName, HomeAddresses) VALUES ('Ankit', 'Singh', 'Bangalore India; Indore India')
INSERT INTO MyContacts#TEMP (GivenName, MiddleName, HomeAddresses) VALUES ('Aman', '', 'Bangalore India; Indore India')
INSERT INTO [My Contacts] (GivenName, HomeAddresses) SELECT GivenName, HomeAddresses FROM MyContacts#TEMP
You can update any field in the Contacts table that is not read-only. You can add multiple values for few specific fields separated by semi-colon.
UPDATE [My Contacts] SET GivenName = 'Elizabeth', FamilyName = 'Bennet', MobilePhoneNumbers = '+355696969999;+355676555001' WHERE Id = '48b8b9158b1db34d' UPDATE [My Contacts] SET HomeAddresses = 'Electronic City Bangalore India; Brilliant Solitaire Indore India' WHERE Id = 'c6545017396039868174'
To update details of multiple contacts at once, use the #TEMP table.
For Example:
INSERT INTO MyContacts#TEMP (Id, GivenName, HomeAddresses) VALUES ('c9197613024342508599', 'Ankit', 'Bangalore India; Indore India')
INSERT INTO MyContacts#TEMP (Id, GivenName, HomeAddresses) VALUES ('c2042847992816525584', 'Aman', 'Bangalore India; Indore India')
UPDATE [My Contacts] (Id, GivenName, HomeAddresses) SELECT Id, GivenName, HomeAddresses FROM MyContacts#TEMP
To delete a Contact, the Id is required.
DELETE FROM [My Contacts] WHERE Id = '567931ee88efc109'
To delete multiple contacts at once, use the #TEMP table.
For Example:
INSERT INTO MyContacts#TEMP (Id) VALUES ('c9197613024342508599')
INSERT INTO MyContacts#TEMP (Id) VALUES ('c2042847992816525584')
DELETE FROM [My Contacts] WHERE EXISTS SELECT Id FROM MyContacts#TEMP
| Name | Type | ReadOnly | Description |
| Id [KEY] | String | True |
The Id of the contact. |
| ResourceName | String | True |
The ResourceName of the contact. |
| Etag | String | True |
The ETag of the resource. (Note that the quotation marks are part of the ETag.) |
| NamePrefix | String | True |
The honorific prefixes, such as Mrs. or Dr. |
| FullName | String | True |
The display name formatted according to the locale specified by the viewer's account |
| GivenName | String | False |
The given name of the contact. |
| MiddleName | String | False |
The middle name of the contact. |
| FamilyName | String | False |
The family name of the contact. |
| NameSuffix | String | False |
The honorific suffixes, such as Jr. |
| PhoneticNamePrefix | String | True |
The Phonetic honorific prefixes, such as Mrs. or Dr. |
| PhoneticFullName | String | False |
The Phonetic display name formatted according to the locale specified by the viewer's account. |
| PhoneticGivenName | String | False |
The Phonetic given name of the contact. |
| PhoneticMiddleName | String | False |
The Phonetic middle name of the contact. |
| PhoneticFamilyName | String | False |
The Phonetic family name of the contact. |
| PhoneticNameSuffix | String | False |
The Phonetic honorific suffixes, such as Jr. |
| NickNames | String | False |
The nickname of the contact. |
| Birthday | Date | False |
The birthday of the contact. The format of the date is yyyy-mm-dd. |
| GenderAddressMeAs | String | False |
The type of pronoun that should be used to address the contact. |
| Gender | String | False |
The gender for the contact. |
| Photos | String | True |
The contact's photo. |
| UnlabeledEmailAddresses | String | False |
The unlabeled email addresses of the contact. Multiple email addresses should be separated by semi-colon. |
| HomeEmailAddresses | String | False |
The home email addresses of the contact. Multiple email addresses should be separated by semi-colon. |
| WorkEmailAddresses | String | False |
The work email addresses of the contact. Multiple email addresses should be separated by semi-colon. |
| OtherEmailAddresses | String | False |
The other email addresses of the contact. Multiple email addresses should be separated by semi-colon. |
| CustomEmailAddressTypes | String | False |
The custom type of the email address. This attribute should be used along with CustomEmailAddresses. Multiple custom types should be separated by semi-colon. |
| CustomEmailAddresses | String | False |
The custom value of the email address. This attribute should be used along with CustomEmailAddressTypes. Multiple custom emailAddresses should be separated by semi-colon. |
| UnlabeledPhoneNumbers | String | False |
The unlabeled phone numbers of the contacts. Multiple phone numbers should be separated by semi-colon. |
| HomePhoneNumbers | String | False |
The home phone numbers of the contacts. Multiple phone numbers should be separated by semi-colon. |
| WorkPhoneNumbers | String | False |
The work phone numbers of the contacts. Multiple phone numbers should be separated by semi-colon. |
| MobilePhoneNumbers | String | False |
The mobile phone numbers of the contacts. Multiple phone numbers should be separated by semi-colon. |
| OtherPhoneNumbers | String | False |
The homeFax phone numbers of the contacts. Multiple phone numbers should be separated by semi-colon. |
| HomeFaxes | String | False |
The workFax phone numbers of the contacts. Multiple phone numbers should be separated by semi-colon. |
| WorkFaxes | String | False |
The otherFax phone numbers of the contacts. Multiple phone numbers should be separated by semi-colon. |
| OtherFaxes | String | False |
The pager phone numbers of the contacts. Multiple phone numbers should be separated by semi-colon. |
| Pagers | String | False |
The workMobile phone numbers of the contacts. Multiple phone numbers should be separated by semi-colon. |
| WorkMobilePhoneNumbers | String | False |
The workPager phone numbers of the contacts. Multiple phone numbers should be separated by semi-colon. |
| WorkPagers | String | False |
The main phone numbers of the contacts. Multiple phone numbers should be separated by semi-colon. |
| MainPhoneNumbers | String | False |
The googleVoice phone numbers of the contacts. Multiple phone numbers should be separated by semi-colon. |
| GoogleVoicePhoneNumbers | String | False |
The other phone numbers of the contacts. Multiple phone numbers should be separated by semi-colon. |
| CustomPhoneNumberTypes | String | False |
The custom type of the phone number. This attribute should be used along with CustomPhoneNumbers. Multiple custom types should be separated by semi-colon. |
| CustomPhoneNumbers | String | False |
The custom value of the phone number. This attribute should be used along with CustomPhoneNumberTypes. Multiple custom phone numbers should be separated by semi-colon. |
| UnlabeledAddresses | String | False |
The unlabeled addresses of the contact. Multiple addresses should be separated by semi-colon. |
| HomeAddresses | String | False |
The home addresses of the contact. Multiple addresses should be separated by semi-colon. |
| WorkAddresses | String | False |
The work addresses of the contact. Multiple addresses should be separated by semi-colon. |
| OtherAddresses | String | False |
The other addresses of the contact. Multiple addresses should be separated by semi-colon. |
| CustomAddressTypes | String | False |
The custom type of the address. This attribute should be used along with CustomAddresses. Multiple custom types should be separated by semi-colon. |
| CustomAddresses | String | False |
The custom value of the address. This attribute should be used along with CustomAddressTypes. Multiple custom emailAddresses should be separated by semi-colon. |
| AgeRanges | String | True |
An age range of a contact. |
| Biography | String | False |
The short biography of the contact. |
| BiographyContentType | String | False |
The content type of the biography of the contact. |
| HomeCalendarUrls | String | True |
The home calendar urls of the contact. Multiple calendar urls should be separated by semi-colon. |
| FreeBusyCalendarUrls | String | True |
The freeBusy calendar urls of the contact. Multiple calendar urls should be separated by semi-colon. |
| WorkCalendarUrls | String | True |
The work calendar urls of the contact. Multiple calendar urls should be separated by semi-colon. |
| CustomCalendarUrlTypes | String | True |
The custom type of the address. This attribute should be used along with CustomCalendarUrls. Multiple custom types should be separated by semi-colon. |
| CustomCalendarUrls | String | True |
The custom value of the address. This attribute should be used along with CustomCalendarUrlTypes. Multiple custom calendar urls should be separated by semi-colon. |
| ClientData | String | False |
The group's client data. |
| CoverPhotos | String | True |
A contact's cover photo. |
| UnlabeledEvents | String | False |
The dates of unlabeled events. Multiple dates should be separated by semi-colon. |
| AnniversaryEvents | String | False |
The dates of anniversary events. Multiple dates should be separated by semi-colon. |
| OtherEvents | String | False |
The dates of other events. Multiple dates should be separated by semi-colon. |
| CustomEventTypes | String | False |
The custom type of an event. Multiple types should be separated by semi-colon. |
| CustomEvents | String | False |
The custom value of an event. Multiple custom event dates should be separated by semi-colon. |
| AccountExternalIds | String | False |
The account externalIds of the contact. Multiple externalIds should be separated by semi-colon. |
| CustomerExternalIds | String | False |
The customer externalIds of the contact. Multiple externalIds should be separated by semi-colon. |
| LoginIdExternalIds | String | False |
The loginId externalIds of the contact. Multiple externalIds should be separated by semi-colon. |
| NetworkExternalIds | String | False |
The network externalIds of the contact. Multiple externalIds should be separated by semi-colon. |
| OrganizationExternalIds | String | False |
The organization externalIds of the contact. Multiple externalIds should be separated by semi-colon. |
| CustomExternalIdTypes | String | False |
The custom type of the externalId. This attribute should be used along with CustomExternalIds. Multiple types should be separated by semi-colon. |
| CustomExternalIds | String | False |
The custom value of the externalId. This attribute should be used along with CustomExternalIdTypes. Multiple externalIds should be separated by semi-colon. |
| FileAses | String | True |
The name that should be used to sort the contact in a list. |
| ImClientsProtocols | String | True |
The semi-colon separated list of ImClients Protocols. Multiple protocols should be separated by semi-colon. |
| ImClientsUsernames | String | True |
The semi-colon separated list of ImClients Usernames. Multiple usernames should be separated by semi-colon. |
| Interests | String | False |
The contact's interests. |
| Locales | String | False |
The contact's locales. |
| DeskLocations | String | False |
The desk locations of the contact. Multiple locations should be separated by semi-colon. |
| GrewUpLocations | String | False |
The grewUp locations of the contact. Multiple locations should be separated by semi-colon. |
| CustomLocationTypes | String | False |
The custom types of the location. The attribute should be used along with CustomLocations. Multiple locations should be separated by semi-colon. |
| CustomLocations | String | False |
The custom value of the location. The attribute should be used along with CustomLocationsTypes. Multiple locations should be separated by semi-colon. |
| Memberships | String | True |
The resource name for the contact group, assigned by the server. Only contactGroupResourceName can be used for modifying memberships. Any contact group membership can be removed, but only user group or 'myContacts' or 'starred' system groups memberships can be added. A contact must always have at least one contact group membership. |
| MiscKeywordTypes | String | False |
The miscellaneous keyword types. Multiple types should be separated by semi-colon. Allowed Values are : TYPE_UNSPECIFIED, OUTLOOK_BILLING_INFORMATION, OUTLOOK_DIRECTORY_SERVER, OUTLOOK_KEYWORD, OUTLOOK_MILEAGE, OUTLOOK_PRIORITY, OUTLOOK_SENSITIVITY, OUTLOOK_SUBJECT, OUTLOOK_USER, HOME, WORK, OTHER The allowed values are TYPE_UNSPECIFIED, OUTLOOK_BILLING_INFORMATION, OUTLOOK_DIRECTORY_SERVER, OUTLOOK_KEYWORD, OUTLOOK_MILEAGE, OUTLOOK_PRIORITY, OUTLOOK_SENSITIVITY, OUTLOOK_SUBJECT, OUTLOOK_USER, HOME, WORK, OTHER. |
| MiscKeywordValues | String | False |
The miscellaneous keywords. Multiple miscellaneous keywords should be separated by semi-colon. |
| Occupations | String | False |
The contact's occupations |
| Organizations | String | False |
The organizations of the contact. |
| RelationshipTypes | String | True |
The contact's relation to the other person. This attribute should be used along with RelationValues. Multiple types should be separated by semi-colon. |
| RelationshipValues | String | True |
The name of the other person this relation refers to. This attribute should be used along with RelationTypes. Multiple names should be separated by semi-colon. |
| UnlabeledSipAddresses | String | False |
The dates of anniversary events. Multiple dates should be separated by semi-colon. |
| HomeSipAddresses | String | False |
The home sipAddresses of the contact. Multiple sipAddresses should be separated by semi-colon. |
| WorkSipAddresses | String | False |
The work sipAddresses of the contact. Multiple sipAddresses should be separated by semi-colon. |
| MobileSipAddresses | String | False |
The mobile sipAddresses of the contact. Multiple sipAddresses should be separated by semi-colon. |
| OtherSipAddresses | String | False |
The other sipAddresses of the contact. Multiple sipAddresses should be separated by semi-colon. |
| CustomSipAddressTypes | String | False |
The custom type of the sipAddress. This attribute should be used along with CustomSipAddresses. Multiple types should be separated by semi-colon. |
| CustomSipAddresses | String | False |
The custom value of the sipAddress. This attribute should be used along with CustomSipAddressTypes. Multiple sipAddresses should be separated by semi-colon. |
| Skills | String | True |
The skills that the contact has. |
| UnlabeledUrls | String | False |
The unlabeled website urls of the contact. Multiple urls should be separated by semi-colon. |
| HomeUrls | String | False |
The home website urls of the contact. Multiple urls should be separated by semi-colon. |
| WorkUrls | String | False |
The work website urls of the contact. Multiple urls should be separated by semi-colon. |
| BlogUrls | String | False |
The blog website urls of the contact. Multiple urls should be separated by semi-colon. |
| ProfileUrls | String | False |
The profile website urls of the contact. Multiple urls should be separated by semi-colon. |
| HomePageUrls | String | False |
The homePage website urls of the contact. Multiple urls should be separated by semi-colon. |
| FtpUrls | String | False |
The ftp website urls of the contact. Multiple urls should be separated by semi-colon. |
| ReservationsUrls | String | False |
The reservations website urls of the contact. Multiple urls should be separated by semi-colon. |
| OtherUrls | String | False |
The appInstall Page website urls of the contact. Multiple urls should be separated by semi-colon. |
| AppInstallPageUrls | String | False |
The other website urls of the contact. Multiple urls should be separated by semi-colon. |
| CustomUrlTypes | String | False |
The custom type of the website url. This attribute values should be used along with CustomUrls. Multiple urls should be separated by semi-colon. |
| CustomUrls | String | False |
The custom value of the website url. This attribute values should be used along with CustomUrlTypes. Multiple urls should be separated by semi-colon. |
| UnlabeledCountry | String | True |
The unlabeled country of the contact. Multiple addresses should be separated by semi-colon. |
| UnlabeledCity | String | True |
The unlabeled city of the contact. Multiple addresses should be separated by semi-colon. |
| UnlabeledCountryCode | String | True |
The unlabeled country code of the contact. Multiple addresses should be separated by semi-colon. |
| UnlabeledExtendedAddress | String | True |
The unlabeled extended address of the contact. Multiple addresses should be separated by semi-colon. |
| UnlabeledPostalCode | String | True |
The unlabeled postal code of the contact. Multiple addresses should be separated by semi-colon. |
| UnlabeledRegion | String | True |
The unlabeled region of the contact. Multiple addresses should be separated by semi-colon. |
| UnlabeledStreetAddress | String | True |
The unlabeled street address of the contact. Multiple addresses should be separated by semi-colon. |
| HomeCountry | String | True |
The home country of the contact. Multiple addresses should be separated by semi-colon. |
| HomeCity | String | True |
The home city of the contact. Multiple addresses should be separated by semi-colon. |
| HomeCountryCode | String | True |
The home country code of the contact. Multiple addresses should be separated by semi-colon. |
| HomeExtendedAddress | String | True |
The home extended address of the contact. Multiple addresses should be separated by semi-colon. |
| HomePostalCode | String | True |
The home postal code of the contact. Multiple addresses should be separated by semi-colon. |
| HomeRegion | String | True |
The home region of the contact. Multiple addresses should be separated by semi-colon. |
| HomeStreetAddress | String | True |
The home street address of the contact. Multiple addresses should be separated by semi-colon. |
| WorkCountry | String | True |
The work country of the contact. Multiple addresses should be separated by semi-colon. |
| WorkCity | String | True |
The work city of the contact. Multiple addresses should be separated by semi-colon. |
| WorkCountryCode | String | True |
The work country code of the contact. Multiple addresses should be separated by semi-colon. |
| WorkExtendedAddress | String | True |
The work extended address of the contact. Multiple addresses should be separated by semi-colon. |
| WorkPostalCode | String | True |
The work postal code of the contact. Multiple addresses should be separated by semi-colon. |
| WorkRegion | String | True |
The work region of the contact. Multiple addresses should be separated by semi-colon. |
| WorkStreetAddress | String | True |
The work street address of the contact. Multiple addresses should be separated by semi-colon. |
| OtherCountry | String | True |
The other country of the contact. Multiple addresses should be separated by semi-colon. |
| OtherCity | String | True |
The other city of the contact. Multiple addresses should be separated by semi-colon. |
| OtherCountryCode | String | True |
The other country code of the contact. Multiple addresses should be separated by semi-colon. |
| OtherExtendedAddress | String | True |
The other extended address of the contact. Multiple addresses should be separated by semi-colon. |
| OtherPostalCode | String | True |
The other postal code of the contact. Multiple addresses should be separated by semi-colon. |
| OtherRegion | String | True |
The other region of the contact. Multiple addresses should be separated by semi-colon. |
| OtherStreetAddress | String | True |
The other street address of the contact. Multiple addresses should be separated by semi-colon. |
| CustomCountry | String | True |
The custom country of the contact. Multiple addresses should be separated by semi-colon. |
| CustomCity | String | True |
The custom city of the contact. Multiple addresses should be separated by semi-colon. |
| CustomCountryCode | String | True |
The custom country code of the contact. Multiple addresses should be separated by semi-colon. |
| CustomExtendedAddress | String | True |
The custom extended address of the contact. Multiple addresses should be separated by semi-colon. |
| CustomPostalCode | String | True |
The custom postal code of the contact. Multiple addresses should be separated by semi-colon. |
| CustomRegion | String | True |
The custom region of the contact. Multiple addresses should be separated by semi-colon. |
| CustomStreetAddress | String | True |
The custom street address of the contact. Multiple addresses should be separated by semi-colon. |
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.
| Name | Type | Description |
| SearchTerms | String |
The query matches on a contact's names, nickNames, emailAddresses, phoneNumbers, and organizations fields that are from the CONTACT source. Maximum 10 matching rows will be returned. |
| ClientDataKey | String |
The client specified key of the client data. |
| ClientDataValue | String |
The client specified value of the client data. |
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.
| Name | Description |
| ContactOrganizations | This view specifies all the details of the Contact's Organizations |
| GroupMembers | Query contact group resource names |
| OtherContacts | The view specifies all the details of Other Contacts |
| PeopleConnections | This view specifies all the details of People Connections |
This view specifies all the details of the Contact's Organizations
The ContactOrganizations view supports the Id in the WHERE clause. The supported operators are '=, IN' for Id.
For example:
SELECT * FROM [ContactOrganizations] WHERE Id = '567931ee88efc109'
SELECT * FROM [ContactOrganizations] WHERE Id IN ('567931ee88efc109', '79733d1ee88efc109')
| Name | Type | Description |
| Id | String | The Id of the contact. |
| ResourceName | String | The resource name of the contact. |
| Current | Boolean | True if organization is the person's current organization |
| Department | String | The person's department at the organization. |
| Domain | String | The domain name associated with the organization |
| FormattedType | String | The type of the organization translated and formatted in the viewer's account locale |
| JobDescription | String | The person's job description at the organization. |
| Location | String | The location of the organization office the person works at. |
| Name | String | The name of the organization. |
| PhoneticName | String | The phonetic name of the organization. |
| StartDate | Date | The start date when the person joined the organization. |
| EndDate | Date | The end date when the person left the organization. |
| Symbol | String | The symbol associated with the organization. |
| Title | String | The contact's job title at the organization. |
| Type | String | The type of the organization. |
Query contact group resource names
The GroupMembers view supports the Id and MemberCount columns in the WHERE clause. Id is required for this view.
For example:
SELECT * FROM [GroupMembers] WHERE Id = '4fe7dbbd0d26cc95'
| Name | Type | Description |
| Id | String | The Id of the contact group. |
| MemberCount | Integer | The total number of contacts in the group irrespective of max members in specified in the request. |
| ContactId | String | The list of contact person resource names that are members of the contact group. |
The view specifies all the details of Other Contacts
SELECT * FROM [OtherContacts] WHERE SearchTerms = 'Yash'
| Name | Type | Description |
| Id [KEY] | String | The Id of the contact. |
| ResourceName | String | The ResourceName of the contact. |
| Etag | String | The ETag of the resource. (Note that the quotation marks are part of the ETag.) |
| NamePrefix | String | The honorific prefixes, such as Mrs. or Dr. |
| FullName | String | The display name formatted according to the locale specified by the viewer's account |
| GivenName | String | The given name of the contact. |
| MiddleName | String | The middle name of the contact. |
| FamilyName | String | The family name of the contact. |
| NameSuffix | String | The honorific suffixes, such as Jr. |
| PhoneticNamePrefix | String | The Phonetic honorific prefixes, such as Mrs. or Dr. |
| PhoneticFullName | String | The Phonetic display name formatted according to the locale specified by the viewer's account. |
| PhoneticGivenName | String | The Phonetic given name of the contact. |
| PhoneticMiddleName | String | The Phonetic middle name of the contact. |
| PhoneticFamilyName | String | The Phonetic family name of the contact. |
| PhoneticNameSuffix | String | The Phonetic honorific suffixes, such as Jr. |
| UnlabeledEmailAddresses | String | The unlabeled email addresses of the contact. Multiple email addresses should be separated by comma. |
| HomeEmailAddresses | String | The home email addresses of the contact. Multiple email addresses should be separated by comma. |
| WorkEmailAddresses | String | The work email addresses of the contact. Multiple email addresses should be separated by comma. |
| OtherEmailAddresses | String | The other email addresses of the contact. Multiple email addresses should be separated by comma. |
| CustomEmailAddressTypes | String | The custom type of the email address. This attribute should be used along with CustomEmailAddresses. Multiple custom types should be separated by comma. |
| CustomEmailAddresses | String | The custom value of the email address. This attribute should be used along with CustomEmailAddressTypes. Multiple custom emailAddresses should be separated by comma. |
| UnlabeledPhoneNumbers | String | The unlabeled phone numbers of the contacts. Multiple phone numbers should be separated by comma. |
| HomePhoneNumbers | String | The home phone numbers of the contacts. Multiple phone numbers should be separated by comma. |
| WorkPhoneNumbers | String | The work phone numbers of the contacts. Multiple phone numbers should be separated by comma. |
| MobilePhoneNumbers | String | The mobile phone numbers of the contacts. Multiple phone numbers should be separated by comma. |
| HomeFaxes | String | The homeFax phone numbers of the contacts. Multiple phone numbers should be separated by comma. |
| WorkFaxes | String | The workFax phone numbers of the contacts. Multiple phone numbers should be separated by comma. |
| OtherFaxes | String | The otherFax phone numbers of the contacts. Multiple phone numbers should be separated by comma. |
| Pagers | String | The pager phone numbers of the contacts. Multiple phone numbers should be separated by comma. |
| WorkMobilePhoneNumbers | String | The workMobile phone numbers of the contacts. Multiple phone numbers should be separated by comma. |
| WorkPagers | String | The workPager phone numbers of the contacts. Multiple phone numbers should be separated by comma. |
| MainPhoneNumbers | String | The main phone numbers of the contacts. Multiple phone numbers should be separated by comma. |
| GoogleVoicePhoneNumbers | String | The googleVoice phone numbers of the contacts. Multiple phone numbers should be separated by comma. |
| OtherPhoneNumbers | String | The other phone numbers of the contacts. Multiple phone numbers should be separated by comma. |
| CustomPhoneNumberTypes | String | The custom type of the phone number. This attribute should be used along with CustomPhoneNumbers. Multiple custom types should be separated by comma. |
| CustomPhoneNumbers | String | The custom value of the phone number. This attribute should be used along with CustomPhoneNumberTypes. Multiple custom phone numbers should be separated by comma. |
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.
| Name | Type | Description |
| SearchTerms | String | The query matches on a contact's names, emailAddresses, and phoneNumbers fields that are from the OTHER_CONTACT source. Maximum 10 matching rows will be returned. |
This view specifies all the details of People Connections
| Name | Type | Description |
| Id [KEY] | String | The Id of the contact. |
| ResourceName | String | The ResourceName of the contact. |
| Etag | String | The ETag of the resource. (Note that the quotation marks are part of the ETag.) |
| NamePrefix | String | The honorific prefixes, such as Mrs. or Dr. |
| FullName | String | The display name formatted according to the locale specified by the viewer's account |
| GivenName | String | The given name of the contact. |
| MiddleName | String | The middle name of the contact. |
| FamilyName | String | The family name of the contact. |
| NameSuffix | String | The honorific suffixes, such as Jr. |
| PhoneticNamePrefix | String | The Phonetic honorific prefixes, such as Mrs. or Dr. |
| PhoneticFullName | String | The Phonetic display name formatted according to the locale specified by the viewer's account. |
| PhoneticGivenName | String | The Phonetic given name of the contact. |
| PhoneticMiddleName | String | The Phonetic middle name of the contact. |
| PhoneticFamilyName | String | The Phonetic family name of the contact. |
| PhoneticNameSuffix | String | The Phonetic honorific suffixes, such as Jr. |
| NickNames | String | The nickname of the contact. |
| Birthday | Date | The birthday of the contact. The format of the date is yyyy-mm-dd. |
| GenderAddressMeAs | String | The type of pronoun that should be used to address the contact. |
| Gender | String | The gender for the contact. |
| Photos | String | The contact's photo. |
| UnlabeledEmailAddresses | String | The unlabeled email addresses of the contact. Multiple email addresses should be separated by semi-colon. |
| HomeEmailAddresses | String | The home email addresses of the contact. Multiple email addresses should be separated by semi-colon. |
| WorkEmailAddresses | String | The work email addresses of the contact. Multiple email addresses should be separated by semi-colon. |
| OtherEmailAddresses | String | The other email addresses of the contact. Multiple email addresses should be separated by semi-colon. |
| CustomEmailAddressTypes | String | The custom type of the email address. This attribute should be used along with CustomEmailAddresses. Multiple custom types should be separated by semi-colon. |
| CustomEmailAddresses | String | The custom value of the email address. This attribute should be used along with CustomEmailAddressTypes. Multiple custom emailAddresses should be separated by semi-colon. |
| UnlabeledPhoneNumbers | String | The unlabeled phone numbers of the contacts. Multiple phone numbers should be separated by semi-colon. |
| HomePhoneNumbers | String | The home phone numbers of the contacts. Multiple phone numbers should be separated by semi-colon. |
| WorkPhoneNumbers | String | The work phone numbers of the contacts. Multiple phone numbers should be separated by semi-colon. |
| MobilePhoneNumbers | String | The mobile phone numbers of the contacts. Multiple phone numbers should be separated by semi-colon. |
| OtherPhoneNumbers | String | The homeFax phone numbers of the contacts. Multiple phone numbers should be separated by semi-colon. |
| HomeFaxes | String | The workFax phone numbers of the contacts. Multiple phone numbers should be separated by semi-colon. |
| WorkFaxes | String | The otherFax phone numbers of the contacts. Multiple phone numbers should be separated by semi-colon. |
| OtherFaxes | String | The pager phone numbers of the contacts. Multiple phone numbers should be separated by semi-colon. |
| Pagers | String | The workMobile phone numbers of the contacts. Multiple phone numbers should be separated by semi-colon. |
| WorkMobilePhoneNumbers | String | The workPager phone numbers of the contacts. Multiple phone numbers should be separated by semi-colon. |
| WorkPagers | String | The main phone numbers of the contacts. Multiple phone numbers should be separated by semi-colon. |
| MainPhoneNumbers | String | The googleVoice phone numbers of the contacts. Multiple phone numbers should be separated by semi-colon. |
| GoogleVoicePhoneNumbers | String | The other phone numbers of the contacts. Multiple phone numbers should be separated by semi-colon. |
| CustomPhoneNumberTypes | String | The custom type of the phone number. This attribute should be used along with CustomPhoneNumbers. Multiple custom types should be separated by semi-colon. |
| CustomPhoneNumbers | String | The custom value of the phone number. This attribute should be used along with CustomPhoneNumberTypes. Multiple custom phone numbers should be separated by semi-colon. |
| UnlabeledAddresses | String | The unlabeled addresses of the contact. Multiple addresses should be separated by semi-colon. |
| HomeAddresses | String | The home addresses of the contact. Multiple addresses should be separated by semi-colon. |
| WorkAddresses | String | The work addresses of the contact. Multiple addresses should be separated by semi-colon. |
| OtherAddresses | String | The other addresses of the contact. Multiple addresses should be separated by semi-colon. |
| CustomAddressTypes | String | The custom type of the address. This attribute should be used along with CustomAddresses. Multiple custom types should be separated by semi-colon. |
| CustomAddresses | String | The custom value of the address. This attribute should be used along with CustomAddressTypes. Multiple custom emailAddresses should be separated by semi-colon. |
| AgeRanges | String | An age range of a contact. |
| Biography | String | The short biography of the contact. |
| BiographyContentType | String | The content type of the biography of the contact. |
| HomeCalendarUrls | String | The home calendar urls of the contact. Multiple calendar urls should be separated by semi-colon. |
| FreeBusyCalendarUrls | String | The freeBusy calendar urls of the contact. Multiple calendar urls should be separated by semi-colon. |
| WorkCalendarUrls | String | The work calendar urls of the contact. Multiple calendar urls should be separated by semi-colon. |
| CustomCalendarUrlTypes | String | The custom type of the address. This attribute should be used along with CustomCalendarUrls. Multiple custom types should be separated by semi-colon. |
| CustomCalendarUrls | String | The custom value of the address. This attribute should be used along with CustomCalendarUrlTypes. Multiple custom calendar urls should be separated by semi-colon. |
| ClientData | String | The group's client data. |
| CoverPhotos | String | A contact's cover photo. |
| UnlabeledEvents | String | The dates of unlabeled events. Multiple dates should be separated by semi-colon. |
| AnniversaryEvents | String | The dates of anniversary events. Multiple dates should be separated by semi-colon. |
| OtherEvents | String | The dates of other events. Multiple dates should be separated by semi-colon. |
| CustomEventTypes | String | The custom type of an event. Multiple types should be separated by semi-colon. |
| CustomEvents | String | The custom value of an event. Multiple custom event dates should be separated by semi-colon. |
| AccountExternalIds | String | The account externalIds of the contact. Multiple externalIds should be separated by semi-colon. |
| CustomerExternalIds | String | The customer externalIds of the contact. Multiple externalIds should be separated by semi-colon. |
| LoginIdExternalIds | String | The loginId externalIds of the contact. Multiple externalIds should be separated by semi-colon. |
| NetworkExternalIds | String | The network externalIds of the contact. Multiple externalIds should be separated by semi-colon. |
| OrganizationExternalIds | String | The organization externalIds of the contact. Multiple externalIds should be separated by semi-colon. |
| CustomExternalIdTypes | String | The custom type of the externalId. This attribute should be used along with CustomExternalIds. Multiple types should be separated by semi-colon. |
| CustomExternalIds | String | The custom value of the externalId. This attribute should be used along with CustomExternalIdTypes. Multiple externalIds should be separated by semi-colon. |
| FileAses | String | The name that should be used to sort the contact in a list. |
| ImClientsProtocols | String | The custom type of the imClient. This attribute should be used along with CustomImClients. Multiple custom types should be separated by semi-colon. |
| ImClientsUsernames | String | The custom value of the imClient. This attribute should be used along with CustomImClientTypes. Multiple custom imClients should be separated by semi-colon. |
| Interests | String | The contact's interests. |
| Locales | String | The contact's locales. |
| DeskLocations | String | The desk locations of the contact. Multiple locations should be separated by semi-colon. |
| GrewUpLocations | String | The grewUp locations of the contact. Multiple locations should be separated by semi-colon. |
| CustomLocationTypes | String | The custom types of the location. The attribute should be used along with CustomLocations. Multiple locations should be separated by semi-colon. |
| CustomLocations | String | The custom value of the location. The attribute should be used along with CustomLocationsTypes. Multiple locations should be separated by semi-colon. |
| Memberships | String | The resource name for the contact group, assigned by the server. Only contactGroupResourceName can be used for modifying memberships. Any contact group membership can be removed, but only user group or 'myContacts' or 'starred' system groups memberships can be added. A contact must always have at least one contact group membership. |
| MiscKeywordTypes | String | The miscellaneous keyword types. Multiple types should be separated by semi-colon. Allowed Values are : TYPE_UNSPECIFIED, OUTLOOK_BILLING_INFORMATION, OUTLOOK_DIRECTORY_SERVER, OUTLOOK_KEYWORD, OUTLOOK_MILEAGE, OUTLOOK_PRIORITY, OUTLOOK_SENSITIVITY, OUTLOOK_SUBJECT, OUTLOOK_USER, HOME, WORK, OTHER
The allowed values are TYPE_UNSPECIFIED, OUTLOOK_BILLING_INFORMATION, OUTLOOK_DIRECTORY_SERVER, OUTLOOK_KEYWORD, OUTLOOK_MILEAGE, OUTLOOK_PRIORITY, OUTLOOK_SENSITIVITY, OUTLOOK_SUBJECT, OUTLOOK_USER, HOME, WORK, OTHER. |
| MiscKeywordValues | String | The miscellaneous keywords. Multiple miscellaneous keywords should be separated by semi-colon. |
| Occupations | String | The contact's occupations |
| Organizations | String | The organizations of the contact. |
| RelationshipTypes | String | The contact's relation to the other person. This attribute should be used along with RelationValues. Multiple types should be separated by semi-colon. |
| RelationshipValues | String | The name of the other person this relation refers to. This attribute should be used along with RelationTypes. Multiple names should be separated by semi-colon. |
| UnlabeledSipAddresses | String | The unlabeled sipAddresses of the contact. Multiple sipAddresses should be separated by semi-colon. |
| HomeSipAddresses | String | The home sipAddresses of the contact. Multiple sipAddresses should be separated by semi-colon. |
| WorkSipAddresses | String | The work sipAddresses of the contact. Multiple sipAddresses should be separated by semi-colon. |
| MobileSipAddresses | String | The mobile sipAddresses of the contact. Multiple sipAddresses should be separated by semi-colon. |
| OtherSipAddresses | String | The other sipAddresses of the contact. Multiple sipAddresses should be separated by semi-colon. |
| CustomSipAddressTypes | String | The custom type of the sipAddress. This attribute should be used along with CustomSipAddresses. Multiple types should be separated by semi-colon. |
| CustomSipAddresses | String | The custom value of the sipAddress. This attribute should be used along with CustomSipAddressTypes. Multiple sipAddresses should be separated by semi-colon. |
| Skills | String | The skills that the contact has. |
| UnlabeledUrls | String | The unlabeled website urls of the contact. Multiple urls should be separated by semi-colon. |
| HomeUrls | String | The home website urls of the contact. Multiple urls should be separated by semi-colon. |
| WorkUrls | String | The work website urls of the contact. Multiple urls should be separated by semi-colon. |
| BlogUrls | String | The blog website urls of the contact. Multiple urls should be separated by semi-colon. |
| ProfileUrls | String | The profile website urls of the contact. Multiple urls should be separated by semi-colon. |
| HomePageUrls | String | The homePage website urls of the contact. Multiple urls should be separated by semi-colon. |
| FtpUrls | String | The ftp website urls of the contact. Multiple urls should be separated by semi-colon. |
| ReservationsUrls | String | The reservations website urls of the contact. Multiple urls should be separated by semi-colon. |
| OtherUrls | String | The appInstall Page website urls of the contact. Multiple urls should be separated by semi-colon. |
| AppInstallPageUrls | String | The other website urls of the contact. Multiple urls should be separated by semi-colon. |
| CustomUrlTypes | String | The custom type of the website url. This attribute values should be used along with CustomUrls. Multiple urls should be separated by semi-colon. |
| CustomUrls | String | The custom value of the website url. This attribute values should be used along with CustomUrlTypes. Multiple urls should be separated by semi-colon. |
The connection string properties are the various options that can be used to establish a connection. This section provides a complete list of the options you can configure in the connection string for this provider. Click the links for further details.
For more information on establishing a connection, see Establishing a Connection.
| Property | Description |
| AuthScheme | The type of authentication to use when connecting to GoogleContacts. |
| Property | Description |
| OAuthClientId | Specifies the client Id that was assigned the custom OAuth application was created. (Also known as the consumer key.) This ID registers the custom application with the OAuth authorization server. |
| OAuthClientSecret | Specifies the client secret that was assigned when the custom OAuth application was created. (Also known as the consumer secret ). This secret registers the custom application with the OAuth authorization server. |
| DelegatedServiceAccounts | A space-delimited list of service account emails for delegated requests. |
| RequestingServiceAccount | A service account email to make a delegated request. |
| Scope | Specify scope to obtain the initial access and refresh token. |
| Property | Description |
| OAuthJWTCert | The JWT Certificate store. |
| OAuthJWTCertType | The type of key store containing the JWT Certificate. |
| OAuthJWTCertPassword | The password for the OAuth JWT certificate used to access a certificate store that requires a password. If the certificate store does not require a password, leave this property blank. |
| OAuthJWTCertSubject | The subject of the OAuth JWT certificate used to locate a matching certificate in the store. Supports partial matches and the wildcard '*' to select the first certificate. |
| OAuthJWTIssuer | The issuer of the Java Web Token. |
| OAuthJWTSubject | The user subject for which the application is requesting delegated access. |
| Property | Description |
| SSLServerCert | Specifies the certificate to be accepted from the server when connecting using TLS/SSL. |
| Property | Description |
| FirewallType | Specifies the protocol the provider uses to tunnel traffic through a proxy-based firewall. |
| FirewallServer | Identifies the IP address, DNS name, or host name of a proxy used to traverse a firewall and relay user queries to network resources. |
| FirewallPort | Specifies the TCP port to be used for a proxy-based firewall. |
| FirewallUser | Identifies the user ID of the account authenticating to a proxy-based firewall. |
| FirewallPassword | Specifies the password of the user account authenticating to a proxy-based firewall. |
| Property | Description |
| ProxyAutoDetect | Specifies whether the provider checks your system proxy settings for existing proxy server configurations, rather than using a manually specified proxy server. |
| ProxyServer | The hostname or IP address of the proxy server that you want to route HTTP traffic through. |
| ProxyPort | The TCP port on your specified proxy server (set in the ProxyServer connection property) that has been reserved for routing HTTP traffic to and from the client. |
| ProxyAuthScheme | Specifies the authentication method the provider uses when authenticating to the proxy server specified in the ProxyServer connection property. |
| ProxyUser | The username of a user account registered with the proxy server specified in the ProxyServer connection property. |
| ProxyPassword | The password associated with the user specified in the ProxyUser connection property. |
| ProxySSLType | The SSL type to use when connecting to the proxy server specified in the ProxyServer connection property. |
| ProxyExceptions | A semicolon separated list of destination hostnames or IPs that are exempt from connecting through the proxy server set in the ProxyServer connection property. |
| Property | Description |
| LogModules | Specifies the core modules to include in the log file. Use a semicolon-separated list of module names. By default, all modules are logged. |
| Property | Description |
| Location | Specifies the location of a directory containing schema files that define tables, views, and stored procedures. Depending on your service's requirements, this may be expressed as either an absolute path or a relative path. |
| BrowsableSchemas | Optional setting that restricts the schemas reported to a subset of all available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC . |
| Tables | Optional setting that restricts the tables reported to a subset of all available tables. For example, Tables=TableA,TableB,TableC . |
| Views | Optional setting that restricts the views reported to a subset of the available tables. For example, Views=ViewA,ViewB,ViewC . |
| Property | Description |
| AWSWorkloadIdentityConfig | Configuration properties to provide when using Workload Identity Federation via AWS. |
| MaxRows | Specifies the maximum rows returned for queries without aggregation or GROUP BY. |
| Other | Specifies additional hidden properties for specific use cases. These are not required for typical provider functionality. Use a semicolon-separated list to define multiple properties. |
| PseudoColumns | Specifies the pseudocolumns to expose as table columns. Use the format 'TableName=ColumnName;TableName=ColumnName'. The default is an empty string, which disables this property. |
| Timeout | Specifies the maximum time, in seconds, that the provider waits for a server response before throwing a timeout error. The default is 60 seconds. Set to 0 to disable the timeout. |
| UserDefinedViews | Specifies a filepath to a JSON configuration file defining custom views. The provider automatically detects and uses the views specified in this file. |
| WorkloadPoolId | The ID of your Workload Identity Federation pool. |
| WorkloadProjectId | The ID of the Google Cloud project that hosts your Workload Identity Federation pool. |
| WorkloadProviderId | The ID of your Workload Identity Federation pool provider. |
This section provides a complete list of the Authentication properties you can configure in the connection string for this provider.
| Property | Description |
| AuthScheme | The type of authentication to use when connecting to GoogleContacts. |
The type of authentication to use when connecting to GoogleContacts.
This section provides a complete list of the OAuth properties you can configure in the connection string for this provider.
| Property | Description |
| OAuthClientId | Specifies the client Id that was assigned the custom OAuth application was created. (Also known as the consumer key.) This ID registers the custom application with the OAuth authorization server. |
| OAuthClientSecret | Specifies the client secret that was assigned when the custom OAuth application was created. (Also known as the consumer secret ). This secret registers the custom application with the OAuth authorization server. |
| DelegatedServiceAccounts | A space-delimited list of service account emails for delegated requests. |
| RequestingServiceAccount | A service account email to make a delegated request. |
| Scope | Specify scope to obtain the initial access and refresh token. |
Specifies the client Id that was assigned the custom OAuth application was created. (Also known as the consumer key.) This ID registers the custom application with the OAuth authorization server.
OAuthClientId is one of a handful of connection parameters that need to be set before users can authenticate via OAuth. For details, see Establishing a Connection.
Specifies the client secret that was assigned when the custom OAuth application was created. (Also known as the consumer secret ). This secret registers the custom application with the OAuth authorization server.
OAuthClientSecret is one of a handful of connection parameters that need to be set before users can authenticate via OAuth. For details, see Establishing a Connection.
A space-delimited list of service account emails for delegated requests.
The service account emails must be specified in a space-delimited list.
Each service account must be granted the roles/iam.serviceAccountTokenCreator role on its next service account in the chain.
The last service account in the chain must be granted the roles/iam.serviceAccountTokenCreator role on the requesting service account. The requesting service account is the one specified in the RequestingServiceAccount property.
Note that for delegated requests, the requesting service account must have the permission iam.serviceAccounts.getAccessToken, which can also be granted through the serviceAccountTokenCreator role.
A service account email to make a delegated request.
The service account email of the account for which the credentials are requested in a delegated request. With the list of delegated service accounts in DelegatedServiceAccounts, this property is used to make a delegated request.
You must have the IAM permission iam.serviceAccounts.getAccessToken on this service account.
Specify scope to obtain the initial access and refresh token.
Scopes are set to define what kind of access the authenticating user will have; for example, read, read and write, restricted access to sensitive information. System administrators can use scopes to selectively enable access by functionality or security clearance.
When InitiateOAuth is set to GETANDREFRESH, you must use this property if you want to change which scopes are requested. When InitiateOAuth is set to either REFRESH or OFF, you can use either this property or the Scope input to change which scopes are requested.
Specify scope to obtain the initial access and refresh token.
This section provides a complete list of the JWT OAuth properties you can configure in the connection string for this provider.
| Property | Description |
| OAuthJWTCert | The JWT Certificate store. |
| OAuthJWTCertType | The type of key store containing the JWT Certificate. |
| OAuthJWTCertPassword | The password for the OAuth JWT certificate used to access a certificate store that requires a password. If the certificate store does not require a password, leave this property blank. |
| OAuthJWTCertSubject | The subject of the OAuth JWT certificate used to locate a matching certificate in the store. Supports partial matches and the wildcard '*' to select the first certificate. |
| OAuthJWTIssuer | The issuer of the Java Web Token. |
| OAuthJWTSubject | The user subject for which the application is requesting delegated access. |
The JWT Certificate store.
The name of the certificate store for the client certificate.
The OAuthJWTCertType field specifies the type of the certificate store specified by OAuthJWTCert. If the store is password protected, specify the password in OAuthJWTCertPassword.
OAuthJWTCert is used in conjunction with the OAuthJWTCertSubject field in order to specify client certificates. If OAuthJWTCert has a value, and OAuthJWTCertSubject is set, a search for a certificate is initiated. Please refer to the OAuthJWTCertSubject field for details.
Designations of certificate stores are platform-dependent.
The following are designations of the most common User and Machine certificate stores in Windows:
| MY | A certificate store holding personal certificates with their associated private keys. |
| CA | Certifying authority certificates. |
| ROOT | Root certificates. |
| SPC | Software publisher certificates. |
In Java, the certificate store normally is a file containing certificates and optional private keys.
When the certificate store type is PFXFile, this property must be set to the name of the file. When the type is PFXBlob, the property must be set to the binary contents of a PFX file (i.e. PKCS12 certificate store).
The type of key store containing the JWT Certificate.
This property can take one of the following values:
| USER | For Windows, this specifies that the certificate store is a certificate store owned by the current user. Note: This store type is not available in Java. |
| MACHINE | For Windows, this specifies that the certificate store is a machine store. Note: this store type is not available in Java. |
| PFXFILE | The certificate store is the name of a PFX (PKCS12) file containing certificates. |
| PFXBLOB | The certificate store is a string (base-64-encoded) representing a certificate store in PFX (PKCS12) format. |
| JKSFILE | The certificate store is the name of a Java key store (JKS) file containing certificates. Note: this store type is only available in Java. |
| JKSBLOB | The certificate store is a string (base-64-encoded) representing a certificate store in Java key store (JKS) format. Note: this store type is only available in Java. |
| PEMKEY_FILE | The certificate store is the name of a PEM-encoded file that contains a private key and an optional certificate. |
| PEMKEY_BLOB | The certificate store is a string (base64-encoded) that contains a private key and an optional certificate. |
| PUBLIC_KEY_FILE | The certificate store is the name of a file that contains a PEM- or DER-encoded public key certificate. |
| PUBLIC_KEY_BLOB | The certificate store is a string (base-64-encoded) that contains a PEM- or DER-encoded public key certificate. |
| SSHPUBLIC_KEY_FILE | The certificate store is the name of a file that contains an SSH-style public key. |
| SSHPUBLIC_KEY_BLOB | The certificate store is a string (base-64-encoded) that contains an SSH-style public key. |
| P7BFILE | The certificate store is the name of a PKCS7 file containing certificates. |
| PPKFILE | The certificate store is the name of a file that contains a PPK (PuTTY Private Key). |
| XMLFILE | The certificate store is the name of a file that contains a certificate in XML format. |
| XMLBLOB | The certificate store is a string that contains a certificate in XML format. |
| BCFKSFILE | The certificate store is the name of a file that contains an Bouncy Castle keystore. |
| BCFKSBLOB | The certificate store is a string (base-64-encoded) that contains a Bouncy Castle keystore. |
The password for the OAuth JWT certificate used to access a certificate store that requires a password. If the certificate store does not require a password, leave this property blank.
This property specifies the password needed to open the certificate store, but only if the store type requires one. To determine if a password is necessary, refer to the documentation or configuration for your specific certificate store.
The subject of the OAuth JWT certificate used to locate a matching certificate in the store. Supports partial matches and the wildcard '*' to select the first certificate.
The value of this property is used to locate a matching certificate in the store. The search process works as follows:
You can set the value to '*' to automatically select the first certificate in the store. The certificate subject is a comma-separated list of distinguished name fields and values. For example: CN=www.server.com, OU=test, C=US, [email protected]. Common fields include:
| Field | Meaning |
| CN | Common Name. This is commonly a host name like www.server.com. |
| O | Organization |
| OU | Organizational Unit |
| L | Locality |
| S | State |
| C | Country |
| E | Email Address |
If a field value contains a comma, enclose it in quotes. For example: "O=ACME, Inc.".
The issuer of the Java Web Token.
The issuer of the Java Web Token. Enter the value of the service account email address.
The user subject for which the application is requesting delegated access.
The user subject for which the application is requesting delegated access. Enter the email address of the user for which the application is requesting delegated access.
This section provides a complete list of the SSL properties you can configure in the connection string for this provider.
| Property | Description |
| SSLServerCert | Specifies the certificate to be accepted from the server when connecting using TLS/SSL. |
Specifies the certificate to be accepted from the server when connecting using TLS/SSL.
If using a TLS/SSL connection, this property can be used to specify the TLS/SSL certificate to be accepted from the server. Any other certificate that is not trusted by the machine is rejected.
This property can take the following forms:
| Description | Example |
| A full PEM Certificate (example shortened for brevity) | -----BEGIN CERTIFICATE----- MIIChTCCAe4CAQAwDQYJKoZIhv......Qw== -----END CERTIFICATE----- |
| A path to a local file containing the certificate | C:\cert.cer |
| The public key (example shortened for brevity) | -----BEGIN RSA PUBLIC KEY----- MIGfMA0GCSq......AQAB -----END RSA PUBLIC KEY----- |
| The MD5 Thumbprint (hex values can also be either space or colon separated) | ecadbdda5a1529c58a1e9e09828d70e4 |
| The SHA1 Thumbprint (hex values can also be either space or colon separated) | 34a929226ae0819f2ec14b4a3d904f801cbb150d |
If not specified, any certificate trusted by the machine is accepted.
Use '*' to signify to accept all certificates. Note that this is not recommended due to security concerns.
This section provides a complete list of the Firewall properties you can configure in the connection string for this provider.
| Property | Description |
| FirewallType | Specifies the protocol the provider uses to tunnel traffic through a proxy-based firewall. |
| FirewallServer | Identifies the IP address, DNS name, or host name of a proxy used to traverse a firewall and relay user queries to network resources. |
| FirewallPort | Specifies the TCP port to be used for a proxy-based firewall. |
| FirewallUser | Identifies the user ID of the account authenticating to a proxy-based firewall. |
| FirewallPassword | Specifies the password of the user account authenticating to a proxy-based firewall. |
Specifies the protocol the provider uses to tunnel traffic through a proxy-based firewall.
A proxy-based firewall (or proxy firewall) is a network security device that acts as an intermediary between user requests and the resources they access. The proxy accepts the request of an authenticated user, tunnels through the firewall, and transmits the request to the appropriate server.
Because the proxy evaluates and transfers data backets on behalf of the requesting users, the users never connect directly with the servers, only with the proxy.
Note: By default, the Sync App connects to the system proxy. To disable this behavior and connect to one of the following proxy types, set ProxyAutoDetect to false.
The following table provides port number information for each of the supported protocols.
| Protocol | Default Port | Description |
| TUNNEL | 80 | The port where the Sync App opens a connection to GoogleContacts. Traffic flows back and forth via the proxy at this location. |
| SOCKS4 | 1080 | The port where the Sync App opens a connection to GoogleContacts. SOCKS 4 then passes theFirewallUser value to the proxy, which determines whether the connection request should be granted. |
| SOCKS5 | 1080 | The port where the Sync App sends data to GoogleContacts. If the SOCKS 5 proxy requires authentication, set FirewallUser and FirewallPassword to credentials the proxy recognizes. |
To connect to HTTP proxies, use ProxyServer and ProxyPort. To authenticate to HTTP proxies, use ProxyAuthScheme, ProxyUser, and ProxyPassword.
Identifies the IP address, DNS name, or host name of a proxy used to traverse a firewall and relay user queries to network resources.
A proxy-based firewall (or proxy firewall) is a network security device that acts as an intermediary between user requests and the resources they access. The proxy accepts the request of an authenticated user, tunnels through the firewall, and transmits the request to the appropriate server.
Because the proxy evaluates and transfers data backets on behalf of the requesting users, the users never connect directly with the servers, only with the proxy.
Specifies the TCP port to be used for a proxy-based firewall.
A proxy-based firewall (or proxy firewall) is a network security device that acts as an intermediary between user requests and the resources they access. The proxy accepts the request of an authenticated user, tunnels through the firewall, and transmits the request to the appropriate server.
Because the proxy evaluates and transfers data backets on behalf of the requesting users, the users never connect directly with the servers, only with the proxy.
Identifies the user ID of the account authenticating to a proxy-based firewall.
A proxy-based firewall (or proxy firewall) is a network security device that acts as an intermediary between user requests and the resources they access. The proxy accepts the request of an authenticated user, tunnels through the firewall, and transmits the request to the appropriate server.
Because the proxy evaluates and transfers data backets on behalf of the requesting users, the users never connect directly with the servers, only with the proxy.
Specifies the password of the user account authenticating to a proxy-based firewall.
A proxy-based firewall (or proxy firewall) is a network security device that acts as an intermediary between user requests and the resources they access. The proxy accepts the request of an authenticated user, tunnels through the firewall, and transmits the request to the appropriate server.
Because the proxy evaluates and transfers data backets on behalf of the requesting users, the users never connect directly with the servers, only with the proxy.
This section provides a complete list of the Proxy properties you can configure in the connection string for this provider.
| Property | Description |
| ProxyAutoDetect | Specifies whether the provider checks your system proxy settings for existing proxy server configurations, rather than using a manually specified proxy server. |
| ProxyServer | The hostname or IP address of the proxy server that you want to route HTTP traffic through. |
| ProxyPort | The TCP port on your specified proxy server (set in the ProxyServer connection property) that has been reserved for routing HTTP traffic to and from the client. |
| ProxyAuthScheme | Specifies the authentication method the provider uses when authenticating to the proxy server specified in the ProxyServer connection property. |
| ProxyUser | The username of a user account registered with the proxy server specified in the ProxyServer connection property. |
| ProxyPassword | The password associated with the user specified in the ProxyUser connection property. |
| ProxySSLType | The SSL type to use when connecting to the proxy server specified in the ProxyServer connection property. |
| ProxyExceptions | A semicolon separated list of destination hostnames or IPs that are exempt from connecting through the proxy server set in the ProxyServer connection property. |
Specifies whether the provider checks your system proxy settings for existing proxy server configurations, rather than using a manually specified proxy server.
When this connection property is set to True, the Sync App checks your system proxy settings for existing proxy server configurations (no need to manually supply proxy server details).
This connection property takes precedence over other proxy settings. Set to False if you want to manually configure the Sync App to connect to a specific proxy server.
To connect to an HTTP proxy, see ProxyServer. For other proxies, such as SOCKS or tunneling, see FirewallType.
The hostname or IP address of the proxy server that you want to route HTTP traffic through.
The Sync App only routes HTTP traffic through the proxy server specified in this connection property when ProxyAutoDetect is set to False. If ProxyAutoDetect is set to True, which is the default, the Sync App instead routes HTTP traffic through the proxy server specified in your system proxy settings.
The TCP port on your specified proxy server (set in the ProxyServer connection property) that has been reserved for routing HTTP traffic to and from the client.
The Sync App only routes HTTP traffic through the proxy server port specified in this connection property when ProxyAutoDetect is set to False. If ProxyAutoDetect is set to True, which is the default, the Sync App instead routes HTTP traffic through the proxy server port specified in your system proxy settings.
For other proxy types, see FirewallType.
Specifies the authentication method the provider uses when authenticating to the proxy server specified in the ProxyServer connection property.
The authentication type can be one of the following:
For all values other than "NONE", you must also set the ProxyUser and ProxyPassword connection properties.
If you need to use another authentication type, such as SOCKS 5 authentication, see FirewallType.
The username of a user account registered with the proxy server specified in the ProxyServer connection property.
The ProxyUser and ProxyPassword connection properties are used to connect and authenticate against the HTTP proxy specified in ProxyServer.
After selecting one of the available authentication types in ProxyAuthScheme, set this property as follows:
| ProxyAuthScheme Value | Value to set for ProxyUser |
| BASIC | The user name of a user registered with the proxy server. |
| DIGEST | The user name of a user registered with the proxy server. |
| NEGOTIATE | The username of a Windows user who is a valid user in the domain or trusted domain that the proxy server is part of, in the format user@domain or domain\user. |
| NTLM | The username of a Windows user who is a valid user in the domain or trusted domain that the proxy server is part of, in the format user@domain or domain\user. |
| NONE | Do not set the ProxyPassword connection property. |
The Sync App only uses this username if ProxyAutoDetect is set to False. If ProxyAutoDetect is set to True, which is the default, the Sync App instead uses the username specified in your system proxy settings.
The password associated with the user specified in the ProxyUser connection property.
The ProxyUser and ProxyPassword connection properties are used to connect and authenticate against the HTTP proxy specified in ProxyServer.
After selecting one of the available authentication types in ProxyAuthScheme, set this property as follows:
| ProxyAuthScheme Value | Value to set for ProxyPassword |
| BASIC | The password associated with the proxy server user specified in ProxyUser. |
| DIGEST | The password associated with the proxy server user specified in ProxyUser. |
| NEGOTIATE | The password associated with the Windows user account specified in ProxyUser. |
| NTLM | The password associated with the Windows user account specified in ProxyUser. |
| NONE | Do not set the ProxyPassword connection property. |
For SOCKS 5 authentication or tunneling, see FirewallType.
The Sync App only uses this password if ProxyAutoDetect is set to False. If ProxyAutoDetect is set to True, which is the default, the Sync App instead uses the password specified in your system proxy settings.
The SSL type to use when connecting to the proxy server specified in the ProxyServer connection property.
This property determines when to use SSL for the connection to the HTTP proxy specified by ProxyServer. You can set this connection property to the following values :
| AUTO | Default setting. If ProxyServer is set to an HTTPS URL, the Sync App uses the TUNNEL option. If ProxyServer is set to an HTTP URL, the component uses the NEVER option. |
| ALWAYS | The connection is always SSL enabled. |
| NEVER | The connection is not SSL enabled. |
| TUNNEL | The connection is made through a tunneling proxy. The proxy server opens a connection to the remote host and traffic flows back and forth through the proxy. |
A semicolon separated list of destination hostnames or IPs that are exempt from connecting through the proxy server set in the ProxyServer connection property.
The ProxyServer is used for all addresses, except for addresses defined in this property. Use semicolons to separate entries.
Note that the Sync App uses the system proxy settings by default, without further configuration needed. If you want to explicitly configure proxy exceptions for this connection, set ProxyAutoDetect to False.
This section provides a complete list of the Logging properties you can configure in the connection string for this provider.
| Property | Description |
| LogModules | Specifies the core modules to include in the log file. Use a semicolon-separated list of module names. By default, all modules are logged. |
Specifies the core modules to include in the log file. Use a semicolon-separated list of module names. By default, all modules are logged.
This property lets you customize the log file content by specifying the logging modules to include. Logging modules categorize logged information into distinct areas, such as query execution, metadata, or SSL communication. Each module is represented by a four-character code, with some requiring a trailing space for three-letter names.
For example, EXEC logs query execution, and INFO logs general provider messages. To include multiple modules, separate their names with semicolons as follows: INFO;EXEC;SSL.
The Verbosity connection property takes precedence over the module-based filtering specified by this property. Only log entries that meet the verbosity level and belong to the specified modules are logged. Leave this property blank to include all available modules in the log file.
For a complete list of available modules and detailed guidance on configuring logging, refer to the Advanced Logging section in Logging.
This section provides a complete list of the Schema properties you can configure in the connection string for this provider.
| Property | Description |
| Location | Specifies the location of a directory containing schema files that define tables, views, and stored procedures. Depending on your service's requirements, this may be expressed as either an absolute path or a relative path. |
| BrowsableSchemas | Optional setting that restricts the schemas reported to a subset of all available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC . |
| Tables | Optional setting that restricts the tables reported to a subset of all available tables. For example, Tables=TableA,TableB,TableC . |
| Views | Optional setting that restricts the views reported to a subset of the available tables. For example, Views=ViewA,ViewB,ViewC . |
Specifies the location of a directory containing schema files that define tables, views, and stored procedures. Depending on your service's requirements, this may be expressed as either an absolute path or a relative path.
The Location property is only needed if you want to either customize definitions (for example, change a column name, ignore a column, etc.) or extend the data model with new tables, views, or stored procedures.
If left unspecified, the default location is %APPDATA%\\CData\\GoogleContacts Data Provider\\Schema, where %APPDATA% is set to the user's configuration directory:
| Platform | %APPDATA% |
| Windows | The value of the APPDATA environment variable |
| Linux | ~/.config |
Optional setting that restricts the schemas reported to a subset of all available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC .
Listing all available database schemas can take extra time, thus degrading performance. Providing a list of schemas in the connection string saves time and improves performance.
Optional setting that restricts the tables reported to a subset of all available tables. For example, Tables=TableA,TableB,TableC .
Listing all available tables from some databases can take extra time, thus degrading performance. Providing a list of tables in the connection string saves time and improves performance.
If there are lots of tables available and you already know which ones you want to work with, you can use this property to restrict your viewing to only those tables. To do this, specify the tables you want in a comma-separated list. Each table should be a valid SQL identifier with any special characters escaped using square brackets, double-quotes or backticks. For example, Tables=TableA,[TableB/WithSlash],WithCatalog.WithSchema.`TableC With Space`.
Note: If you are connecting to a data source with multiple schemas or catalogs, you must specify each table you want to view by its fully qualified name. This avoids ambiguity between tables that may exist in multiple catalogs or schemas.
Optional setting that restricts the views reported to a subset of the available tables. For example, Views=ViewA,ViewB,ViewC .
Listing all available views from some databases can take extra time, thus degrading performance. Providing a list of views in the connection string saves time and improves performance.
If there are lots of views available and you already know which ones you want to work with, you can use this property to restrict your viewing to only those views. To do this, specify the views you want in a comma-separated list. Each view should be a valid SQL identifier with any special characters escaped using square brackets, double-quotes or backticks. For example, Views=ViewA,[ViewB/WithSlash],WithCatalog.WithSchema.`ViewC With Space`.
Note: If you are connecting to a data source with multiple schemas or catalogs, you must specify each view you want to examine by its fully qualified name. This avoids ambiguity between views that may exist in multiple catalogs or schemas.
This section provides a complete list of the Miscellaneous properties you can configure in the connection string for this provider.
| Property | Description |
| AWSWorkloadIdentityConfig | Configuration properties to provide when using Workload Identity Federation via AWS. |
| MaxRows | Specifies the maximum rows returned for queries without aggregation or GROUP BY. |
| Other | Specifies additional hidden properties for specific use cases. These are not required for typical provider functionality. Use a semicolon-separated list to define multiple properties. |
| PseudoColumns | Specifies the pseudocolumns to expose as table columns. Use the format 'TableName=ColumnName;TableName=ColumnName'. The default is an empty string, which disables this property. |
| Timeout | Specifies the maximum time, in seconds, that the provider waits for a server response before throwing a timeout error. The default is 60 seconds. Set to 0 to disable the timeout. |
| UserDefinedViews | Specifies a filepath to a JSON configuration file defining custom views. The provider automatically detects and uses the views specified in this file. |
| WorkloadPoolId | The ID of your Workload Identity Federation pool. |
| WorkloadProjectId | The ID of the Google Cloud project that hosts your Workload Identity Federation pool. |
| WorkloadProviderId | The ID of your Workload Identity Federation pool provider. |
Configuration properties to provide when using Workload Identity Federation via AWS.
The properties are formatted as a semicolon-separated list of Key=Value properties, where the value is optionally quoted.
For example, this setting authenticates in AWS using a user's root keys:
AWSWorkloadIdentityConfig="AuhtScheme=AwsRootKeys;AccessKey='AKIAABCDEF123456';SecretKey=...;Region=us-east-1"
Specifies the maximum rows returned for queries without aggregation or GROUP BY.
This property sets an upper limit on the number of rows the Sync App returns for queries that do not include aggregation or GROUP BY clauses. This limit ensures that queries do not return excessively large result sets by default.
When a query includes a LIMIT clause, the value specified in the query takes precedence over the MaxRows setting. If MaxRows is set to "-1", no row limit is enforced unless a LIMIT clause is explicitly included in the query.
This property is useful for optimizing performance and preventing excessive resource consumption when executing queries that could otherwise return very large datasets.
Specifies additional hidden properties for specific use cases. These are not required for typical provider functionality. Use a semicolon-separated list to define multiple properties.
This property allows advanced users to configure hidden properties for specialized scenarios. These settings are not required for normal use cases but can address unique requirements or provide additional functionality. Multiple properties can be defined in a semicolon-separated list.
Note: It is strongly recommended to set these properties only when advised by the support team to address specific scenarios or issues.
Specify multiple properties in a semicolon-separated list.
| DefaultColumnSize | Sets the default length of string fields when the data source does not provide column length in the metadata. The default value is 2000. |
| ConvertDateTimeToGMT | Determines whether to convert date-time values to GMT, instead of the local time of the machine. |
| RecordToFile=filename | Records the underlying socket data transfer to the specified file. |
Specifies the pseudocolumns to expose as table columns. Use the format 'TableName=ColumnName;TableName=ColumnName'. The default is an empty string, which disables this property.
This property allows you to define which pseudocolumns the Sync App exposes as table columns.
To specify individual pseudocolumns, use the following format: "Table1=Column1;Table1=Column2;Table2=Column3"
To include all pseudocolumns for all tables use: "*=*"
Specifies the maximum time, in seconds, that the provider waits for a server response before throwing a timeout error. The default is 60 seconds. Set to 0 to disable the timeout.
This property controls the maximum time, in seconds, that the Sync App waits for an operation to complete before canceling it. If the timeout period expires before the operation finishes, the Sync App cancels the operation and throws an exception.
The timeout applies to each individual communication with the server rather than the entire query or operation. For example, a query could continue running beyond 60 seconds if each paging call completes within the timeout limit.
Setting this property to 0 disables the timeout, allowing operations to run indefinitely until they succeed or fail due to other conditions such as server-side timeouts, network interruptions, or resource limits on the server. Use this property cautiously to avoid long-running operations that could degrade performance or result in unresponsive behavior.
Specifies a filepath to a JSON configuration file defining custom views. The provider automatically detects and uses the views specified in this file.
This property allows you to define and manage custom views through a JSON-formatted configuration file called UserDefinedViews.json. These views are automatically recognized by the Sync App and enable you to execute custom SQL queries as if they were standard database views. The JSON file defines each view as a root element with a child element called "query", which contains the SQL query for the view. For example:
{
"MyView": {
"query": "SELECT * FROM [My Contacts] WHERE MyColumn = 'value'"
},
"MyView2": {
"query": "SELECT * FROM MyTable WHERE Id IN (1,2,3)"
}
}
You can define multiple views in a single file and specify the filepath using this property. For example: UserDefinedViews=C:\Path\To\UserDefinedViews.json. When you use this property, only the specified views are seen by the Sync App.
Refer to User Defined Views for more information.
The ID of your Workload Identity Federation pool.
The ID of your Workload Identity Federation pool.
The ID of the Google Cloud project that hosts your Workload Identity Federation pool.
The ID of the Google Cloud project that hosts your Workload Identity Federation pool.
The ID of your Workload Identity Federation pool provider.
The ID of your Workload Identity Federation pool provider.