The DocumentsCorePack (DCP) connector allows you to add various actions, such as generating documents, concatenating documents, and running Once-Click-Actions (OCAs). This article outlines how to use the most common actions of the DCP Premium connector.
To use the DCP connector, start by accessing Power Automate and navigate to My Flows. Select a flow or create a new one. Then add a new step and search for the DCP connector.
Click here to see all the available actions.
Figure 1: Search for the DocumentsCorePack connector
After you’ve selected the DocumentsCorePack connector, you will see a list of actions. The most frequently used are the following:
Create document (sync)(V2)
Create DocumentJob (async)(V2)
Attach DocumentJob to email (V2)
Send email (V2)
Attach DocumentJob as note (V2)
Print DocumentJob
Sign DocumentJob based on an XML (sync)(V2)
CreateSharePointFolders (V2)
RunOneClickAction (sync) (V2)
RunOneClickAction (async) (V2)
Concatenate two DocumentJobs (V2)
Concatenate two Document Contents or base64 encoded files (pdf,docx)(V2)
* = mandatory fields.
Outlined below are more details on each of these common actions.
.
Create document (sync)(V2)
❶ *Environment: Specifies the connection to use for a perUser APIKey.
❷ *Template: Select the template for this DocumentJob.
❸ *EntityId: Dynamics 365 source record id.
❹ *FileType: Select a file type for the generated document.
❺ User: Select the user who can execute this action.
❻ SaveToSharePoint: Save document to SharePoint.
❼ DCPPrinterName: Select the DCP printer for a PrintDocument operation.
❽ AttachToEmail: Specifies the email to attach the Job to.
❾ AttachToEntity: Specifies the entity ID to attach the Job to.
❿ AttachToEntity – Schemaname: Specifies the entity schema name to attach the DocumentJob to.
.
Create DocumentJob (async)(V2)
❶ *Environment: Specifies the connection to use for a perUser APIKey.
❷ *Template: Select the template for this DocumentJob.
❸ *EntityId: Dynamics 365 source record id.
❹ *FileType: Select a filetype for the generated document.
❺ User: Select the user who can execute this action.
❻ SaveToSharePoint: Save document to sharepoint.
❼ DCPPrinterName: Select the DCP printer for a PrintDocument operation.
❽ AttachToEmail: Specifies the email to attach the Job to.
❾ AttachToEntity: Specifies the entity ID to attach the Job to.
❿ AttachtoEntity – Schemaname: Specifies the entity schema name to attach the DocumentJob to.
.
Attach DocumentJob to email (V2)
❶ *Environment: Select the Environment for this operation.
❷ *DocumentJobId: The DocumentJob ID of the generated document to attach to the email.
❸ *EmailId: The email the document should be attached to.
❹ User: Select the user who can execute this action.
.
Send email (V2)
❶ *Environment: Select the Environment for this operation.
❷ *EmailToSend: GUID of email to send.
❸ User: Select the user who can execute this action.
❹ Sender (userid): GUID of email sender.
❺ Sender (Schemaname): Schema name of the sender (default is systemuser).
❻ Regarding (Id): GUID of the entity to set as regarding.
❼ Regarding (Schemaname): Entity name of the record to set as regarding.
.
Attach DocumentJob as note (V2)
❶ *Environment: Select the Environment for this operation.
❷ *DocumentJob: The DocumentJob ID of the generated document to attach to the note.
❸ *Schemaname: Entity name of the record the note is attached to.
❹ *EntityId: GUID of the entity to attach the note to.
❺ Note description: Set this text as Notes description.
❻ Note subject: Set this text as Notes subjects.
❼ User: Select the user who can execute this action.
.
Print DocumentJob (V2)
❶ *Environment: Specifies the connection to use for a perUser APIKey.
❷ *DocumentJob: GUID of the DocumentJob Id to print.
❸ *DCPPrinterName: DCP Printername of the printer to use.
.
Sign DocumentJob based on an XML (sync) (V2):
❶ *Environment: Specifies the connection to use for a perUser APIKey.
❷ *EntityId: GUID of the Entity that the eSign record will be attached to.
❸ *Schemaname: The Schemaname of the Entity that the eSign record will be attached to.
❹ *DocumentJob: DocumentJobId containing the document to sign.
❺ *Signing Provider: The provider that should be used to sign this document.
❻ *Name: The display of the Signee.
❼ *Email: The email address of the Signee.
❽ *InPerson Signing: Generates a link to start the signing process.
❾ Subject: Personalized subject in signing request email.
❿ Message: Personalized message in signing request email.
⓫ Telephonenumber: Signees telephone number for SMS authentication. (DocuSign only)
⓬ DocuSign Hostname: Signing hosts name for inPerson signing. (DocuSign only)
⓭ Hostemail: Signing hosts email address for inPerson signing. (DocuSign only)
⓮ Email Default Subject: Default subject in signing request email.
⓯ Email Default Message: Default message in signing request email.
.
CreateSharePointFolders (V2)
❶ *Environment: Specifies the connection to use for a perUser APIKey.
❷ *EntityId: GUID of the entity to create the folders for.
❸ *Dynamics Schemaname: The Schemaname of the entity to create the folders for.
❹ Folder name enumeration: Name of the folder(s) you want to create.
Syntax: “;” separates list of folders
“/” creates subfolders
Example: FOLDER/subfolder 1; FOLDER/subfolder 2; FOLDER1/subfolder 1
Creates folders as follows:
❺ User: Select the user who can execute this action.
❻ DocumentLocation: SharePoint location you want to create the folders in.
.
RunOneClickAction (sync)(V2)
❶ *Environment: Specifies the connection to use for a perUser APIKey.
❷ *EntityId: Dynamics 365 source record id.
❸ *OneClickAction: Id of the OneClickAction to apply.
❹ User: Select the user who can execute this action.
.
RunOneClickAction (async)(V2)
❶ *Environment: Specifies the connection to use for a perUser APIKey.
❷ *EntityId: Dynamics 365 source record id.
❸ *OneClickAction: Id of the OneClickAction to apply.
❹ User: Only retrieve templates accessible to this user.
.
Concatenate two DocumentJobs (V2)
❶ *Environment: Select the Environment for this operation.
❷ *First DocumentJob: First DocumentJobId of ConcatenationJob.
❸ *Second DocumentJob: Second DocumentJobId of ConcatenationJob.
❹ *CombineType: Define the format that the documents should be concatenated.
❺ *OutputFileType: File type of the concatenated document.
❻ User: Select the user who can execute this action.
.
Concatenate two Document Contents or base64 encoded files (pdf,docx) (V2)
❶ *Environment: Select the Environment for this operation.
❷ *First Filename: The filename of the first document.
❸ *First Mime–Type: Content mime-type for handling of the first document (e.g. application/pdf).
❹ *First Document content: A content-object or base64 encoded string representing the files content.
❺ *Second Filename: The filename of the second document.
❻ *Second Mime-Type: Content mime-type for handling of the second document (e.g. application/pdf).
❼ *Second Document content: A content-object or base64 encoded string representing the files content.
❽ *CombineType: Define the format that the documents should be concatenated.
❾ *OutputFileType: File type of the concatenated document.
❿ User: Select the user who can execute this action.
Back to “The DocumentsCorePack connector for PowerApps and PowerAutomate (Microsoft Flow)“.
That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com