SharePoint Journey: June 2022

Monday, June 27, 2022

MS CRM: How to convert word template into pdf using Microsoft Flow

Many times, when we use word template in dynamics crm to generate a template, we customer want the word template to be in pdf format rather than word which obviously seems more professional to send to their consumers and can’t be edited directly.

Unfortunately, so far, out of the box crm doesn’t have any tool to get the pdf file from generated word file for any record, but now we have Microsoft flow for our rescue.

In this post,we’ll see how we can generate a word template using a workflow and how can we get the word template file converted into pdf format using microsoft flow.

Scenario:

We have Invoice summary word template which customer run on invoice record to generate Invoice summary for customer in word format. We want to convert it into pdf format.

Part A: Creating workflow in crm to generate word template on record

Step A1:

Create a UI workflow in crm as shown below. In add step select perform action:

Step A2:

After step 1, workflow will look as shown below.

Click on set properties as select word template and primary field of the entity:

Step A3:

We have kept this workflow on demand only of testing purpose. You can configure it to fire on the event you want as per your requirement.

Now, activate your workflow.

Step A4 (Testing the workflow):

This workflow, when run on an invoice record, will generate a word file from selected template and attach in the notes section as shown below:

Part B: Creating a Microsoft flow to convert this word file from notes into pdf

Step B1: Go to https://flow.microsoft.com and select Dynamics365 as start the service for your flow.

Then select when a record is created as the trigger of your flow as shown below:

Step B2: Now select your crm instance and entity name as notes and check if the file name equals Invoice Summary.docx (same as the file generated by workflow)

STEP B3: Now on Yes part of result of condition, select One drive for business as the connector and select create File as the action.

In create one drive file :

Select a path where file will be stored
set a file name
Type base64ToBinary function in expression and then from Dynamics content select document field of “When a record created” step (notes record which triggered the flow) and set this as file content.

Step B3: In this step again select one drive for business connector and select convert file as the action. Here you have to pass unique Id of the file we just created in one drive in last step as the parameter.

Step 4B:Now create a notes record in crm with the file we just converted in last step.

Set Title and file name with .pdf extension as shown in below screenshow. For document, just set “body(‘Convert_file’)[‘$content’]” in expression and click update.

Basically here Convert_File is the name of last step. Change “body(‘Convert_file’)[‘$content’]” to “body(‘Convert_docx_file_to_pdf_in_onedrive’)[‘$content’]” if your last step’s name is “Convert docx file to pdf in onedrive”.

For regarding, set regarding value of notes record created and regarding type as Invoice.

Step 5B:

Now to save up extra space, delete the .docx file created in one drive as well as the docx file created in crm.

Step 6B: One done, your flow will look as below . I have changed steps label for better understanding.

Just save it now.

Testing:

Now it’s time to test the whole setup. Just run the on demand workflow on an invoice record and wait for some time. you’ll see a pdf record attached in notes section of your record as shown below:

So this was how you can convert word template to pdf.

Now you can use this pdf file attached in notes to send to customer in email. So the whole process of sending pdf of word template can be done on a single button click event on crm form.

Few imp Points :

You can also use Azure logic apps, (Both ms flow and azure logic apps are licence based services)
As per my logic, this flow will trigger on each notes record creation. This can be optimize keeping in mind under licence have limited number of flow run per month.

File Type column in Microsoft Dataverse (formerly cds)

Yesterday I saw that there is a new (new to me at least..!) type of column (formerly attribute) which you can create in any customizable table (formerly entity) which can be used to upload file.

You can create multiple file type columns in a table and upload one file in one column.

I create a new column called Document in account table as shown below from power app maker portal.

Same can be created from classic interface as well:

More importantly it’s not visible in classic form editor to add onto account form So better to use power app maker portal to do any customization :

Then i uploaded a sample txt file in my Document column on account record:

Playing arou

JavaScript and Business Rule on the same field

Recently, on change of value of a field, we had business rule earlier and then we decided to perform the same using JavaScript to avoid hard coding of value in Business rule. The logic was to set value of 2 other fields on the form based on the value selected.

The logic was working fine on DEV as we had deactivated the business rule. However, after deploying to TEST and UAT, it stopped working.

We verified that the JavaScript event handler was enabled for the OnChange event of that field.

While debugging the code as well using browser console, we checked that the break point was hitting the code block where we were setting the value of 2 other fields.

After struggling for few minutes, it came to our mind that Business rule was also written which should have been deactivated.

The business rule was basically clearing the values of the 2 fields if the selected value of field was not in the condition anywhere.

After deactivating the business rule, closing the form, opening it again when we tested it, it worked.

So, if we have JavaScript and Business Rule written on the same field, then the order of execution is first JavaScript then Business Rule for which even if the values of the 2 fields were set using JavaScript were getting cleared by the Business Rule.

In Dynamics crm ff you have both javascript and business rules on same form then it follow below order:

