XML response aggregate returned from QuickBooks.

This field contains one XML response aggregate returned from QuickBooks after a successful call to Search.

This field may be used to set the Aggregate field of any other component. If this is done the component will be set to the record specified in ResultAggregate.

The Ids are also provided separately in the ResultId field.

Id of the result aggregate stored in Aggregate.

The ResultIds will automatically be prefixed with a hash, and may be passed as is to the Get method of any component, or used as references.

The corresponding XML response aggregate is provided in the Aggregate field

Name of the result aggregate stored in Aggregate.

The ResultName will only be returned for Entity searches, and may be passed as is to the GetByName method of any component that supports such functionality. (Customer, Account, Item, Vendor, Employee, etc).

The corresponding XML response aggregate is provided in the Aggregate field

An account name to search for in a transaction. Limits the search to transactions associated with the account specified by AccountId.

Only applicable to searches for transaction objects and BillToPay queries.

An account name to search for in a transaction. Limits the search to transactions associated with the account specified by AccountName. For example, if searching for a CCCredit AccountName would be the full name of a credit card.

Only applicable to searches for transaction objects and BillToPay queries.

Search by the type of QuickBooks account.

Only applicable to account queries.

Limits the search to active or inactive records only. May be used to limit the search to active or inactive records only.

The following values are permitted:

Only applicable to searches for entity objects.

Limits the search to transactions associated with the entity specified by EntityId. Note that you may use EntityName OR EntityId to search, but you may not use both.

Only applicable to searches for transaction objects, with the following exceptions: BillToPay queries map this to the PayeeEntityId field, and ItemAssembliesCanBuild queries map this to the ItemInventoryAssemblyId field.

An entity name to search for in a transaction. Limits the search to transactions associated with the entity specified by EntityName. For example, if searching for an Invoice EntityName would be the full name of a Customer.

Only applicable to searches for transaction objects, with the following exceptions: BillToPay queries map this to the PayeeEntityName field, and ItemAssembliesCanBuild queries map this to the ItemInventoryAssemblyName field.

The type of item to search for. Applies only to searches for items. If set to itAll (the default) the component will search for all types of items.

Latest modified date to search for. Limits the search to records modified on or before this date.

This is also used as the Deleted date range filter for qtListDeletedQuery and qtTxnDeletedQuery query types.

The standard formatting for dates is YYYY-MM-DD; i.e., September 2, 2002 is formatted as 2002-09-02. When getting the value of a date property, the date will always be in this format.

When setting the value of a date property, the formats MM-DD-YY, MM-DD-YYYY, MM/DD/YY, and MM/DD/YYYY are also acceptable. Dates in these formats will be automatically parsed and stored in YYYY-MM-DD format.

This field may also be set using the DateTime format. This format for specifying date and time is"CCCC-MM-DDThh:mm:ss+hh:mm" or "CCCC-MM-DDThh:mm:ss-hh:mm" where CCCC is the four-digit year, MM is the month, DD is the day, the character T is a separator, hh is the hour, mm is the minute, ss is the second, and hh:mm is the difference between the local time of the client and UTC (Universal Coordinated Time). For example, "2011-01-19T15:43:21-05:00" is January first, 2011 3:43:21 PM, Eastern Standard Time. The timezone differential is optional, if omitted Quickbooks will use the System's time zone.

Earliest modified date to search for. Limits the search to records modified on or after this date.

This is also used as the Deleted date range filter for qtListDeletedQuery and qtTxnDeletedQuery query types.

The standard formatting for dates is YYYY-MM-DD; i.e., September 2, 2002 is formatted as 2002-09-02. When getting the value of a date property, the date will always be in this format.

When setting the value of a date property, the formats MM-DD-YY, MM-DD-YYYY, MM/DD/YY, and MM/DD/YYYY are also acceptable. Dates in these formats will be automatically parsed and stored in YYYY-MM-DD format.

