![\"\"](\"https:\/\/cm-edgetun.pages.dev\/en-us\/power-platform\/blog\/wp-content\/uploads\/2024\/06\/Icm-OneNote-flow.png\"\/)
<\/p>\nToday, I’ll describe another flow that we use internally and describe some of the advanced concepts used in the flow.<\/p>\n
Internally at Microsoft, we use a system call Incident Call Manager (ICM) to handle live site servicing rotation and service outage\u00a0notifications. Mulitple Microsoft Teams use ICM for the devOps\/Live site rotations with different engineers on call for differing periods.\u00a0As part of handling service outages and investigations, frequently we need to look up the engineers on call for a different service to get help. The Flows team (as is true for mulitple teams) needs to interact with mutliple partner teams while investigating incidents. Its pretty common for us to lookup who the onCall engineer is for a particular service – the flow I describe makes saves time for our OnCall engineers by updating an OneNote with the onCall lists for multiple teams each week.<\/p>\n
The flow I describe users a Custom API that’s published internally within the Microsoft tenant to talk to the ICM service, builds up a HTML table of all partner teams we typically interact with and updates a section in One Note weekly so we have a handy place to look up the onCall engineers for the team we interact with.<\/p>\n
The flow is shown below<\/p>\n
<\/p>\n
The flow calls the ICM connector mutliple times, gets the onCalls for a particular service\u00a0 – you can see in the picture above that calls are made for the Flow Service followed by PowerApps RP, and then API Hubs service and so on.<\/p>\n
Note that there’s a compose action that processes the results of the JSON object returned by the connector for each ICM service – as shown below – I do that becuase I needed to transform the JSON object returned by the service to add an addiontal field. Take the flow team snip below<\/p>\n
<\/p>\n
The JSON object returned by the ICM connector looks like this – Notice that I’m pulling\u00a0“TeamName”, “Email” and “Name” fields from mutliple JSON objects in the original payload and converting it to a new JSON object that only has these fields that I’m interested in as shown below. – Lets call these JSON objects the full ICM Objects. At the end of the flow, I have a bunch of these JSON objects for different services and I need to process them to create a HTML table.<\/p>\n
<\/p>\n
I use the handy union function as describe here(https:\/\/docs.microsoft.com\/en-us\/azure\/logic-apps\/logic-apps-workflow-definition-language) in the compose card at the end to create\u00a0an single array of these JSON objects to parse to the create HTML table<\/p>\n
\u00a0<\/p>\n
Then I use the CreateHtML to create a html table of the JSON objects and write to a One Note section. Noe that OneNote requires a html snipped to properly create and name the title of the page – Like so<\/p>\n
<\/p>\n
At the end – In One note you see these cool entries every week!<\/p>\n
![](\"https:\/\/cm-edgetun.pages.dev\/en-us\/power-platform\/blog\/wp-content\/uploads\/2024\/06\/flow_raj.png\"\/)
<\/p>\n
I hope this was useful, important topics covered here:<\/p>\n
How to extend a JSON object in building the full onCall JSON object.\u00a0<\/p>\n
Combining JSON objects using the union function and how to create sections in OneNote.<\/p>\n
As always, if you have comments, please leave them in the comments below, in our community<\/a> or tweet us on twitter<\/a>!<\/p>\n","protected":false},"excerpt":{"rendered":" Today, I’ll describe another flow that we use internally and describe some of the advanced concepts used in the flow. Internally at Microsoft, we use a system call Incident Call Manager (ICM) to handle live site servicing rotation and service outage notifications. The flow I describe users a Custom API that’s published internally within the Microsoft tenant to talk to the ICM service, builds up a HTML table of all partner teams we typically interact with and updates a section in One Note weekly so we have a handy place to look up the onCall engineers for the team with whom we interact.<\/p>\n","protected":false},"author":360,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"ms_queue_id":[],"ep_exclude_from_search":false,"_classifai_error":"","_classifai_text_to_speech_error":"","_alt_title":"","ms-ems-related-posts":[],"footnotes":""},"audience":[3378],"content-type":[],"job-role":[],"product":[3474],"property":[],"topic":[3435],"coauthors":[2929],"class_list":["post-110895","post","type-post","status-publish","format-standard","hentry","audience-it-professional","product-power-automate","topic-operations"],"yoast_head":"\n