> ## Documentation Index
> Fetch the complete documentation index at: https://docs.engini.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Microsoft Dataverse
Learn how to connect Microsoft Dataverse to Engini, enabling efficient integration of your business data and application logic. With the Dataverse connector, you can access structured data in real time, automate workflows, and unify information across different services. Effortlessly manage entities, relationships, and custom tables to support business processes and analytics.
To get started with the Microsoft Dataverse, create a free account at Microsoft or use your organizational Microsoft account.
## Connecting Engini to Microsoft Dataverse
1. Enter your Engini account at [https://app.engini.io](https://app.engini.io/).
2. Navigate to Connections page by clicking on the Connections on the left side bar or by clicking [here](https://app.engini.io/connections).
3. Click on the "New Integration" option located at the top bar.
4. Choose “MIcrosoft Dataverse” option from available applications.
5. Enter the following details in the “New Integration” form and press Save:
1. *Connection name* – A unique identifier for the connection within Engini.
2. *URL of Dataverse environment* – The URL of a Dataverse environment is the web address you use to access your specific Dataverse workspace, where your data is stored and managed.
* To access this, sign in to your Microsoft Dataverse account and navigate to **Settings**
* In the opened menu, select **Developer Resources**.
* Navigate to the section labeled ‘Web API Endpoint’ and copy the Base URL highlighted in the picture to Engini.
3. *Microsoft Signin* – this is the authentication process where users log into their Microsoft account to gain access to Microsoft services.
* Click on the button to sign in to your Microsoft account.
* ***Access Token & Refresh Token*** – Automatically populated post connecting to a your Microsoft account.
* *Access Token* – A temporary security token that allows your application to access protected resources or APIs on behalf of the user. It serves as proof that the user has granted permission.
* *Refresh Token*– A token with an extended lifespan used to request a new Access Token once the original one expires, without requiring the user to log in again
4. Click on the save button to save the connection.
After you’ve saved the connection, a window will open displaying all available entities and actions. From this window, select the entities and actions you want to use.
**Note**: After you’ve saved the connection, you can add additional objects and actions.
On the right side of the saved connection, you’ll see three dots.
* Click on the three dots and then click on “Select database objects”.
* A window will open displaying all available entities and actions, just like when you saved your connection. From this window, select the new entities and actions you want to use.
Once you’ve finished selecting the additional entities and actions, click Save.
## Triggers
### Entity Event Trigger
Triggers when an event type is activated.
* *Event Type* – Select the type of event that will trigger the workflow to start. Common event types include creation, update, or deletion.
## Activities
### Create Record
This activity creates a new record in Microsoft Dataverse based on yours selected object.
* *Object Type –* Select the object you want to create (e.g., Accounts, Contacts).
After selecting a specific object, you will have the option to populate it’s fields by using “Add Field”.
* *Add Field* - Click Add Field to add and populate additional fields for the selected activity. To learn more about managing activity data, [click here](/help/workflows/workflow-editor#add-fields).
### Create Records Batch
This action creates multiple new records in Microsoft Dataverse in one batch operation.
1. *Object Type –* Select the type of object (table) where the records will be created.
2. *Data List –* Provide the list of records to be created. Each item in the list should match the structure of the selected object type.
After selecting a specific object, you will have the option to populate it’s fields by using “Add Field”.
* *Add Field* - Click Add Field to add and populate additional fields for the selected activity. To learn more about managing activity data, [click here](/help/workflows/workflow-editor#add-fields).
### Delete Record
This action deletes a specific record from Microsoft Dataverse based on the selected object type.
* *Object Type –* Select the type of Microsoft Dataverse object you want to delete (e.g., Accounts, Contacts).
* After selecting the object type (e.g., Accounts), provide the unique ID of the specific record you want to delete. For this object, it’s the Account ID.
### Delete Records Batch
This action removes multiple records from Microsoft Dataverse in a single batch operation.
1. *Object Type –* Select the type of object from which the records should be deleted.
2. *Data List –* Provide the list of records to be deleted. Each item in the list should match the structure of the selected object type.
* After selecting the object type (e.g., **Accounts**), provide the unique **ID** of the specific records you want to delete.
### Execute Action
This action executes an operation from the list you selected during the connection setup.
* *Action type –* Click the dropdown and select the specific action to be performed from the list.
After selecting the action type (e.g., Send Email), provide the necessary details for the action.
* *Add Field* - Click Add Field to add and populate additional fields for the selected activity. To learn more about managing activity data, [click here](/help/workflows/workflow-editor#add-fields).
### Get Record
This action retrieves a specific record from Microsoft Dataverse based on the selected object type.
* *Object Type –* Select the type of Microsoft Dataverse object you want to retrieve (e.g., Accounts, Contacts).
After selecting the object type (e.g., **Accounts**), provide the necessary detail.
1. *Account –* Provide the unique identifier of the record you want to retrieve.
2. *Output fields –* Specify which fields you want to retrieve from the record.
### Get Records
This action retrieves multiple records from Microsoft Dataverse based on the selected object type. You can optionally apply filters, sorting, and set a limit (Top N) on how many records to fetch.
1. *Object Type –* Select the type of object you want to retrieve records from.
2. *Top N –* You can specify how many records with the same value you want to get. Click on ‘Top N’ and enter the maximum number of values you want to retrieve.
If you set `Top N = 1`, a single record will be returned instead of an array. If no record is found, the action will fail, allowing you to implement an IF condition within the workflow. This can be useful for processes where the existence of a record determines the next steps in the workflow.
3. *Add Filter -* Click Add Filter to define conditions that narrow down the data list and return only the relevant items. To learn more about using filters, [click here](/help/workflows/workflow-editor#add-filters).
4. *Add Sort -* Click Add Sort to organize the data list by a selected field in ascending or descending order. To learn more about sorting data, [click here](/help/workflows/workflow-editor#add-sorts).
### Get Records Batch
The Get Records Batch action retrieves multiple records from Microsoft Dataverse in a single call based on a list of IDs.
1. *Object Type –* Select the type of object to retrieve records from.
2. *Data List –* Provide the list of records to be retrived. Each item in the list should match the structure of the selected object type.
* After selecting the object type (e.g., **Accounts**), provide the unique **ID** of the specific record you want to retrieve.
### Update Record
This action updates an existing record in Microsoft Dataverse. It allows you to change one or more fields within a specified object
* *Object Type –* Select the type of object that contains the record you want to update.
After selecting the object type (e.g., **Accounts**), provide the necessary detail.
1. *Account* – This field requires the unique identifier (ID) of the record you want to update.
2. *Add Field* - Click Add Field to add and populate additional fields for the selected activity. To learn more about managing activity data, [click here](/help/workflows/workflow-editor#add-fields).
### Update Records Batch
This action updates multiple existing records in Microsoft Dataverse in one request.
1. *Object Type –* Select the type of object that contains the records you want to update.
2. *Data List –* Provide a list of records to update.
After selecting the object type (e.g., **Accounts**), provide the necessary detail.
1. *Account* – This field requires the unique identifier (ID) of the record you want to update.
2. *Add Field* - Click Add Field to add and populate additional fields for the selected activity. To learn more about managing activity data, [click here](/help/workflows/workflow-editor#add-fields).
### Initialize Object Array
This action initializes an array variable that holds objects of the selected type.
1. *Variable name –* Enter a name for the array variable that will store the list of objects.
2. *Object Item Type –* Select the type of object that each item in the array will represent.
After selecting a specific object item type, you will have the option to populate it’s fields by using “Add Field”.
* *Add Field* - Click Add Field to add and populate additional fields for the selected activity. To learn more about managing activity data, [click here](/help/workflows/workflow-editor#add-fields).
### Append to Object Array
This action adds a new object to an existing object array variable that was initialized earlier in the workflow.
* *Variable –* Select the array you initialized in the previous steps.
After selecting the variable, the “Add Field” option becomes available.
* *Add Field* - Click Add Field to add and populate additional fields for the selected activity. To learn more about managing activity data, [click here](/help/workflows/workflow-editor#add-fields).
### Map Object Array
The map array activity allows you to transform a list of data items into a new data list based on the object’s properties and values you choose.
1. *Data List –* Choose a data list that you’ve obtained from previous activities in your workflow. This data list typically contains an array of objects that you want to process and transform.
2. *Object name –* Define the type of objects from the drop down that will be stored within the array.
After selecting the object, the “Add Field” option becomes available.
* *Add Field* - Click Add Field to add and populate additional fields for the selected activity. To learn more about managing activity data, [click here](/help/workflows/workflow-editor#add-fields).
### Send API Request
This action allows you to send a custom API request directly to the Microsoft Dataverse API.
1. *Base Url* – This is the root URL of the API you’re sending the request to.
2. *Relative Url* – You can specify additional path segments or parameters that need to be added to the end of the automatically generated URL. This allows you to customize the specific request you want to perform.
3. *Method* – Select the HTTP method (e.g., Get, Post, Put, Delete, Patch).
4. *Body Type* – Defines the format of the data in the body of your request. A commonly used value is application/json , which means the body will contain a JSON-formatted payload.
5. *Body* – Contains any data that is being sent to the server.
6. *Add Headers* – Additional metadata about the request, such as the type of data that Engini can accept, the length of the request body, and authentication information.
* Click on the “Add Headers” button to add a header.
* Click on the headers field to enter the key, and on the value field to enter a value. Each header consists of a key-value pair, where the key is the name of the parameter, and the value is the data associated with that parameter.
* Click on the “Add” button to add more Headers.
7. *Add Queries* – The query refers to the parameters or data that are included in the URL of an HTTP request to provide additional information or instructions to the server.
* Click on the “Add Queries” button to add a header.
* Click on the queries field to enter the key, and on the value field to enter a value.
Each query consists of a key-value pair, where the key is the name of the parameter, and the value is the data associated with that parameter.
* Click on the “Add” button to add more queries.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.