This field may also be set using the DateTime format. This format for specifying date and time is"CCCC-MM-DDThh:mm:ss+hh:mm" or "CCCC-MM-DDThh:mm:ss-hh:mm" where CCCC is the four-digit year, MM is the month, DD is the day, the character T is a separator, hh is the hour, mm is the minute, ss is the second, and hh:mm is the difference between the local time of the client and UTC (Universal Coordinated Time). For example, "2011-01-19T15:43:21-05:00" is January first, 2011 3:43:21 PM, Eastern Standard Time. The timezone differential is optional, if omitted Quickbooks will use the System's time zone.

String which names are to contain. Limits the search to records with names which contain the string NameContains.

If NameContains is specified none of the other Name properties may be specified.

Only applicable to searches for entity objects.

String which names are to end with. Limits the search to records with names which end with the string specified by NameEndsWith.

If NameEndsWith is specified none of the other Name properties may be specified.

Only applicable to searches for entity objects.

Ending point of a name range. Limits the search to records with names lexicographically lower than or equal to NameRangeEnd.

May be combined with NameRangeStart, but not with NameContains, NameStartsWith, or NameEndsWith.

Only applicable to searches for entity objects.

Starting point of a name range. Limits the search to records with names lexicographically higher than or equal to NameRangeStart.

May be combined with NameRangeEnd, but not with NameContains, NameStartsWith, or NameEndsWith.

Only applicable to searches for entity objects.

String which names are to start with. Limits the search to records with names which start with the string specified by NameStartsWith.

If NameStartsWith is specified none of the other Name properties may be specified.

Only applicable to searches for entity objects.

Limits the search to paid or unpaid transactions only. May be used to limit the search to paid or unpaid records only.

The following values are permitted:

Only applicable to searches for Bill or Invoice transaction objects.

Exact RefNumber to search for. Limits the search to records with RefNumbers identical to RefNumber.

If RefNumber is specified, no other search criteria will be sent in the query. If you wish to narrow your results based on the RefNumber and other criteria such as ModifiedDateStart or EntityName, you will need to use the RefNumberContains, RefNumberStartsWith, RefNumberEndsWith, RefNumberRangeStart, or RefNumberRangeEnd properties.

Only applicable to searches for transaction objects.

String which RefNumbers are to contain. Limits the search to records with RefNumbers which contain the string RefNumberContains.

If RefNumberContains is specified none of the other RefNumber properties may be specified.

Only applicable to searches for transaction objects.

String which RefNumbers are to end with. Limits the search to records with RefNumbers which end with the string specified by RefNumberEndsWith.

If RefNumberEndsWith is specified none of the other RefNumber properties may be specified.

Only applicable to searches for transaction objects.

Ending point of a RefNumber range. Limits the search to records with RefNumbers lexicographically lower than or equal to RefNumberRangeEnd.

May be combined with RefNumberRangeStart, but not with RefNumberContains, RefNumberStartsWith, or RefNumberEndsWith.

Only applicable to searches for transaction objects.

Starting point of a RefNumber range. Limits the search to records with RefNumbers lexicographically higher than or equal to RefNumberRangeStart.

May be combined with RefNumberRangeEnd, but not with RefNumberContains, RefNumberStartsWith, or RefNumberEndsWith.

Only applicable to searches for transaction objects.

String which RefNumbers are to start with. Limits the search to records with RefNumbers which start with the string specified by RefNumberStartsWith.

If RefNumberStartsWith is specified none of the other RefNumber properties may be specified.

Only applicable to searches for transaction objects.

A maximum balance which returned records should have. Limits the search to records with balances less than or equal to TotalBalanceMaximum.

If TotalBalanceMaximum is specified TotalBalanceMinimum may not be (this limitation is imposed by the QBXML interface).

The amount should be formatted as a string in dollars.

Only applicable to searches for entity objects.

A minimum balance which returned records should have. Limits the search to records with balances greater than or equal to TotalBalanceMinimum.

