MYOB

Building the JDBC URL

After installing the license, open the connection management page by running java -jar kingswaysoft.jdbc.jar. Enter the required details to generate the JDBC connection URL. Click Test Connection to test the generated URL, or Copy to Clipboard to copy the connection string for use in your application.

Note: If the license is not installed, you can still use the connection manager to generate a JDBC URL; however, the Test Connection feature will be disabled.

General Page

The General page allows you to specify connection properties and login credentials for the MYOB REST service:

connectionmanage

General Settings

Product

Select one of the following MYOB products:

AccountRight provides access to AccountRight company files.
MYOB Business provides access to MYOB Business.

Endpoint or Region

For AccountRight, select Cloud or Local. For MYOB Business, select the AU or NZ region.

Base URL

The driver populates this value according to the selected product and endpoint. You can edit it when a custom or locally hosted endpoint is required.

AccountRight Cloud: https://api.myob.com/accountright
MYOB Business AU: https://api.myob.com/au/essentials/businesses
MYOB Business NZ: https://api.myob.com/nz/essentials/businesses

API Throttle Rate

Limits the number of requests sent per minute. The connection manager default is 20 requests per minute. Set this value to 0 to disable throttling.

Authentication and Product Settings

AccountRight Cloud

AccountRight Cloud uses OAuth Authorization Code authentication.

Use Generate Token File to complete the OAuth flow, save the token file, and provide its path and password in the connection manager.

Select a value in Company Files after the OAuth settings have been configured. The selected company file is used as the AccountRight company endpoint.

Path To Token File

The path to the token file on the file system.

Token File Password

The Password for the token file.

Generate Token File

This button completes the OAuth authentication process to generate a new token.

Client ID: The Client ID option allows you to specify the unique ID which identifies the application making the request.
Client Secret: The Client Secret option allows you to specify the client secret belonging to your app.
Redirect URL: The Redirect URL option allows you to specify the Redirect URL to complete the authentication process.
Scope: The Scope option allows you to specify the scope of the token file being generated.

AccountRight Local

AccountRight Local uses the local endpoint and MYOB credentials. Provide the User Name and Password displayed by the local AccountRight service. OAuth and Company Files are not used for this mode.

User Name: The user name of the account being used to authenticate with MYOB.
Password: The password of the account being used to authenticate with MYOB.

MYOB Business

MYOB Business uses OAuth Authorization Code authentication.

Select the appropriate region and choose a value from the Businesses list after authentication.

Path To Token File

The path to the token file on the file system.

Token File Password

The Password for the token file.

Generate Token File

This button completes the OAuth authentication process to generate a new token.

Client ID: The Client ID option allows you to specify the unique ID which identifies the application making the request.
Client Secret: The Client Secret option allows you to specify the client secret belonging to your app.
Redirect URL: The Redirect URL option allows you to specify the Redirect URL to complete the authentication process.
Scope: The Scope option allows you to specify the scope of the token file being generated.

Test Connection

After completing the required product, endpoint or region, authentication, and company or business settings, click Test Connection to validate the configuration and verify that MYOB requests authenticate successfully.

Advanced Settings Page

The Advanced Settings page allows you to specify advanced settings for the connection.

connectionmanage

Proxy Server Settings

Proxy Server Settings

Proxy Mode

The Proxy Mode option allows you to specify how you want to configure the proxy server setting. There are three options available.

No Proxy
Auto-detect (Use system configured proxy)
Manual

Proxy Server

Using the Proxy Server option allows you to specify the name of the proxy server for the connection.

Port

The Port option allows you to specify the port number of the proxy server for the connection.

Username (Proxy Server Authentication)

The Username option (under Proxy Server Authentication) allows you to specify the proxy user account.

Password (Proxy Server Authentication)

The Password option (under Proxy Server Authentication) allows you to specify the proxy user's password.

Miscellaneous Settings

Miscellaneous Settings

Timeout (secs)

The Timeout (secs) option allows you to specify a timeout value in seconds for the connection. The default value is 120 seconds. Specify 0 for infinite timeout.

