Enterprise Service Bus Data Handler - QuickBooks Browse

The QuickBooks Browse data handler allows the builder to create an application that reads records from QuickBooks Online.

This feature will be available in Platform Version 10.14.1001

For the QuickBooks Browse data handler to work properly there needs to be several elements added to the application. A table will need to be created by the builder that the ESB will write to. The QuickBooks Browse Data Handler will read a variable amount of data depending on the type of QuickBooks Record. The ID and Sync Token are used to identify and sync a record with QuickBooks and is required for QuickBooks Edit and QuickBooks Delete data handlers to work.

For an End User to connect to QuickBooks and use this ESB they will need to login to QuickBooks Online.

There are five configuration options in this data handler.

• OAuth Consumer Key - Intuit provides this key as a way to identify an application when requesting data from QuickBooks.
• OAuth Consumer Secret - Intuit provides this key as a way to secure the identity of the application. This value should not be public knowledge and protected like a password.
• OAuth Field - This query points to the record and Intuit OAuth field that is being used to identify which QuickBooks Online Account the ESB is communicating with.
• QuickBooks Table - This is the table that the ESB will add records to.
• Values to Browse - This setting allows the application developer to determine what data is returned from QuickBooks.

This Data Handler is triggered via an Enterprise Service Bus Action. To see which actions will trigger this Data Handler use the “Outgoing” tab on the Enterprise Service Bus page.

When this Data Handler is used in an Enterprise Service Bus Action it becomes possible to add child actions below the ESB Action. Actions added to this part of the action tree will have available as run time values the values returned from QuickBooks.