If TotalBalanceMinimum is specified TotalBalanceMaximum may not be (this limitation is imposed by the QBXML interface).

The amount should be formatted as a string in dollars.

Only applicable to searches for entity objects.

Latest transaction date to search for. Limits the search to transactions with a date on or before TransactionDateEnd.

The standard formatting for dates is YYYY-MM-DD; i.e., September 2, 2002 is formatted as 2002-09-02. When getting the value of a date property, the date will always be in this format.

When setting the value of a date property, the formats MM-DD-YY, MM-DD-YYYY, MM/DD/YY, and MM/DD/YYYY are also acceptable. Dates in these formats will be automatically parsed and stored in YYYY-MM-DD format.

Only applicable to searches for transaction objects.

Earliest transaction date to search for. Limits the search to transactions with a date on or after TransactionDateStart.

The standard formatting for dates is YYYY-MM-DD; i.e., September 2, 2002 is formatted as 2002-09-02. When getting the value of a date property, the date will always be in this format.

When setting the value of a date property, the formats MM-DD-YY, MM-DD-YYYY, MM/DD/YY, and MM/DD/YYYY are also acceptable. Dates in these formats will be automatically parsed and stored in YYYY-MM-DD format.

Only applicable to searches for transaction objects.

Since 2006, QuickBooks has allowed AuthFlags to be set before connecting to QuickBooks. By default, the component can connect to Pro, Premier, and Enterprise editions of QuickBooks. However, because QuickBooks Simple Start contains only a subset of the functionality that other desktop versions provide, Intuit does not allow COM connection to Simple Start unless these AuthFlags explicitly indicate you wish to support it.

A list of allowable AuthFlags is provided below.

To specify support for multiple editions, OR together the values for each edition.

NOTE: If the version of QuickBooks being used does not support AuthFlags, the contents of this config will be ignored. However, if QuickBooks does support this feature, setting "AuthFlags=1" (Support for Simple Start only) on a machine running QuickBooks 2013 Pro will result in an error message indicating that the Request Processor cannot be found.

This is available for entity searches (Account, Customer, etc) when QBXMLVersion is "8.0" or greater.

This is available for entity searches (Account, Customer, etc) when QBXMLVersion is "8.0" or greater.

This field is used as the DueDate for the qtBillToPayQuery Query Type and the TxnDate for the qtItemAssembliesCanBuildQuery Query Type. The standard formatting for dates is YYYY-MM-DD; i.e., September 2, 2002 is formatted as 2002-09-02. When getting the value of a date property, the date will always be in this format.

When setting the value of a date property, the formats MM-DD-YY, MM-DD-YYYY, MM/DD/YY, and MM/DD/YYYY are also acceptable. Dates in these formats will be automatically parsed and stored in YYYY-MM-DD format.

For the qtListDeletedQuery QueryType the following values are supported: Account, BillingRate, Class, Currency, Customer, CustomerMsg, CustomerType, DateDrivenTerms, Employee, ItemDiscount, ItemFixedAsset, ItemGroup, ItemInventory, ItemInventoryAssembly, ItemNonInventory, ItemOtherCharge, ItemPayment, ItemSalesTax, ItemSalesTaxGroup, ItemService, ItemSubtotal, JobType, OtherName, PaymentMethod, PayrollItemNonWage, PayrollItemWage, PriceLevel, SalesRep, SalesTaxCode, ShipMethod, StandardTerms, ToDo, UnitOfMeasureSet, Vehicle, Vendor, and VendorType.

For the qtTxnDeletedQuery QueryType the following values are supported: ARRefundCreditCard, Bill, BillPaymentCheck, BillPaymentCreditCard, BuildAssembly, Charge, Check, CreditCardCharge, CreditCardCredit, CreditMemo, Deposit, Estimate, InventoryAdjustment, Invoice, ItemReceipt, JournalEntry, PurchaseOrder, ReceivePayment, SalesOrder, SalesReceipt, SalesTaxPaymentCheck, TimeTracking, VehicleMileage, VendorCredit

