With the new option to call a Flow from the ‘Create Document‘-dialog, DocumentsCorePack users can utilize the full suite of Power Automate to process documents or add logic as needed for their business process.
How it works
Visit flow.microsoft.com, navigate to My Flows, and press New Flow.
A drop-down list offers you some choices. Select Instant cloud flow.
The Build an instant cloud flow site opens. First, give your flow a name. Then scroll down to When HTTP request is received and make a tick. Press the Create button.
Click on the When a HTTP request is received action header to open the details.
Please note: The HTTP POST URL you will later need is generated here after saving!
Please note: Only Flows with a specific trigger (When a HTTP request is received) will work.
The following Request Body JSON Schema has to be added to the Flow (Just copy and paste it).
{
"type": "object",
"properties": {
"AMWIID": {
"type": "string"
},
"RecordID": {
"type": "string"
},
"RecordLogicalName": {
"type": "string"
},
"File name": {
"type": "string"
},
"File size": {
"type": "integer"
},
"Document (Base64 encoded)": {
"type": "string"
},
"Mime-Type": {
"type": "string"
},
"ActivityLogicalName": {
"type": "string"
},
"ActivityId": {
"type": "string"
}
}
}
The request JSON Schema defines the data that will be delivered to the Flow:
- “AMWIID“ – It is the ID from the AutoMergeWorkingItem which was created in the dialog.
- “RecordID“ – ID of the start data record from which the dialog was started
- “RecordLogicalName” – Logical Name of the start data record (e.g.: account, quote, contact, opportunity,…)
- “File name“ – Name of the file that was created
- “File size“ – The size of the file that was created
- “Document (Base64 encoded)“ – Document content as Base64 string
- “Mime-Type“ – Document type that is given (e.g., application/pdf)
- “ActivityLogicalName” – Logical name of the activity (e.g.: email, letter, phone call,…)
- “ActivityID – ID” of created activity
As you can see it contains both: Information on the record (RecordID) the document was generated for as well as the document itself. Thus, it is now possible to use this information in your flow to work with the document and perform operations in your Dynamics 365 instance (DataVerse) as required by your business process.
To activate this flow in your environment, you need to add the following MSCRM-ADDONS.com Settingskey (Learn more about how to create a Settingskey):
Name: MicrosoftFlows
KeyValue: [FlowName1]|[FlowUrl1];[FlowName2]|[FlowUrl2]…
Product: AutoMerge
Please note: Please have a look at Figure 4 where to get the Flow URL!
In this example it is looking like this:
In your Dynamics 365, you can see under My Flows the success of your newly created MicrosoftFlow.
Example: Save a document to Onedrive and store the link to the Record in Dynamics 365.
This example shows how a document generated for a Quote inside the Sales Hub can be uploaded to a specific folder on Onedrive as well as storing the URL of this file back to the Quote inside the Sales Hub.
Flow-Setup: Instant Cloud flow with HTTPS trigger as outlined above.
Actions:
- Upload file to Onedrive: Here we can use the Filename and Document (Base64 encoded) parameters provided by the HTTP trigger.
- Save URL back to Dynamics record: Here we use the RecordID provided by the HTTP trigger to identify the quote record so we can do an update of the Description field to hold information on the file upload.
Send a response from Flow to DocumentsCorePack dialog:
There is also the option of sending a response back to the dialog. You can define records as entity references and pass them back as the body of the HTTP-Response action inside your flow.
Examples:
- You are creating records (e.g. tasks or cases) in your flow and want to open them up upon generating a document.
- You are doing updates on the record you are generating the document for and want to refresh the record for the user so they see the updated version.
Example JSON-schema for two entity records:
{
"EntityReferences": [
{
"LogicalName": "[Entity Name 1]",
"Id": "[GUID 1]"
},
{
"LogicalName": "[Entity Name 2]",
"Id": "[GUID 2]"
},
]
}
In this response, you can specify data records in a JSON format, which are then opened by the dialog.
In this example the “Quote” is pushed back to the dialog ensuring users see the updated version (description field in this example).
That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.