Connections > QuickBooks V2 Connection Properties
  

QuickBooks V2 Connection Properties

When you set up a QuickBooks V2 connection, you must configure the connection properties.
The following table describes the QuickBooks V2 connection properties:
Connection Property
Description
Connection Name
Name of the connection.
Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -,
Maximum length is 255 characters.
Description
Description of the connection. Maximum length is 4000 characters.
Use Secret Vault
Stores sensitive credentials for this connection in the secrets manager that is configured for your organization.
This property appears only if secrets manager is set up for your organization.
This property is not supported by Data Ingestion and Replication and the Data Access Management services.
When you enable the secret vault in the connection, you can select which credentials that the Secure Agent retrieves from the secrets manager. If you don't enable this option, the credentials are stored in the repository or on a local Secure Agent, depending on how your organization is configured.
Note: If you’re using this connection to apply data access policies through pushdown or proxy services, you cannot use the Secret Vault configuration option.
For information about how to configure and use a secrets manager, see Secrets manager configuration.
Runtime Environment
The name of the runtime environment where you want to run the tasks.
Select a Secure Agent or elastic runtime environment.
For more information about how to configure and use the runtime environments, see Runtime environments.
Username
Username of the QuickBooks account.
Password
Password of the QuickBooks account.
Connection URL
The Connection URL to connect to the QuickBooks application.
Schema
The value of Schema is set to default automatically.
QBXML version
QBXML version of the QuickBooks. The default QBXML version is 6.0.
Enable Logging
Enable logging to see the session logs of tasks.