Hi,
bit of a newbie here and struggling to understand the finer points of flow.
I have a teams channel that takes in events from a process and I want to get that data into an excel sheet for auditing use.
so far I have worked out this much.
which gives me a text string like this
idcontentTypecontentUrlcontentnamethumbnailUrlbe28b51c80d84790a0c110770c7a4473
application/vnd.microsoft.teams.card.o365connector{ "summary": "Jamf ", "text":
"", "title": "Test message", "themeColor": "0072C6", "sections": [ { "text":
"<p>Testing is happening</p>", "facts": [ { "name": "Computer Name:", "value":
"<p>my computer</p>" }, { "name": "Serial:", "value":
"<p>abcgabcdabcd</p>" }, { "name": "User:", "value": "<p>auser</p>" } ],
"title": "", "activityTitle": "", "activitySubtitle": "", "activityText": "",
"markdown": true, "startGroup": false } ] }
but I have absolutely no idea how to pull out the values I need, these being; Computer Name, Serial and user.
any help would be massively appreciated as everything I've tried gives no output or fails..
Solved! Go to Solution.
You need to use Parse JSON to extract the values. Here it is
Initialise a string and assig the JSON value
Next we need JSON Parser (Couple of them)
The above schema is as follows:
If you liked my response, please consider giving it a thumbs up
Proud to be a Flownaut!
Learn more from my blogSo many thanks to @abm it's now all working. I'll document it here in case anyone else wants a similar thing
As shown above the input data is a team message in HTML format giving four parameters, in this case computername, serial, user and a reason and I wanted to push that into an excel sheet along with the date.
Started with initialize a variable
Then need to parse the JSON
below is the schema for this one
{
"type": "object",
"properties": {
"@@odata.type": {
"type": "string"
},
"replyToId": {},
"etag": {
"type": "string"
},
"messageType": {
"type": "string"
},
"createdDateTime": {
"type": "string"
},
"lastModifiedDateTime": {},
"deletedDateTime": {},
"subject": {},
"summary": {
"type": "string"
},
"importance": {
"type": "string"
},
"locale": {
"type": "string"
},
"webUrl": {
"type": "string"
},
"policyViolation": {},
"id": {
"type": "string"
},
"from": {
"type": "object",
"properties": {
"device": {},
"user": {},
"conversation": {},
"application": {
"type": "object",
"properties": {
"id": {
"type": "string"
},
"displayName": {
"type": "string"
},
"applicationIdentityType": {
"type": "string"
}
}
}
}
},
"body": {
"type": "object",
"properties": {
"contentType": {
"type": "string"
},
"content": {
"type": "string"
}
}
},
"attachments": {
"type": "array",
"items": {
"type": "object",
"properties": {
"id": {
"type": "string"
},
"contentType": {
"type": "string"
},
"contentUrl": {},
"content": {
"type": "string"
},
"name": {},
"thumbnailUrl": {}
},
"required": [
"id",
"contentType",
"contentUrl",
"content",
"name",
"thumbnailUrl"
]
}
},
"mentions": {
"type": "array"
},
"reactions": {
"type": "array"
}
}
}
Then parse JSON again to pull out the attachment section
and below is the Schema for this one
{
"type": "array",
"items": {
"type": "object",
"properties": {
"content": {
"type": "string"
},
"id": {
"type": "string"
},
"contentType": {
"type": "string"
},
"contentUrl": {},
"name": {},
"thumbnailUrl": {}
},
"required": [
"id",
"contentType",
"contentUrl",
"content",
"name",
"thumbnailUrl"
]
}
}
and now the really good bit...
an apply to each is next as there is an array to pull apart
The two schemas are here
parse_JSON_3 schema
{
"type": "object",
"properties": {
"summary": {
"type": "string"
},
"text": {
"type": "string"
},
"title": {
"type": "string"
},
"themeColor": {
"type": "string"
},
"sections": {
"type": "array",
"items": {
"type": "object",
"properties": {
"text": {
"type": "string"
},
"facts": {
"type": "array",
"items": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string"
}
},
"required": [
"name",
"value"
]
}
},
"title": {
"type": "string"
},
"activityTitle": {
"type": "string"
},
"activitySubtitle": {
"type": "string"
},
"activityText": {
"type": "string"
},
"markdown": {
"type": "boolean"
},
"startGroup": {
"type": "boolean"
}
},
"required": [
"text",
"facts",
"title",
"activityTitle",
"activitySubtitle",
"activityText",
"markdown",
"startGroup"
]
}
}
}
}
parse_json_4 schema
{
"type": "array",
"items": {
"type": "object",
"properties": {
"text": {
"type": "string"
},
"facts": {
"type": "array",
"items": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string"
}
},
"required": [
"name",
"value"
]
}
},
"title": {
"type": "string"
},
"activityTitle": {
"type": "string"
},
"activitySubtitle": {
"type": "string"
},
"activityText": {
"type": "string"
},
"markdown": {
"type": "boolean"
},
"startGroup": {
"type": "boolean"
}
},
"required": [
"text",
"facts",
"title",
"activityTitle",
"activitySubtitle",
"activityText",
"markdown",
"startGroup"
]
}
}
and now the actual values can be pulled from the data and tidied up for pushing to excel
Firstly a parseJSON to get the Facts section
the schema is here
{
"type": "array",
"items": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string"
}
},
"required": [
"name",
"value"
]
}
}
then four Compose sections, one for each of the data values we have. These are the items in an array and are html formatted so have tags to remove <p> and </p>. Name the compose blocks as per the item they are then use this in the expression;
This now gives us all the four required values ready for use
The excel sheet needs to be premade with the a table setup for the columns required.
We've added the data using an Expression directly
then mapped the compose outputs
because we named the outputs they can easily be mapped as shown below
Note that the name set shows above the output
And that's it. now when a message comes into teams the sheet is populated
Could you post your run time history details of "When a new channel message is added"? Open the run history expand the first step and send me the details of output.
If you liked my response, please consider giving it a thumbs up
Proud to be a Flownaut!
Learn more from my blogThanks for offering to help. I think you mean this;
{
"@odata.type": "#microsoft.graph.chatMessage",
"replyToId": null,
"etag": "1584097207615",
"messageType": "message",
"createdDateTime": "2020-03-13T11:00:07.615Z",
"lastModifiedDateTime": null,
"deletedDateTime": null,
"subject": null,
"summary": "Jamf ",
"importance": "normal",
"locale": "en-us",
"webUrl": "https://teams.microsoft.com/l/message/19%3A595359cc14b042bf98a8e7954cd5f2f6%40thread.tacv2/1584097207615?groupId=b147e627-zzzz-zzzz-zzzz-zzzzbcda017b&tenantId=zzzzzzzz-zzzz-zzzz-zzzz-zzzze760c89a&createdTime=1584097207615&parentMessageId=1234123412345",
"policyViolation": null,
"id": "1584097207615",
"from": {
"device": null,
"user": null,
"conversation": null,
"application": {
"id": "203azzzz-zzzz-zzzz-zzz-zzzzf960b6b2",
"displayName": "JamfLogging",
"applicationIdentityType": "office365Connector"
}
},
"body": {
"contentType": "html",
"content": "<attachment id=\"17729b674a514bbfad72b8e13df0830c\"></attachment>"
},
"attachments": [
{
"id": "17729b674a514bbfad72b8e13df0830c",
"contentType": "application/vnd.microsoft.teams.card.o365connector",
"contentUrl": null,
"content": "{\r\n \"summary\": \"Jamf \",\r\n \"text\": \"\",\r\n \"title\": \"Admin Elevation\",\r\n \"themeColor\": \"0072C6\",\r\n \"sections\": [\r\n {\r\n \"text\": \"<p>Admin elevator was run</p>\",\r\n \"facts\": [\r\n {\r\n \"name\": \"Computer Name:\",\r\n \"value\": \"<p>Tom MacBook Pro</p>\"\r\n },\r\n {\r\n \"name\": \"Serial:\",\r\n \"value\": \"<p>abcdabcdabcd</p>\"\r\n },\r\n {\r\n \"name\": \"User:\",\r\n \"value\": \"<p>tom</p>\"\r\n },\r\n {\r\n \"name\": \"Reason:\",\r\n \"value\": \"<p>App install</p>\"\r\n }\r\n ],\r\n \"title\": \"\",\r\n \"activityTitle\": \"\",\r\n \"activitySubtitle\": \"\",\r\n \"activityText\": \"\",\r\n \"markdown\": true,\r\n \"startGroup\": false\r\n }\r\n ]\r\n}",
"name": null,
"thumbnailUrl": null
}
],
"mentions": [],
"reactions": []
}
You need to use Parse JSON to extract the values. Here it is
Initialise a string and assig the JSON value
Next we need JSON Parser (Couple of them)
The above schema is as follows:
If you liked my response, please consider giving it a thumbs up
Proud to be a Flownaut!
Learn more from my blogWow! Thanks @abm I shall try this straight away I would never have worked that out.
Hi @abm. I'm making progress but I have a feeling you have pasted for each2 in twice and missed for each 1 . I just can't get my inputs to show the names you have and the json looks the same for both.
@abm I'm really stuck! I've spent hours trying to achieve the state shown here
but I can't ever get an input of sections let alone a content of Facts.
So many thanks to @abm it's now all working. I'll document it here in case anyone else wants a similar thing
As shown above the input data is a team message in HTML format giving four parameters, in this case computername, serial, user and a reason and I wanted to push that into an excel sheet along with the date.
Started with initialize a variable
Then need to parse the JSON
below is the schema for this one
{
"type": "object",
"properties": {
"@@odata.type": {
"type": "string"
},
"replyToId": {},
"etag": {
"type": "string"
},
"messageType": {
"type": "string"
},
"createdDateTime": {
"type": "string"
},
"lastModifiedDateTime": {},
"deletedDateTime": {},
"subject": {},
"summary": {
"type": "string"
},
"importance": {
"type": "string"
},
"locale": {
"type": "string"
},
"webUrl": {
"type": "string"
},
"policyViolation": {},
"id": {
"type": "string"
},
"from": {
"type": "object",
"properties": {
"device": {},
"user": {},
"conversation": {},
"application": {
"type": "object",
"properties": {
"id": {
"type": "string"
},
"displayName": {
"type": "string"
},
"applicationIdentityType": {
"type": "string"
}
}
}
}
},
"body": {
"type": "object",
"properties": {
"contentType": {
"type": "string"
},
"content": {
"type": "string"
}
}
},
"attachments": {
"type": "array",
"items": {
"type": "object",
"properties": {
"id": {
"type": "string"
},
"contentType": {
"type": "string"
},
"contentUrl": {},
"content": {
"type": "string"
},
"name": {},
"thumbnailUrl": {}
},
"required": [
"id",
"contentType",
"contentUrl",
"content",
"name",
"thumbnailUrl"
]
}
},
"mentions": {
"type": "array"
},
"reactions": {
"type": "array"
}
}
}
Then parse JSON again to pull out the attachment section
and below is the Schema for this one
{
"type": "array",
"items": {
"type": "object",
"properties": {
"content": {
"type": "string"
},
"id": {
"type": "string"
},
"contentType": {
"type": "string"
},
"contentUrl": {},
"name": {},
"thumbnailUrl": {}
},
"required": [
"id",
"contentType",
"contentUrl",
"content",
"name",
"thumbnailUrl"
]
}
}
and now the really good bit...
an apply to each is next as there is an array to pull apart
The two schemas are here
parse_JSON_3 schema
{
"type": "object",
"properties": {
"summary": {
"type": "string"
},
"text": {
"type": "string"
},
"title": {
"type": "string"
},
"themeColor": {
"type": "string"
},
"sections": {
"type": "array",
"items": {
"type": "object",
"properties": {
"text": {
"type": "string"
},
"facts": {
"type": "array",
"items": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string"
}
},
"required": [
"name",
"value"
]
}
},
"title": {
"type": "string"
},
"activityTitle": {
"type": "string"
},
"activitySubtitle": {
"type": "string"
},
"activityText": {
"type": "string"
},
"markdown": {
"type": "boolean"
},
"startGroup": {
"type": "boolean"
}
},
"required": [
"text",
"facts",
"title",
"activityTitle",
"activitySubtitle",
"activityText",
"markdown",
"startGroup"
]
}
}
}
}
parse_json_4 schema
{
"type": "array",
"items": {
"type": "object",
"properties": {
"text": {
"type": "string"
},
"facts": {
"type": "array",
"items": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string"
}
},
"required": [
"name",
"value"
]
}
},
"title": {
"type": "string"
},
"activityTitle": {
"type": "string"
},
"activitySubtitle": {
"type": "string"
},
"activityText": {
"type": "string"
},
"markdown": {
"type": "boolean"
},
"startGroup": {
"type": "boolean"
}
},
"required": [
"text",
"facts",
"title",
"activityTitle",
"activitySubtitle",
"activityText",
"markdown",
"startGroup"
]
}
}
and now the actual values can be pulled from the data and tidied up for pushing to excel
Firstly a parseJSON to get the Facts section
the schema is here
{
"type": "array",
"items": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"value": {
"type": "string"
}
},
"required": [
"name",
"value"
]
}
}
then four Compose sections, one for each of the data values we have. These are the items in an array and are html formatted so have tags to remove <p> and </p>. Name the compose blocks as per the item they are then use this in the expression;
This now gives us all the four required values ready for use
The excel sheet needs to be premade with the a table setup for the columns required.
We've added the data using an Expression directly
then mapped the compose outputs
because we named the outputs they can easily be mapped as shown below
Note that the name set shows above the output
And that's it. now when a message comes into teams the sheet is populated
It's time for the SECOND Power Apps Copilot Coffee Chat featuring the Copilot Studio product team, which will be held LIVE on April 3, 2024 at 9:30 AM Pacific Daylight Time (PDT). This is an incredible opportunity to connect with members of the Copilot Studio product team and ask them anything about Copilot Studio. We'll share our special guests with you shortly--but we want to encourage to mark your calendars now because you will not want to miss the conversation. This live event will give you the unique opportunity to learn more about Copilot Studio plans, where we’ll focus, and get insight into upcoming features. We’re looking forward to hearing from the community, so bring your questions! TO GET ACCESS TO THIS EXCLUSIVE AMA: Kudo this post to reserve your spot! Reserve your spot now by kudoing this post. Reservations will be prioritized on when your kudo for the post comes through, so don't wait! Click that "kudo button" today. Invitations will be sent on April 2nd.Users posting Kudos after April 2nd at 9AM PDT may not receive an invitation but will be able to view the session online after conclusion of the event. Give your "kudo" today and mark your calendars for April 3, 2024 at 9:30 AM PDT and join us for an engaging and informative session!
TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users. With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips! THIS WEEK'S TIP: Unlocking Achievements and Earning BadgesAcross the Communities, you'll see badges on users profile that recognize and reward their engagement and contributions. These badges each signify a different achievement--and all of those achievements are available to any Community member! If you're a seasoned pro or just getting started, you too can earn badges for the great work you do. Check out some details on Community badges below--and find out more in the detailed link at the end of the article! A Diverse Range of Badges to Collect The badges you can earn in the Community cover a wide array of activities, including: Kudos Received: Acknowledges the number of times a user’s post has been appreciated with a “Kudo.”Kudos Given: Highlights the user’s generosity in recognizing others’ contributions.Topics Created: Tracks the number of discussions initiated by a user.Solutions Provided: Celebrates the instances where a user’s response is marked as the correct solution.Reply: Counts the number of times a user has engaged with community discussions.Blog Contributor: Honors those who contribute valuable content and are invited to write for the community blog. A Community Evolving Together Badges are not only a great way to recognize outstanding contributions of our amazing Community members--they are also a way to continue fostering a collaborative and supportive environment. As you continue to share your knowledge and assist each other these badges serve as a visual representation of your valuable contributions. Find out more about badges in these Community Support pages in each Community: All About Community Badges - Power Apps CommunityAll About Community Badges - Power Automate CommunityAll About Community Badges - Copilot Studio CommunityAll About Community Badges - Power Pages Community
TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users. With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips! This Week's Tip: Power Up Your Profile! 🚀 It's where every Community member gets their start, and it's essential that you keep it updated! Your Community User Profile is how you're able to get messages, post solutions, ask questions--and as you rank up, it's where your badges will appear and how you'll be known when you start blogging in the Community Blog. Your Community User Profile is how the Community knows you--so it's essential that it works the way you need it to! From changing your username to updating contact information, this Knowledge Base Article is your best resource for powering up your profile. Password Puzzles? No Problem! Find out how to sync your Azure AD password with your community account, ensuring a seamless sign-in. No separate passwords to remember! Job Jumps & Email Swaps Changed jobs? Got a new email? Fear not! You'll find out how to link your shiny new email to your existing community account, keeping your contributions and connections intact. Username Uncertainties Unraveled Picking the perfect username is crucial--and sometimes the original choice you signed up with doesn't fit as well as you may have thought. There's a quick way to request an update here--but remember, your username is your community identity, so choose wisely. "Need Admin Approval" Warning Window? If you see this error message while using the community, don't worry. A simple process will help you get where you need to go. If you still need assistance, find out how to contact your Community Support team. Whatever you're looking for, when it comes to your profile, the Community Account Support Knowledge Base article is your treasure trove of tips as you navigate the nuances of your Community Profile. It’s the ultimate resource for keeping your digital identity in tip-top shape while engaging with the Power Platform Community. So, dive in and power up your profile today! 💪🚀 Community Account Support | Power Apps Community Account Support | Power AutomateCommunity Account Support | Copilot Studio Community Account Support | Power Pages
In our 2nd installment of this new ongoing feature in the Community, we're thrilled to announce that Chris Piasecki is our Super User of the Month for March 2024. If you've been in the Community for a while, we're sure you've seen a comment or marked one of Chris' helpful tips as a solution--he's been a Super User for SEVEN consecutive seasons! Since authoring his first reply in April 2020 to his most recent achievement organizing the Canadian Power Platform Summit this month, Chris has helped countless Community members with his insights and expertise. In addition to being a Super User, Chris is also a User Group leader, Microsoft MVP, and a featured speaker at the Microsoft Power Platform Conference. His contributions to the new SUIT program, along with his joyous personality and willingness to jump in and help so many members has made Chris a fixture in the Power Platform Community. When Chris isn't authoring solutions or organizing events, he's actively leading Piasecki Consulting, specializing in solution architecture, integration, DevOps, and more--helping clients discover how to strategize and implement Microsoft's technology platforms. We are grateful for Chris' insightful help in the Community and look forward to even more amazing milestones as he continues to assist so many with his great tips, solutions--always with a smile and a great sense of humor.You can find Chris in the Community and on LinkedIn. Thanks for being such a SUPER user, Chris! 💪 🌠
TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users. With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!This Week: Community Ranks--Moving from "Member" to "Community Champion" Have you ever wondered how your fellow community members ascend the ranks within our community? What sets apart an Advocate from a Helper, or a Solution Sage from a Community Champion? In today’s #TuesdayTip, we’re unveiling the secrets and sharing tips to help YOU elevate your ranking—and why it matters to our vibrant communities. Community ranks serve as a window into a member’s role and activity. They celebrate your accomplishments and reveal whether someone has been actively contributing and assisting others. For instance, a Super User is someone who has been exceptionally helpful and engaged. Some ranks even come with special permissions, especially those related to community management. As you actively participate—whether by creating new topics, providing solutions, or earning kudos—your rank can climb. Each time you achieve a new rank, you’ll receive an email notification. Look out for the icon and rank name displayed next to your username—it’s a badge of honor! Fun fact: Your Community Engagement Team keeps an eye on these ranks, recognizing the most passionate and active community members. So shine brightly with valuable content, and you might just earn well-deserved recognition! Where can you see someone’s rank? When viewing a post, you’ll find a member’s rank to the left of their name.Click on a username to explore their profile, where their rank is prominently displayed. What about the ranks themselves? New members start as New Members, progressing to Regular Visitors, and then Frequent Visitors.Beyond that, we have a categorized system: Kudo Ranks: Earned through kudos (teal icons).Post Ranks: Based on your posts (purple icons).Solution Ranks: Reflecting your solutions (green icons).Combo Ranks: These orange icons combine kudos, solutions, and posts. The top ranks have unique names, making your journey even more exciting! So dive in, collect those kudos, share solutions, and let’s see how high you can rank! 🌟 🚀 Check out the Using the Community boards in each of the communities for more helpful information! Power Apps, Power Automate, Copilot Studio & Power Pages
We know many of you visit the Power Platform Communities to ask questions and receive answers. But do you know that many of our best answers and solutions come from Community members who are super active, helping anyone who needs a little help getting unstuck with Business Applications products? We call these dedicated Community members Super Users because they are the real heroes in the Community, willing to jump in whenever they can to help! Maybe you've encountered them yourself and they've solved some of your biggest questions. Have you ever wondered, "Why?"We interviewed several of our Super Users to understand what drives them to help in the Community--and discover the difference it has made in their lives as well! Take a look in our gallery today: What Motivates a Super User? - Power Platform Community (microsoft.com)
User | Count |
---|---|
55 | |
50 | |
27 | |
25 | |
24 |
User | Count |
---|---|
65 | |
47 | |
45 | |
36 | |
33 |