Pre-fill from Dynamics 365 via FetchXML

Automatically import data from your MS Dynamics 365 records to documents.

When the bot works by default:

The Pre-fill from MS Dynamics 365 via FetchXML bot activates when a recipient opens or creates a document.

To add the bot to a step, click on the three dots for this step and select Add bot to step.

Search for the bot you need by category or using the search bar. Then, install the bot to your workflow by clicking the Install bot button.

To connect the bot to your MS Dynamics 365 account, click Connect in the Connection settings section.

Then, select the MS Dynamics 365 account you need to connect. You can also connect a new account by clicking Add connection.

Enter your MS Dynamics 365 instance URL. Copy it from your MS Dynamics 365 organization, as shown in the example. After that, click Apply, and you’ll be redirected to the Microsoft login screen. Once you’ve logged in, you’ll be directed back.

Once connected, proceed to the next section.

In the Select entities and map fields section, paste your FetchXML query that will retrieve data from the MS Dynamics 365 records. After that, click Update mapping.

.

If you need, you can also retrieve data from the documents by including document fields in the query. To do this, put a value in the query and click +Data variable. Then, select a document in the workflow and the document field from which you intend to export data (as shown in the screenshot).

Select a data transfer method. The single line method means that you transfer one data instance from field to field, such as Name, Email, and Address, while the table method transfers data from table to table, such as lists of customers or products.

Next, indicate which data must be transferred to the document by mapping the needed entity fields to the respective document fields. Select entity fields and link them to the document fields that should contain the corresponding values from the entity’s record. To map more fields, click the Map another field button and repeat the process.

Configure the bot execution conditions based on simple “if-this-then-that” rules. For example, you can set conditions based on document field information, recipient data, date of document signing, document data, and decline reason. Learn more about bot conditions usage in the dedicated article.

In this section, you can set additional bot configurations:

Learn more about adjusting Advanced settings in this article.