Retry on Intermittent Errors

The retry on intermittent errors determines if requests will be retried when there is an error. If this option is checked, requests will be retried up to 3 times.

Ignore Certificate Errors

This option can be used to ignore those SSL certificate errors when connecting to the target server.

Warning: Enabling the "Ignore Certificate Errors" option is generally NOT recommended, particularly for production instances. Unless there is a strong reason to believe the connection is secure - such as the network communication is only happening in an internal infrastructure, this option should be unchecked for best security.

Note: When this option is enabled, it applies to all HTTP-based SSL connections in the same job process.

Concurrent Writing Threads

This option can be used to set the number of threads to be used during write operations. This can improve performance during large-volume write operations.

Using the JDBC Driver

This section provides examples that use JDBC classes such as Connection, Statement, PreparedStatement, and ResultSet to interact with MYOB data. It covers regular statements and prepared statements for complex or frequently executed queries.

Executing Statements

After you have connected from your code, you can execute SQL statements using the Statement class. For connection details, see Connecting with DriverManager or Connecting with DataSource. For parameterized statements, see Executing Prepared Statements.

SELECT

Use the Statement class's generic execute method or the executeQuery method to execute SQL statements that return data. To retrieve the results of a query, call the getResultSet method of the Statement.

String sql = "SELECT UID, FirstName, LastName, IsActive FROM Contact WHERE IsActive = true";
try (ResultSet resultSet = statement.executeQuery(sql)) {
    LOGGER.info(resultSet.toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

The MYOB driver also supports string filters, pattern matching, ordering, and driver options embedded in SQL.

Some examples can be seen below:

#Reading with a filter on FirstName
SELECT UID, FirstName, LastName FROM Contact WHERE FirstName = 'Geovany'

#Filtering FirstName for entities that start with'Geo'SELECT UID, FirstName, LastName FROM Contact WHERE FirstName LIKE'Geo%'

#Ordering results
SELECT UID, FirstName, LastName FROM Contact ORDERBY FirstName ASC

#Filtering results where IsActive istrueandTypeis'Customer'
#Results ordered by FirstName (ascending)
#Query-levelconnection property override toset the BatchSizeForReading to 1 for this query.
SELECT UID, FirstName, LastName FROM Contact WHERE IsActive = trueANDType = 'Customer'ORDERBY FirstName ASC USING OPTIONS (batchsize = 1)

INSERT

Use either the generic execute method or the executeUpdate method of the Statement class to execute an INSERT operation.

The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the inserted data's ID, exceptions raised during execution, and details of the affected data.

String sql = "INSERT INTO GeneralLedger/Category "
           + "(Name, Description, IsActive, DisplayID) VALUES "
           + "('JDBC_TEST', 'JDBC write test', true, 'DTEST001')";
try {
    statement.executeUpdate(sql);
    try (ResultSet resultSet = statement.getResultSet()) {
        LOGGER.info(resultSet.toString());
    }
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

id,errorcode,errormessage,processdata,haserrors
e5a9ad99-1446-4cb1-891f-deece2b44756,null,null,{"Name":"JDBC_TEST","Description":"JDBC write test","IsActive":true,"DisplayID":"DTEST001"},false

UPDATE

Use either the generic execute method or the executeUpdate method of the Statement class to execute an UPDATE operation.

The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the updated data's ID, exceptions raised during execution, and details of the affected data.

String sql = "UPDATE GeneralLedger/Category "
           + "SET Description = 'JDBC update test', Name = 'test name' "
           + "WHERE UID = 'YOUR_CATEGORY_UID'";
try {
    statement.executeUpdate(sql);
    LOGGER.info(statement.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

id,errorcode,errormessage,processdata,haserrors
e5a9ad99-1446-4cb1-891f-deece2b44756,null,null,{"Description":"JDBC update test","Name":"test name","RowVersion":"4330219837809754112","UID":"e5a9ad99-1446-4cb1-891f-deece2b44756","DisplayID":"DTEST001","IsActive":true,"URI":"https://arl2.api.myob.com/accountright/5e30b8a0-6e33-483f-a531-76965f10597c/GeneralLedger/Category/e5a9ad99-1446-4cb1-891f-deece2b44756"},false

DELETE

Use either the generic execute method or the executeUpdate method of the Statement class to execute a DELETE operation.

The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the deleted data's ID, exceptions raised during execution, and details of the affected data.

String sql = "DELETE FROM GeneralLedger/Category WHERE UID = 'YOUR_CATEGORY_UID'";
try {
    statement.executeUpdate(sql);
    LOGGER.info(statement.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

id,errorcode,errormessage,processdata,haserrors
null,null,null,null,false

Executing Prepared Statements

Using a PreparedStatement can improve performance when you need to execute a SQL statement multiple times with different parameters. Unlike a Statement object, a PreparedStatement object is provided with a SQL statement when it is created, which can then be executed with different values each time. This special type of statement is derived from the more general Statement class.

Below are the steps outlining how to execute a prepared statement:

Creating and Executing a Prepared Statement

Create a PreparedStatement

Use the prepareStatement method of the Connection class to instantiate a PreparedStatement.

For connection details, see Connecting with DriverManager or Connecting with DataSource.

Set Parameters

Declare parameters by calling the corresponding setter method of the PreparedStatement.
NOTE: The parameter indices start at 1.

Execute the PreparedStatement

Use the generic execute or executeUpdate method of the PreparedStatement.

Retrieve Results

Call the getResultSet method of the PreparedStatement to obtain the query results, which are returned as a ResultSet.

Iterate Over the Result Set

Use the next method of the ResultSet to iterate through the results. To obtain column information, use the ResultSetMetaData class. Instantiate a ResultSetMetaData object by calling the getMetaData method of the ResultSet.

SELECT

Use the PreparedStatement class's generic execute method or the executeQuery method to execute SQL statements that return data.

The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the retrieved data.

String sql = "SELECT UID, FirstName, LastName FROM Contact WHERE FirstName = ?";
try (PreparedStatement ps = connection.prepareStatement(sql)) {
    ps.setString(1, "Geovany");
    try (ResultSet resultSet = ps.executeQuery()) {
       LOGGER.info(resultSet.toString());
    }
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

INSERT

Use either the generic execute method or the executeUpdate method of the PreparedStatement class to execute an INSERT operation.

The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the ID of inserted data, exceptions raised during execution, and the data affected by the insertion.

String sql = "INSERT INTO GeneralLedger/Category "
           + "(Name, Description, IsActive, DisplayID) VALUES (?, ?, ?, ?)";
try (PreparedStatement ps = connection.prepareStatement(sql)) {
    ps.setString(1, "JDBC Category");
    ps.setString(2, "JDBC test");
    ps.setBoolean(3, true);
    ps.setString(4, "DTEST001");
    ps.executeUpdate();
    LOGGER.info(ps.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

id,errorcode,errormessage,processdata,haserrors
1c0d7a5f-e33d-4689-962c-723d8fca0aaa,null,null,{"Name":"JDBC Category","Description":"JDBC test","IsActive":true,"DisplayID":"DTEST001"},false

UPDATE

Use either the generic execute method or the executeUpdate method of the PreparedStatement class to execute an UPDATE operation.

The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the ID of updated data, exceptions raised during execution, and the data affected by the update.

String sql = "UPDATE GeneralLedger/Category SET Description = ? WHERE UID = ?";
try (PreparedStatement ps = connection.prepareStatement(sql)) {
    ps.setString(1, "JDBC prepared update test");
    ps.setString(2, "YOUR_CATEGORY_UID");
    ps.executeUpdate();
    LOGGER.info(ps.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

id,errorcode,errormessage,processdata,haserrors
1c0d7a5f-e33d-4689-962c-723d8fca0aaa,null,null,{"Description":"JDBC prepared update test","RowVersion":"5266968560302817280","UID":"1c0d7a5f-e33d-4689-962c-723d8fca0aaa","DisplayID":"DTEST001","Name":"JDBC Category","IsActive":true,"URI":"https://arl2.api.myob.com/accountright/5e30b8a0-6e33-483f-a531-76965f10597c/GeneralLedger/Category/1c0d7a5f-e33d-4689-962c-723d8fca0aaa"},false

DELETE

Use either the generic execute method or the executeUpdate method of the PreparedStatement class to execute a DELETE operation.

String sql = "DELETE FROM GeneralLedger/Category WHERE UID = ?";
try (PreparedStatement ps = connection.prepareStatement(sql)) {
    ps.setString(1, "YOUR_CATEGORY_UID");
    ps.executeUpdate();
    LOGGER.info(ps.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

id,errorcode,errormessage,processdata,haserrors
null,null,null,null,false

Metadata Discovery

This section provides examples on how to retrieve table and column metadata using the getTables, getColumns, and getPrimaryKeys methods from the DatabaseMetaData interface. These are essential for discovering database structures.

Tables

The getTables method from the DatabaseMetaData interface can be used to retrieve a list of tables.

This method only retrieves tables that are not write-only.

To get a list of tables that includes write-only tables, query the table system.tables.

try (ResultSet resultSet = connection.getMetaData().getTables(null, null, null, null)) {
    while (resultSet.next()) {
        LOGGER.info(resultSet.getString("TABLE_NAME"));
    }
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

TABLE_CAT,TABLE_SCHEM,TABLE_NAME,TABLE_TYPE,REMARKS,TYPE_CAT,TYPE_SCHEM,TYPE_NAME,SELF_REFERENCING_COL_NAME,REF_GENERATION
null,null,Banking/BankAccount,TABLE,null,null,null,null,null,null
null,null,Banking/ReceiveMoneyTxn,TABLE,null,null,null,null,null,null
null,null,Banking/SpendMoneyTxn,TABLE,null,null,null,null,null,null
null,null,Banking/Statement,TABLE,null,null,null,null,null,null
null,null,Banking/TransferMoneyTxn,TABLE,null,null,null,null,null,null
null,null,Company,TABLE,null,null,null,null,null,null
null,null,Company/FormTemplate,TABLE,null,null,null,null,null,null
null,null,Company/Preferences,TABLE,null,null,null,null,null,null
null,null,Contact,TABLE,null,null,null,null,null,null
null,null,Contact/Customer,TABLE,null,null,null,null,null,null
null,null,Contact/Employee,TABLE,null,null,null,null,null,null
null,null,Contact/EmployeePaymentDetails,TABLE,null,null,null,null,null,null
null,null,Contact/EmployeePayrollDetails,TABLE,null,null,null,null,null,null
null,null,Contact/EmployeeStandardPay,TABLE,null,null,null,null,null,null
null,null,Contact/Personal,TABLE,null,null,null,null,null,null
null,null,Contact/Supplier,TABLE,null,null,null,null,null,null
......

The getTables method returns the following metadata columns:

Column Name	Data Type	Description
TABLE_CAT	String	The catalog that contains the table.
TABLE_SCHEM	String	The schema of the table.
TABLE_NAME	String	The name of the table.
TABLE_TYPE	String	The type of the table (e.g., TABLE or VIEW).
REMARKS	String	An optional description of the table.

Columns

Use the getColumns method of the DatabaseMetaData interface to retrieve detailed information about database columns.

This method returns columns only for tables that are not write-only.

To get columns for write-only tables, query the table system.columns.

try (ResultSet resultSet = connection.getMetaData().getColumns(null, null, "Contact", null)) {
    while (resultSet.next()) {
        LOGGER.info(resultSet.getString("COLUMN_NAME"));
    }
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

TABLE_CAT,TABLE_SCHEM,TABLE_NAME,COLUMN_NAME,DATA_TYPE,TYPE_NAME,COLUMN_SIZE,BUFFER_LENGTH,DECIMAL_DIGITS,NUM_PREC_RADIX,NULLABLE,REMARKS,COLUMN_DEF,SQL_DATA_TYPE,SQL_DATETIME_SUB,CHAR_OCTET_LENGTH,ORDINAL_POSITION,IS_NULLABLE,SCOPE_CATALOG,SCOPE_SCHEMA,SCOPE_TABLE,SOURCE_DATA_TYPE,IS_AUTOINCREMENT,IS_GENERATEDCOLUMN,DTS_TYPE
null,null,Contact,Addresses,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR
null,null,Contact,CompanyName,12,VARCHAR,255,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR
null,null,Contact,Created,93,TIMESTAMP,null,null,0,0,null,null,null,93,null,null,null,null,null,null,null,null,null,null,DT_DBTIMESTAMP
null,null,Contact,CurrentBalance,3,DECIMAL,null,null,0,0,null,null,null,3,null,null,null,null,null,null,null,null,null,null,DT_DECIMAL
null,null,Contact,CustomField1.Label,12,VARCHAR,255,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR
null,null,Contact,CustomField1.Value,12,VARCHAR,255,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR
null,null,Contact,CustomField2.Label,12,VARCHAR,255,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR
null,null,Contact,CustomField2.Value,12,VARCHAR,255,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR
null,null,Contact,CustomField3.Label,12,VARCHAR,255,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR
null,null,Contact,CustomField3.Value,12,VARCHAR,255,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR
null,null,Contact,CustomList1.Label,12,VARCHAR,255,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR
null,null,Contact,CustomList1.Value,12,VARCHAR,255,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR
null,null,Contact,CustomList2.Label,12,VARCHAR,255,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR
null,null,Contact,CustomList2.Value,12,VARCHAR,255,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR

The getColumns method returns the following columns:

Column Name	Data Type	Description
TABLE_CAT	String	The database name.
TABLE_SCHEM	String	The table schema.
TABLE_NAME	String	The table name.
COLUMN_NAME	String	The column name.
DATA_TYPE	Integer	The data type represented by a constant value from java.sql.Types.
TYPE_NAME	String	The data type name used by the driver.
COLUMN_SIZE	Integer	The length in characters of the column or the numeric precision.
BUFFER_LENGTH	Integer	The buffer length.
DECIMAL_DIGITS	Integer	The column scale or number of digits to the right of the decimal point.
NUM_PREC_RADIX	Integer	The radix, or base.
NULLABLE	Integer	Whether the column can contain null as defined by the following JDBC DatabaseMetaData constants: columnNoNulls (0) or columnNullable (1).
REMARKS	String	The comment or note associated with the object.
COLUMN_DEF	String	The default value for the column.
SQL_DATA_TYPE	Integer	Reserved by the specification.
SQL_DATETIME_SUB	Integer	Reserved by the specification.
CHAR_OCTET_LENGTH	Integer	The maximum length of binary and character-based columns.
ORDINAL_POSITION	Integer	The position of the column in the table, starting at 1.
IS_NULLABLE	String	Whether a null value is allowed: YES or NO.
SCOPE_CATALOG	String	The catalog of the table referenced by a reference attribute (null if `DATA_TYPE` is not `REF`).
SCOPE_SCHEMA	String	The schema of the table referenced by a reference attribute (null if `DATA_TYPE` is not `REF`).
SCOPE_TABLE	String	The name of the table referenced by a reference attribute (null if `DATA_TYPE` is not `REF`).
SOURCE_DATA_TYPE	Short	The source type of a distinct type or user-defined `REF` type (null if `DATA_TYPE` is neither `DISTINCT` nor a user-defined `REF`).
IS_AUTOINCREMENT	String	Whether the column value is assigned by MYOB in fixed increments.
IS_GENERATEDCOLUMN	String	Whether the column is generated: YES or NO.
DTS_TYPE	String	Object DTS attribute type.

Primary Keys

The getPrimaryKeys method in the DatabaseMetaData interface is used to retrieve metadata about primary keys for a given table in MYOB.

try (ResultSet resultSet = connection.getMetaData().getPrimaryKeys(null, null, "Contact")) {
    while (resultSet.next()) {
        LOGGER.info(resultSet.getString("COLUMN_NAME"));
    }
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

TABLE_CAT,TABLE_SCHEM,TABLE_NAME,COLUMN_NAME,KEY_SEQ,PK_NAME
null,null,Contact,UID,1,null

The getPrimaryKeys method returns the following columns:

Column Name	Data Type	Description
TABLE_CAT	String	The catalog name.
TABLE_SCHEM	String	The schema name.
TABLE_NAME	String	The name of the table that contains the primary key.
COLUMN_NAME	String	The name of the column that serves as the primary key for the table.
KEY_SEQ	Short	The sequence number within the primary key.
PK_NAME	String	The primary key name.

Connection Settings

Connection Setting	Type	Default Value	Description
ApiThrottleRate	Integer	20	The maximum number of API requests a client can make to the server within a specific time period, defined in requests per minute. Set to 0 to disable request throttling.
AuthenticationMode	String	AuthorizationCode	AuthenticationMode specifies the method used to authenticate when connecting to MYOB. AccountRight Local uses Basic authentication.
BaseUrl	String	""	The base URL to be used when constructing the request. The connection manager supplies the default URL for the selected product and endpoint or region.
BatchSizeForReading	Integer	400	BatchSizeForReading is used to set how many records can be read from MYOB in a single call.
BatchSizeForWriting	Integer	1	BatchSizeForWriting is used to set how many records can be written to MYOB in a single call.
CacheExpirationTime	Integer	30	Defines the expiration time for cache. A value of 0 disables caching.
Company	String	""	Selected AccountRight company file.
ConcurrentWritingThreads	Integer	1	The number of threads for executing operations in parallel. A value of 0 will disable multi threading.	ConnectionTimeout	Integer	30	ConnectionTimeout is the maximum amount of time the program will wait to set up a connection to MYOB.
ContinueOnErrors	Boolean	false	Determines if the program continues executing SQL statements after encountering an error.
IgnoreCertificateErrors	Boolean	false	Specifies whether to verify the certificate when connecting to MYOB. If certificate verification is not required, you can set this value to 'true'.
LogFileSize	String	"10485760"	A string specifying the maximum size in bytes for a log file.
LogLevel	String	"INFO"	The logging level for the JDBC driver.
LogPath	String	"./jdbcLogs"	The directory where log files are stored.
OemKey	String	""	The OEM license key.
Password	String	""	Password for AccountRight Local authentication.
PathToTokenFile	String	""	The TokenPath specifies the file path where the token used for connecting to MYOB is located.
ProxyMode	String	NoProxy	This setting configures the proxy. Allowed values are "NoProxy", "AutoDetect" and "Manual".
ProxyPassword	String	""	The password to be used to authenticate to the proxy.
ProxyServer	String	""	The host of the proxy server.
ProxyServerPort	Integer	0	The port of the proxy server.
ProxyUsername	String	""	The username to be used to authenticate to the proxy.
ResultPath	String	""	The path where the execution result files are saved.
RetryOnIntermittentErrors	Boolean	true	The RetryOnIntermittentErrors parameter indicates whether to retry the connection when it might occasionally fail due to temporary issues.
SageBusiness	String	""	Selected MYOB Business.
ServiceEndpoint	String	""	AccountRight endpoint (`Cloud` or `Local`) or MYOB Business region (`AU` or `NZ`).
ServiceName	String	""	The ServiceName refers to the name of the service API selected by the user.
ServiceTimeout	Integer	120	The ServiceTimeout is the timeout to receive the full response from the MYOB API.
Suppress404NotFoundError	Boolean	true	When set to true, if a query results in an HTTP 404 error, a result set will still be created. When set to false, an error is logged instead and no result set is created.
TokenPassword	String	""	The password used to read the token file.
UserName	String	""	User name for AccountRight Local authentication.

MYOB JDBC Driver

Documentation for MYOB drivers found within JDBC Driver Pack

MYOB

Building the JDBC URL

General Page

Authentication and Product Settings

Advanced Settings Page

Using the JDBC Driver

Executing Statements

SELECT

INSERT

UPDATE

DELETE

Executing Prepared Statements

SELECT

INSERT

UPDATE

DELETE

Metadata Discovery

Tables

Columns

Primary Keys

Connection Settings