This is a paid bot, and its usage will be counted toward your plan's credit limit. For more information about credit usage, refer to this article.
General
Use the Export files to MS Dynamics 365 bot to automatically attach completed documents to your MS Dynamics 365 records.
Use case: When collecting Purchase orders from your customers, you need documents to export to the respective MS Dynamics 365 records without manual actions.
How to set up
To add the bot:
1. Add a new action by clicking a plus icon.
2. Choose Bot and search for the Export files to MS Dynamics 365 bot.
3. Click on the bot to install it.
Trigger
A trigger is an event that causes the bot to start working. The bot can be placed only after a step or any other element (for example, another bot), and it will run once the previous element finishes its job.
Connection settings
In Destination, connect the bot to your Microsoft account by clicking the Connect button.
In the pop-up, enter your MS Dynamics 365 instance URL. Copy it from the address bar when you’re in your organization and click Select after pasting it. In the screenshot, you can see an example of how it must look like.
You’ll be redirected to the Microsoft login screen. Once you’ve logged in, you’ll be directed back to WorkFlow.
Using the three-dot connection menu, you can disconnect the current account or connect to different accounts anytime.
Select a base object in MS Dynamics 365 where to export files (1). Click Continue to proceed (2).
In Documents, select the documents you want to export by checking the respective documents.
If you want to export documents archived, check the Save document as ZIP file box.
Click Continue to proceed to the next section.
Lookup
In Find record, set rules for how the bot will find the MS Dynamics 365 record you need. Start by selecting an object field that must work as an identifier.
Then, select the value type that your object field must match.
Value based on | Explanation |
Document field value | This option allows the bot to find records by matching the value in the specified object field with a corresponding value in a document field.
For example, if your document has a field that captures a record ID or name, the bot will search for records where the object field contains this value.
|
Signer details | This matching type uses the details the signer provides, such as their email, first name, or last name, to find a corresponding record in the object.
It’s useful for workflows where the signer’s identity must be cross-referenced with your system's records. |
Text input | This option allows you to manually enter a custom text value, which the bot will use to find a matching record in the object.
This is particularly useful when the value to be matched isn't defined by the document or the signer but is a specific input the workflow creator provides.
|
After that, provide the value that must match the object field, according to your choice. You can add as many lookups as you need by clicking Add match.
Click Continue to proceed to the next section.
Testing
In the Test section, simulate the bot's performance by clicking Test.
For testing, you’ll have to input data matching search criteria. Enter it in the field as shown below. A success message confirms proper configuration. Any errors will be displayed as an error message.
Note: Keep in mind that after running the test, the files will be exported to the MS Dynamics 365 record.
Note: The Test section allows you to test your bot and ensure that it’s set correctly. After you publish your workflow, the Test section will no longer be available. The bot will then work using the conditions set in the Find record section.
Conditions
Set conditions to control when the bot activates, tailoring it to your specific needs for more efficient automation. For detailed guidance, refer to this article.
Without defined conditions, the bot will default to activating whenever recipients complete the documents.
Advanced settings
This section allows you to choose how the process proceeds in case the bot fails:
Select Proceed to allow the workflow to move to the next signer and automation if the bot isn't crucial.
Select Stop if the bot is critical; this prevents the next signer from receiving documents if data wasn't pre-filled from the source of your choice.