Intacct Operation

The Intacct Operation defines how to interact with your Intacct company. The Operation represents a specific action (e.g. Create, Apply, Get List, or Delete) to be performed against a specific Intacct record type or object (e.g. GL Account, Bill, GL Entry, Customer, etc.). Not all actions are available for every object. You will need to create a separate Operation Component for each action/object combination required for your integration.

The Operation supports two types of actions:

• Get - Used to retrieve data from Intacct.
• Send - Used to send data to Intacct.

GET Action - Options Tab

Use the Import button to launch the Import Wizard which will help you configure the Operation. The wizard will automatically generate the Request and Response XML Profiles.

This then brings you to a dialog in which you may choose the function, which would be the Intacct object name (see Intacct documentation for reference) Once a function is chosen, you must then choose the action to be applied to that function such as "Get Object" or "Get List".

The Get Object and Get List actions provide a flexible way in which to retrieve information about objects in the Intacct system. The Get Object action allows you to retrieve a single instance of an object by specifying the object, and a key. The Get List action allows you to retrieve a list of all or a filtered set of instances of an object in the Intacct system.

Once Get Object or Get List is chosen, you should then click >> Next >> Finish and Boomi AtomSphere will then load the function into the connector operation. When this happens, a response profile will be auto-generated and populated. This is the XML profile that you may then map from to extract any information needed within the interface. Please follow Intacct documentation or Boomi AtomSphere pre-loaded libraries for proper field mapping rules.

If you choose the Get List action for a particular function, you will be presented with additional options.

Start	You may specify the start record of the list of objects to increase performance. If left blank, this will default to zero.
Max Items	You may define a maximum number of items to pull in the list.  For example, if 100 were defined in this area for pulling from the Employee interface, only 100 employee records will be extracted.  If left blank, all available records will be retrieved.
Show Private	In Multi-entity Shared implementations, some objects may be owned by a subsidiary entity, but are visible at the root.  If this is checked, the list will return all records visible in the current multi-entity context. If left unset, the list will only return those records owned by the current multi-entity context.
Filters	See Below

Filters

This option allows you to build a custom query to apply in extracting data from Intacct.  The "Logical" definition allows you to define AND or OR clauses within the query.  For example, you can use this functionality to extract all Employee records that begin with the last name M.

If you click on the blue arrow next to the "Logical Definition", you will be presented with several options:

Add Logical Sub Group	This allows you to add an additional sub AND or WHERE clause to the existing clause
Insert Logical Sub Group	This allows you to add an additional AND or WHERE clause to the main query.
Add/Insert Expression	When defining a Logical clause or sub clause, you should always define an expression for the clause. This is the definition of the field and operator (such as =, >, <, etc)
Delete	This deletes the current node.

As you build your query, the expression will be built automatically and viable within the filter window. The string in this window is not editable. Since the values that you in your "Logical Definition" are parameters, they will appear as ?'s in the expression.

In order to define the parameters of your Logical definition either dynamically, or with static values, you must define these parameters in the Connector Shape within the Process.

Archiving Tab

Click here for more information on Archiving.