{"id":600,"date":"2024-02-05T11:34:51","date_gmt":"2024-02-05T11:34:51","guid":{"rendered":"https:\/\/poiseddevelopers.com\/reality-tech\/?p=600"},"modified":"2024-04-26T10:11:24","modified_gmt":"2024-04-26T10:11:24","slug":"creating-logs-for-every-action-in-power-automate","status":"publish","type":"post","link":"https:\/\/poiseddevelopers.com\/reality-tech\/creating-logs-for-every-action-in-power-automate\/","title":{"rendered":"Creating Logs for Every Action in Power Automate"},"content":{"rendered":"

The process of \u201ccreating logs for Power Automate instances\u201d involves systematically recording and archiving essential information about each step and action taken during the execution of automated workflows. This comprehensive log becomes an asset, offering users insights into the intricacies of their workflows, enabling efficient troubleshooting, and facilitating performance analysis.<\/p>\n

In this blog post, we explore the significance of creating logs for Power Automate instances and how it transforms into a practice for users seeking a deeper understanding of their automated processes. Imagine having a detailed record of when a workflow starts, the events that trigger its execution, the data it processes, and the outcomes it produces\u2014all neatly documented for reference. This level of visibility not only enhances troubleshooting capabilities but also empowers users to optimize and refine their workflows for peak efficiency.<\/p>\n

Step: 1\u00a0<\/strong>First Add the \u201cWhen an item is created action and add the Site Address and List Name.<\/p>\n

 <\/p>\n

\"img-01\"<\/p>\n

 <\/p>\n

Step: 2\u00a0<\/strong>Next, add another Compose action to retrieve the workflow URL. Add the expression for get the URL in SharePoint Online.<\/p>\n

We need to concat following string in the compose action<\/p>\n

String 1: Environment URL (Region needs to be changed as per tenant configuration)
https:\/\/asia.flow.microsoft.com\/manage\/environments<\/p>\n

String 2: Environment Name
workflow().tags.environmentName<\/p>\n

String 3: \u201cFlows\u201d<\/p>\n

String 4:WorkFlow Name
workflow().name<\/p>\n

String 5: \u201cRuns\u201d<\/p>\n

String 6: Workflow Run Name:
workflow().run.name<\/p>\n

concat(\u2018https:\/\/asia.flow.microsoft.com\/manage\/environments\/\u2019, workflow().tags.environmentName,\u2019\/flows\/\u2019, workflow().name, \u2018\/runs\/\u2019, workflow().run.name)<\/div>\n
\"img-02\"<\/div>\n
Step: 3<\/strong>\u00a0Add the \u201cCreate Item\u201d action and include the site name and site URL for when users want to upload logs to the list in SharePoint Online.<\/div>\n
Title:<\/strong>\u00a0Include the dynamic \u201cTitle\u201d obtained from the \u201cWhen an item is created\u201d action.<\/div>\n
WFItem URL:<\/strong>\u00a0Add the dynamic value \u201cOutput\u201d obtained from the \u201cCompose 2\u201d action.<\/div>\n
Stage:<\/strong>\u00a0Here is the manually added \u201cPending by Stage 1.\u201d<\/div>\n
Assigned To:<\/strong>\u00a0Enter the Assigned To user email.<\/div>\n
Associated List ID:<\/strong>\u00a0Add the dynamic \u201cID\u201d obtained from the \u201cWhen an item is created.\u201d<\/div>\n
Status:<\/strong>\u00a0Include the dynamic \u201cStatus Value\u201d obtained from the \u201cWhen an item is created.\u201d<\/div>\n
Created By Original Claims:\u00a0<\/strong>Add the dynamic \u201cCreated by Claims\u201d obtained from the \u201cWhen an item is created.\u201d<\/div>\n
Modified By Original Claims:\u00a0<\/strong>Add the dynamic \u201cModified by Claims\u201d obtained from the \u201cWhen an item is created.\u201d<\/div>\n
<\/div>\n
<\/div>\n
<\/div>\n
\"img-03\"<\/div>\n
<\/div>\n
Step: 4<\/strong>\u00a0Add the \u201cStart and wait for approval\u201d action.<\/div>\n
\n
    \n
  • Approval type: Add the approval type which you want to choose in the choice value.<\/li>\n
  • Title: Added the Title<\/li>\n
  • Assigned to: Added the username which you want to send for approval.<\/li>\n<\/ul>\n<\/div>\n

     <\/p>\n

    \"img-04\"<\/p>\n

     <\/p>\n

    Step: 5\u00a0<\/strong>Next, include the condition action and add the dynamic \u201cOutcome\u201d obtained from the \u201cStart and Wait for Approval\u201d action. Ensure it is equal to \u201cApprove,\u201d as shown in the screenshot below.<\/p>\n

     <\/p>\n

    \"img-05\"<\/p>\n

     <\/p>\n

    Step: 6\u00a0<\/strong>Again, add the \u201cCreate Item\u201d action in both sides \u201cIf Yes\u201d and \u201cIf No.\u201d<\/p>\n

    Approve By Display Name:\u00a0<\/strong>Add the dynamic content \u201cResponder display name\u201d obtained from the \u201cStart and Wait for Approval\u201d action. This action is automatically applied in the \u201cApply to each\u201d loop.<\/p>\n

    Comments:\u00a0<\/strong>Add the dynamic content \u201cResponses Comments\u201d obtained from the \u201cStart and wait for Approval\u201d action.<\/p>\n

     <\/p>\n

    \"img-06\"<\/p>\n

     <\/p>\n

    Step: 7\u00a0<\/strong>Create a new entry in the SharePoint list and verify the flow.<\/p>\n

      \n
    • Below is a screenshot of the Workflow History list, where we create a log. It displays all the column values that we add in the \u201cCreate Item\u201d action in Power Automate.<\/li>\n<\/ul>\n

       <\/p>\n

      \"img-07\"<\/p>\n","protected":false},"excerpt":{"rendered":"

      The process of \u201ccreating logs for Power Automate instances\u201d involves systematically recording and archiving essential information about each step and action taken during the execution of automated workflows. This comprehensive log becomes an asset, offering users insights into the intricacies of their workflows, enabling efficient troubleshooting, and facilitating performance analysis. In this blog post, we […]<\/p>\n","protected":false},"author":4,"featured_media":603,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[19],"tags":[],"class_list":["post-600","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-power-automate"],"acf":[],"_links":{"self":[{"href":"https:\/\/poiseddevelopers.com\/reality-tech\/wp-json\/wp\/v2\/posts\/600","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/poiseddevelopers.com\/reality-tech\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/poiseddevelopers.com\/reality-tech\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/poiseddevelopers.com\/reality-tech\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/poiseddevelopers.com\/reality-tech\/wp-json\/wp\/v2\/comments?post=600"}],"version-history":[{"count":8,"href":"https:\/\/poiseddevelopers.com\/reality-tech\/wp-json\/wp\/v2\/posts\/600\/revisions"}],"predecessor-version":[{"id":666,"href":"https:\/\/poiseddevelopers.com\/reality-tech\/wp-json\/wp\/v2\/posts\/600\/revisions\/666"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/poiseddevelopers.com\/reality-tech\/wp-json\/wp\/v2\/media\/603"}],"wp:attachment":[{"href":"https:\/\/poiseddevelopers.com\/reality-tech\/wp-json\/wp\/v2\/media?parent=600"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/poiseddevelopers.com\/reality-tech\/wp-json\/wp\/v2\/categories?post=600"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/poiseddevelopers.com\/reality-tech\/wp-json\/wp\/v2\/tags?post=600"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}