If you change this setting to False, the component will no longer check (or error) when the length of a property exceeds the maximum length specified in the QuickBooks SDK.

If set to true, searching by EntityName or EntityId will include all of that item's children in the response.

This is only applicable to searches for transaction objects.

If QuickBooks is installed on the system, this setting will retrieve the highest QBXMLVersion that may be used for sending transactions to QuickBooks.

If QuickBooks is installed on the system, this setting will retrieve a list of all supported QBXMLVersions that may be used for sending transactions to QuickBooks. While GetHighestVersion config returns only the highest QBXMLVersion supported, this config returns ALL supported QBXMLVersions. The list is delimited with '\n' (linefeed) characters.

The default value is false.

This configuration setting can be used to instruct QuickBooks (via the metaData request attribute) to return a count of the results being returned. This can be configured so that the count is returned with the results or so that only a count and no data is returned.

A list of available values is provided below.

If this is set to return a count, this will be available via the ResultCount configuration setting.

Specifying ModifiedDateStart or ModifiedDateEnd SearchCriteria fields will cause a 'ModifiedDateRangeFilter' tag to be added to the qbXML request. In some transaction queries, however, the QuickBooks SDK specifies a different name for this tag. This configuration setting allows you to specify an alternate tag name to be used.

The default value is ModifiedDateRangeFilter

This setting allows you to let the user know immediately whether your application requires access to personal data or not.

A list of available values is provided below.

The default value is pdpOptional.

Specifies whether the integrated application logs in using single-user or multi-user mode.

The following values are permitted:

About Single-User and Multi-User Modes

If the connection to QuickBooks is made in single-user mode, QuickBooks will give exclusive access to the connecting application. It will lock out all other integrated applications; if QuickBooks and the company file are not already open in single-user mode by the QuickBooks user, the user will be locked out as well.

If the connection is made in multi-user mode, QuickBooks will allow all other integrated applications access. QuickBooks end users on other machines will also be allowed to access the file. However, if the application (rather than the end user) starts QuickBooks automatically, end users on the same machine will still be locked out.

If cmDontCare is specified, an appropriate connection mode will be chosen automatically. If a company file is open in either single-user or multi-user mode, the integrated application will accept that connection mode. If no company file is open, QuickBooks will login automatically in multi-user mode.

About Integrated and Automatic Login

Note that your application's login to QuickBooks might be either automatic or interactive. Interactive login is used when QuickBooks is already open. Access will be shared between the integrated application and the QuickBooks end user, and if multi-user mode is specified, other applications and users will have access as well. When a connection is made, QuickBooks will show a dialog window to the user, and ask the user if he/she wants to permit the connection.

Automatic login is used when QuickBooks is not already open. QuickBooks will be opened in the background, and will run until your application has finished its connection with QuickBooks. The QuickBooks user interface will not be displayed, and end-users on the same machine will be locked out. End-users on other machines, however, will be allowed access if multi-user mode is specified.

By default integrated applications do not have permission to login automatically. The first time an application interacts with QuickBooks, it must do so interactively, with QuickBooks and the company file open. The QuickBooks end user may then grant automatic login permission through Edit Preferences - Integrated Applications in the QuickBooks user interface. Click on the name of the application and then "Properties", and you may allow the application to login automatically.

For automatic login the CompanyFile must be specified. CompanyFile, ApplicationName, and other properties relating to the QuickBooks connection may be edited through QBConnectionString.

This setting may be queried before attempting to connect to QuickBooks to determine the current company file status. When queried the component will attempt to determine whether a subsequent connection using the provided QBConnectionString value would succeed. Possible return values are:

The name of the file currently open in QuickBooks, specified completely with the path. This field is read-only.