Any system script is applied first
Custom javascript
Business rule, In case multiple business rule exist on same event, they run in the order they were activated. Means the one which was activated first will execute first and the one activated last will execute at last.

Tuesday, June 14, 2022

Export and Import Dynamic 365 Solution from one environment to another using Azure DevOps CI/CD Pipeline.

DevOps is very vast, we can perform n number of automation but today i will be focusing on import and export Dynamics 365 solution using Azure DevOps CI/CD Pipeline.This blog article is going to be bit longer because we have a lots of step, so guys bear with me and read it thoroughly you will get answer of your questions. We have lots of trigger where we can call our build and release, for your reference https://docs.microsoft.com/en-us/azure/devops/pipelines/build/triggers?view=azure-devops. Also you can call your Pipeline events from Power Automate. I would not go deep into it.

Prerequisite:

1.Azure Pipeline subscription.

2.Dynamics 365 Customer Engagement Online.

Create a folder inside your repository where you can keep solution after the solution is exported.

Give a proper name , I am using “Dynamics365Solution”. You can not create empty folder so i just created an text file with the same name.

Once file is created click on commit changes for saving the file in DevOps repository.

Once the folder added we are going create Variable groups for storing connection string(which will be used while make connection do Dynamics 365 CE Online for export and import of the solution).It is a good practice for storing connection string inside the Variable group. Go to Library then click on +Variable group.

Now give variable group a name. I will assume you got a Dev and a UAT environment. The package from the build automation blog will be deployed to these environments.So, we will create two connection string for the Dev and UAT environments.

1.Connection String-AuthType=$(AuthType);Username=$(Username);Password=$(Password);Url=$(Url)

URL- Enter your instance URL.
Username – Enter the username of your instance
Password – Enter the password of your instance
Authtype – Office365

Below is the sample connection string details for your reference

AuthType=Office365;Username=jsmith@contoso.onmicrosoft.com; Password=passcode;Url=https://contoso.crm.dynamics.com

After that we need to create a build pipeline. Navigate to Pipeline->Create Pipeline.

We are using Azure Repos Git as a source , after that choose your Team project and repository where you want to perform your pipeline operation. Specify your branch for your build , using master for the demonstration.

After that choose your template, but currently we do not have template for Dynamics 365 so we are going to use Empty job.

Microsoft provided job Agents which give you more control to install dependent software needed for your builds and deployment. For exporting solution we need to add three task.

First, search for the Power DevOps Tool Installer(it will copy all the tools to agent, optimize the process) by Wael Hamze.

Second, we are going to add Export Solution in similar way we added installer. Once it is added we need to specify three parameter. We already created in variable groups so lets utilize those connection string.

We need to link Variable group within pipeline, navigate to Variables click on link Variable group.

Choose your variable group, we are using “Dev Credential” here. Click on link. Because first we are going to export solution from our Dev environment.

Now First pass the Connection string. Second, the Name of your solution which you want to export, My solution Name is “DevopsExport”. Third you need to specify the output path.Click on … for browse and select the path which we created a folder inside the repository on start of our blog which was “Dynamics365Solution” .

You have lots of option in Additional setting of the Export Solution. Which you can add based on your requirement.

Once we exported the solution we need to publish it as an artifact. Add third task “Publish Artifact”. You can give a name to Artifact and need to specify the path same as your exported folder. After that click on Save & Queue.

it will open a window where you can give comments and other settings, Click on Save and Run.

It will take some seconds or minute to export and publish artifact based on your solution size.As you can see in below image Agent job run successfully and it produced 1 artifact. you can click on that link and navigate to the exported solution.

Now we need create a release pipeline for importing the solution in UAT environment. Navigate to the Release click on New pipeline.

Click on Empty job template.

Here we can add multiple stages. But i am using only one stage for this demonstration which is UAT. After giving stage name close it from X on right corner.

Now we need to add Artifact which we produced in the last build pipeline. Choose Project, Source(from Build Pipeline which is SolutionMove-CI), Build Version(using the latest, you can have multiple build, but here you need to select which build you want use for the release),Source Alias(by default it will take based on source, renamed it as Dev)

Again link your UAT credential with your pipeline using Variable group.

After linking,Now we need to add Task(select your stage where you want to add task if you have multiple stages it will show you when you will click on Task button), so i have on one stage which is UAT so just click on it.

Add “Power DevOps Tool Installer” and “Import Solution“. Specify the connection string and solution file location(browse to artifact folder where the solution is exported and select the solution Zip File). Below you can see other operation which you can perform when import will take place. Just click on save. After that Create release button will not be read only.you can click on it.

It will open window which is shown in below image. Select the stage and click on create.

Once release is created , we need to deploy it. Navigate to the +Deploy button, we can deploy current stage as well as multiple stage at a time. It will open one more window where you can give your comment and click on Deploy button.