SCA Configuration - Connect additional Datasource

SecContacts.ServiceUrls

This setting is for adding service urls of custom dataverse datasources e.g. Dynamics 365.

• Name: SecContacts.ServiceUrls

• Value: [{"name":"<service ID>", "value":"<service URL>"}]

The Value property is a JSON Array of name value pairs. You can add one or multiple service urls here.

Replace <service ID> with the service ID of a customs datasource

• e.g. D365 or DVRS

Replace <service URL> with the url of a customs datasource

• e.g. https://provectus-lab.crm.dynamics.com

Currently "Dynamics 365" (D365) as well as "Dataverse" (DVRS) 'SCA default Table 'sca_contact_tables' is supported.

Optional properties for SecContacts.ServiceUrls in SCA 3.0

• Name: SecContacts.ServiceUrls

• Value: [{"name":"<service ID>", "value":"<service URL>", "apiFilter":"<ODATA filter expression>", "ccHomePhone":"<cust.column.HomePhone>", "ccBusinessPhone":"<cust.column.BusinessPhone>", "ccMobilePhone":"<cust.column.ccMobilePhone>", "ccPrivateMobilePhone":"<cust.column.PrivateMobilePhone>", "ccEMailAddress":"<cust.column.EMailAddress>" }]

The Value is a JSON array containing one or more ServiceUrls. Each object in the array must include the mandatory fields:

Replace <service ID> with the service ID of a customs datasource

• e.g. D365 or DVRS

Replace <service URL> with the url of a customs datasource

• e.g. https://provectus-lab.crm.dynamics.com

You may also optionally include:

• apiFilter: Define an OData filter expression for the filter parameter used in Microsoft D365 / dataverse API queries. This allows you to limit which records are returned based on specific field values. When used in combination with multiple Service URLs, this enables you to partition your D365 or dataverse environment into multiple distinct SCA data sources - for example, based on region, team, or data ownership. e.g. "statecode eq 0 and contains(name, 'Project')"

• ccHomePhone: Replace <cust.column.HomePhone> with the name of a custom column that holds the home phone number of an D365 contact object

• ccBusinessPhone: Replace <cust.column.BusinessPhone> with the name of a custom column that holds the business phone number of an D365 contact object

• ccMobilePhone: Replace <cust.column.MobilePhone> with the name of a custom column that holds the mobile phone number of an D365 contact object

• ccPrivateMobilePhone: Replace <cust.column.PrivateMobilePhone> with the name of a custom column that holds the private mobile phone number of an D365 contact object

• ccEMailAddress: Replace <cust.column.EMailAddress> with the name of a custom column that holds the email address of an D365 contact object

You can add one or multiple ServiceURLs to this array as needed.

SecContacts.AzureBlobStorage

This setting is for defining an AZURE Blob Storage as optional datasource for contacts.

With Azure Blob Storage in combination with the Provectus Azure Blob Storage Connector (link here) you can easily get contacts from any onPrem Application into the Secure Contacts App as long as the onPrem Application can export it's contacts into an *.csv or *.json file.

• Name: SecContacts.AzureBlobStorage

• Value: [{"name":"<abs name>", "value":"<abs access key>"}]

The Value property is a JSON Array of name value pairs. You can add one or multiple azure blob storages here.

Replace <abs name> with the unique name to identify the Azure Blob Storage

• e.g. ABS1

Replace <abs access key> with the access key for a particular Azure Blob Storage. The access key needs to be generate for each Azure Blob Storage individually via the Provectus Azure Blob Storage Connector.

• e.g. Xt8TVki4+ndWtqSVTAXTNr(...)0UFWNuDo2du3wZ5w92a7w==

SecContacts.SharedMailboxContacts

This setting is for defining exchange online shared mailboxes as optional datasource for contacts.

• Name: SecContacts.SharedMailboxContacts

• Value: [{"name":"<smc_name>", "value":"<smc_emailaddress>"}]

The Value property is a JSON Array of name value pairs. You can add one or multiple shared mailbox email addresses here.

Replace <smc_name> with the unique name to identify the shared mailbox

• e.g. SCM1

Replace <smc_emailaddress> with the email address of a shared mailbox.

• e.g. [email protected]

If the SCA user is member of the shared mailbox configured here, then contacts stored in that shared mailbox will become available in SCA.

If the SCA user is NOT member of the shared mailbox configured here, then this setting is ignored by SCA and the user will not see any contacts stored in that shared mailbox.