A query is submitted to QuickBooks when the value of this property is read. The empty string will be returned if no file is open, if QuickBooks is open in an access mode incompatible with QBConnectionMode, or if an error occurs.

If the value of this property is nonempty, the component may interact exclusively with the open file.

Contains the count returned from QuickBooks when MetaDataType is configured to return this information.

The Base-64 encoded certificate being used by the Remote Connector (you may get this certificate from the Remote Connector by going to the Security tab, and clicking Export.)

This is only necessary if using a self-signed certificate, or any other certificate that has not been signed by a Certificate Authority (CA) trusted by the system.

If your public key certificate is stored in a file, you may set this configuration setting to the full path of the certificate, and it will be immediately read from disk and stored in SSLAcceptServerCert. Equivalent to setting SSLAcceptServerCert to file contents.

Reading the value of this setting will return an empty string.

If StopOnError is True (default), QuickBooks will stop processing when an error occurs. Requests that have already been processed will not be rolled back. An error is returned for the operation that caused the error condition. If StopOnError is False, QuickBooks will continue processing the remaining requests if an error occurs.

Limits the search to records with balances equal to TotalBalance. If TotalBalance is specified, TotalBalanceMaximum and TotalBalanceMinumum may not be (this limitation is imposed by the QBXML interface).

The amount should be formatted as a string in dollars.

Only applicable to searches for entity objects.

Specifying TransactionDateStart or TransactionDateEnd SearchCriteria fields will cause a 'TxnDateRangeFilter' tag to be added to the qbXML request. In some transaction queries, however, the QuickBooks SDK specifies a different name for this tag. This configuration setting allows you to specify an alternate tag name to be used.

The default value is TxnDateRangeFilter

This setting allows you to let the user know immediately whether your application requires the ability to access QuickBooks while QuickBooks is closed.

A list of available values is provided below.

The default value is umpOptional.

By default, the component will throw an exception when a status code with severity "Warn" is returned in a QuickBooks response. Set this field to a comma-separated list of status codes that should not throw an exception if returned. Note that the QuickBooks response code is not necessarily the same as the exception code from the resulting exception.

When queried, this setting will return a string containing information about the product's build.

In a GUI-based application, long-running blocking operations may cause the application to stop responding to input until the operation returns. The component will attempt to discover whether or not the application has a message loop and, if one is discovered, it will process events in that message loop during any such blocking operation.

In some non-GUI applications, an invalid message loop may be discovered that will result in errant behavior. In these cases, setting GUIAvailable to false will ensure that the component does not attempt to process external events.

When queried, this setting will return a string containing information about the license this instance of a component is using. It will return the following information:

• Product: The product the license is for.
• Product Key: The key the license was generated from.
• License Source: Where the license was found (e.g., RuntimeLicense, License File).
• License Type: The type of license installed (e.g., Royalty Free, Single Server).
• Last Valid Build: The last valid build number for which the license will work.

In certain circumstances it may be beneficial to mask sensitive data, like passwords, in log messages. Set this to true to mask sensitive data. The default is true.

This setting only works on these components: AS3Receiver, AS3Sender, Atom, Client(3DS), FTP, FTPServer, IMAP, OFTPClient, SSHClient, SCP, Server(3DS), Sexec, SFTP, SFTPServer, SSHServer, TCPClient, TCPServer.

When set to false, the component will use the system security libraries by default to perform cryptographic functions where applicable. In this case, calls to unmanaged code will be made. In certain environments this is not desirable. To use a completely managed security implementation set this setting to true.

Setting this setting to true tells the component to use the internal implementation instead of using the system security libraries.

On Windows, this setting is set to false by default. On Linux/macOS, this setting is set to true by default.

If using the .NET Standard Library, this setting will be true on all platforms. The .NET Standard library does not support using the system security libraries.

Note: This setting is static. The value set is applicable to all components used in the application.

When this value is set the product's system DLL is no longer required as a reference, as all unmanaged code is stored in that file.