Task-5 _ Call the Powerautomate on click on the approve button and Send an Email

-

 

Call the Powerautomate on click on the approve button and Send an Email

Call the Powerautomate on click on the approve button and send mail to parents.

User Story: -

When we click on the Approve button in the student Entity record then a confirmation email should be sent to the respective student, do this operation using powerautomate.

Sudo code: -

  • Create an Approve button for custom entity using Ribbon work bench in XRM Toolbox. 
    • Create a solution for custom entity ribbon workbench. 
    • Add the required entity meta data to the solution. 
    • Use this solution in Ribbon workbench to create buttons and publish it in the entity.
  • Create a Power automate for that particular entity, with triggering point as a HTTP Request.
  • Retrieve the email to a variable from HTTP Request body.
  • Check the null condition for email.
  • If email is present then send email.
  • If email is not present then stop the power automate.
  • After saving the power automate we will get the URL form triggering the power automate.
  • Now create a JavaScript file, with a function to trigger the power automate.
    • In that JavaScript code, create XML HTTP request.
    • open the connection with POST method with the given power automate URL.
    • retrieve the email and name from the formContext.
    • Create a body object with name and email and convert into JSON object.
    • Send the HTTP request.
  • Create a web resource with JavaScript code.
  • Use this JavaScript web resource to Action function for the Approve button using Ribbon workbench in XRM Toolbox.

JavaScript code: -

function CallPowerAutomate(primaryControl) {
    var formContext = primaryControl;
    var id = formContext.data.entity.getId().replace("{", "").replace("}", "");

    Xrm.WebApi.online.retrieveRecord("naree_student", id, "?$select=naree_name&$expand=naree_Parent($select=emailaddress1,fullname)").then(
        function success(result) {
            var naree_name = result["naree_name"];
            if (result.hasOwnProperty("naree_Parent")) {
                var naree_Parent_emailaddress1 = result["naree_Parent"]["emailaddress1"];
                var naree_Parent_fullname = result["naree_Parent"]["fullname"];

                if (naree_Parent_emailaddress1 != null) {
                    var Url = "Power automate generated URL";
                    var httpReq = new XMLHttpRequest();
                    httpReq.open("POST", Url);
                    httpReq.setRequestHeader("Content-Type", "application/json; charset=UTF-8");

                    var body = JSON.stringify({ "name": naree_name, "email": naree_Parent_emailaddress1, "Parent Name": naree_Parent_fullname })
                    httpReq.send(body);
                }
            }
        },
        function (error) {
            Xrm.Utility.alertDialog(error.message);


        }
    );
   
}







Comments

Post a Comment

Popular posts from this blog

How to create an Azure AD(Active Directory) and create an application to connect Dynamics 365 from console application

-
Image
 Steps: - Video link :  How to connect console application to connect Dynamics 1. Open Azure Portal 2. Login with your CRM login Credentials 3. open Microsoft Entra ID 4. click App registrations. 5. select New registration 6. After Registering the application, you will get the Application Id (Client Id)..etc save the details. 7. Select App Permissions, click on Add permission, then select Dynamics 365. 8. Grant permissions to the created permissions. 9. Select Client & secrets, then click on New client secret, and provide the appropriate details. 10. After creating a secret you should copy the secret value, otherwise you cannot copy it later. 11. Open Power portal administrator, login with your CRM credentials. 12. Select your required environment, open users. 13. select application users, then select +New app user. 14. click on "Add an app", then select the created Azure application. 15. Provide the security role as System administrator, because it has the highest privil
Read more

Task -6 JavaScript , Regular expressions

-
Image
User Story: -   On Change of phone number, need to validate, it should contain only numbers and + symbol if any other characters are there then show the error "Invalid value, please enter only numbers or +" Sudo Code: -   1. Create a javascript function with executionContext as a parameter. 2. Retrieve the phone number field value. 3. Create a pattern to check the value contains numbers and + only by using javascript regular expressions. 4. Using "test" string method check the requirement, it returns true or false. 5. If the return value is false then set Notification to the phone number field using setNotification control method. 6. If the return value is true then clear Notification to the phone number field using clear Notification control method. 7. Create a web resource using this javascript code and publish it. 8. Create an OnChange event to the phone number field using this web resource and function. Show Error message if mobile number field contains charact
Read more

Task_1 JavaScript

-
Image
 User Story In the Case entity, based on Incident type selection, filter the Case category using the category-Incident master entity  Sudo Code Tasks 1. Create Incident type entity -- 30 mins 2. Create a Case category entity 3. Create a Category-Incident master entity 4. In case entity provide the lookup of the Incident type and Case category. 5. On change of Incident type __ form type 1    Read the selected incident type      Read the case category    If the Incident type is null then disable the case category    If the Incident type is not null then enable the case category => Also apply this code in the OnLoad event. 6. Create Incident type and case category lookup fields in Case Entity. 7. Prepare fetchXML from the advanced find view to get the case categories based on incident type  8. On Change event of the incident field, if the Incident field is not null Create a custom filter view to show retrieved case categories and apply it to the case category lookup field. 8. OnChange
Read more