> For the complete documentation index, see [llms.txt](https://docs.greytrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.greytrix.com/gumu-salesforce-integration/sage-intacct-1/user-guide/chaining.md).

# Chaining

In an integrated system, it's crucial to manage data dependencies efficiently, especially during data import routines. A chain import routine is a structured process where multiple data imports are executed in a specific order, ensuring data consistency and integrity. This sequence is particularly important when dealing with entities that have dependencies on one another.

For example, consider a scenario where you need to import data related to **Accounts**, **Contacts**, **Orders**, and **Order lines**. The correct sequence would be to start with Accounts, followed by Contacts, then Orders, and finally Order lines. Here's why this order matters.

In the GUMU integration mapping screen, you can select the next import routine to run, as shown below.

***Note:***\
***This is a feature added so that related object records can be automatically imported once previous object records are imported. This is not a mandatory configuration.***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.greytrix.com/gumu-salesforce-integration/sage-intacct-1/user-guide/chaining.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.