Salesforce

Salesforce database is used to securely sync your data in systems that are part of the Salesforce ecosystem.

Configure the following details for Salesforce data source:

Register data source
Field	Description
Display name	Enter the data source name to be displayed on the screen.
Hostname	Enter the hostname.
Username	Enter the username.
Password	Enter the password.
Port is SSL enabled	Use the toggle switch to enable or disable SSL connection.
Connection details: Arrow Flight	Enter the following details for Arrow Flight service connection: Service hostname: Enter the service hostname from the following options: api.dataplatform.cloud.ibm.com api.eu-gb.dataplatform.cloud.ibm.com api.eu-de.dataplatform.cloud.ibm.com api.jp-tok.dataplatform.cloud.ibm.com. Port: Enter the port number. API key: Enter the API key. For more information, see API key. Token URL: Enter the token URL as https://iam.cloud.ibm.com/identity/token. Port is SSL enabled: Use the toggle switch to enable or disable SSL connection. Validate server certificate: This option can be used when the host certificate is not signed by a known certificate authority. Toggle the switch to enable or disable the server certificate validation. If enabled, i. The Upload SSL certificate (.pem, .crt, .cert or .cer) link is enabled. ii. Click the Upload SSL certificate (.pem, .crt, .cert or .cer) link. iii. Browse the SSL certificate and upload.
Catalog name	Enter the name of the catalog. This catalog is automatically associated with your data source.
Create	Click Create to create the data source.

Limitations for SQL statements

For data source-based catalogs the CREATE SCHEMA, CREATE TABLE, DROP SCHEMA, DROP TABLE, DELETE, DROP VIEW, ALTER TABLE, and ALTER SCHEMA statements are not available in the Data Manager UI.

When the fields of data type REAL have 6 digits or more in the decimal part with the digits being predominately zero, the values when queried are rounded off. It is observed that the rounding off occurs differently based on the precision of the values. For example, a decimal number 1.654 when rounded to 3-digits after the decimal point are the same. Another example is 10.890009 and 10.89000. It is noticed that 10.89000 is rounded to 10.89, whereas 10.89009 is not rounded off. This is an inherent issue because of the representational limitations of binary floating point formats. This might have a significant impact when querying involves sorting.