cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
virakones
Continued Contributor
Continued Contributor

Adaptive Card: How to repeat Fact Set Element within card from a Parse JSON action with multiple objects?

 

Hello, I'm using more custom adaptive cards but just running into some challenges (new to JSON).

 

Background:

 

Recently put together a Powerapp for Teams where a user will submit pricing details to a Lead to approve or edit.

Upon submission, the details will trigger a power automate flow that sends a custom Adaptive Card with text input fields that will look up a record and edit values if an edit is made. Otherwise there is a button to simply approve.

 

Issue:

I have a Parse JSON action that will serialize the request details into an array of objects. Then, I use an 'Apply to Each' action using the body of the Parse JSON action to fill in the Adaptive Card details. However, the Card itself will send multiple times for each object rather than simply repeating the Fact Set element in the card itself, so its just 1 card. Not multiple.

 

Question:

In my template JSON below, how do I bind the Parse JSON output properly to the "$data" property of the Fact Set that I want to repeat below?

 

Tried following the official documentation but just having no luck connecting it to the Parse JSON action.

 

Here is a look at the flow:

Capture.PNG

 

Here is a look at the Card

Capture2.PNG

 

Here is the Adaptive Card Template payload

- In the Fact Set $data property, I would like to bind the Parse JSON data

{
    "type": "AdaptiveCard",
    "body": [
        {
            "type": "Container",
            "style": "emphasis",
            "items": [
                {
                    "type": "ColumnSet",
                    "columns": [
                        {
                            "type": "Column",
                            "items": [
                                {
                                    "type": "TextBlock",
                                    "size": "Large",
                                    "weight": "Bolder",
                                    "text": "@{variables('varClientName')}"
                                }
                            ],
                            "width": "stretch"
                        }
                    ]
                }
            ],
            "bleed": true
        },
        {
            "type": "Container",
            "items": [
                {
                    "type": "ColumnSet",
                    "columns": [
                        {
                            "type": "Column",
                            "items": [
                                {
                                    "type": "TextBlock",
                                    "size": "ExtraLarge",
                                    "text": "@{variables('varOrderDescription')}",
                                    "wrap": true
                                }
                            ],
                            "width": "stretch"
                        }
                    ]
                },
                {
                    "type": "FactSet",
                    "facts": [
                        {
                            "title": "Submitted By",
                            "value": "@{variables('varSubmittedBy')}"
                        },
                        {
                            "title": "Confirm Date",
                            "value": "@{variables('varConfirmationDate')}"
                        },
                        {
                            "title": "In-Hands Date",
                            "value": "@{variables('varInHandsDate')}"
                        },
                        {
                            "title": "Client Budget",
                            "value": "@{variables('varClientBudget')}"
                        },
                        {
                            "title": "Client Price",
                            "value": "@{variables('varClientTargetPrice')}"
                        }
                    ],
                    "separator": true,
                    "height": "stretch"
                },
                {
                    "type": "ColumnSet",
                    "columns": [
                        {
                            "type": "Column",
                            "width": "stretch",
                            "items": [
                                {
                                    "type": "FactSet",
                                    "facts": [
                                        {
                                            "title": "SKU",
                                            "value": "{$root.sku}"
                                        },
                                        {
                                            "title": "Description",
                                            "value": "{$root.description}"
                                        },
                                        {
                                            "title": "Unit Price",
                                            "value": "{$root.unitPrice}"
                                        },
                                        {
                                            "title": "Quantity",
                                            "value": "{$root.quantity}"
                                        },
                                        {
                                            "title": "Production Type",
                                            "value": "{$root.productionType}"
                                        }
                                    ],
                                    "$data": "{$root}" // Bind the Parse JSON data here
                                }
                            ]
                        },
                        {
                            "type": "Column",
                            "width": "stretch",
                            "items": [
                                {
                                    "type": "Input.Text",
                                    "placeholder": "Edit Unit Price",
                                    "maxLength": 1000,
                                    "id": "acEditPrice"
                                }
                            ],
                            "id": "@{items('Apply_to_each')['id']}"
                        }
                    ]
                }
            ]
        },
        {
            "type": "Container",
            "style": "emphasis",
            "items": [
                {
                    "type": "ColumnSet",
                    "columns": [
                        {
                            "type": "Column",
                            "items": [
                                {
                                    "type": "TextBlock",
                                    "horizontalAlignment": "Right",
                                    "text": "Total Price Submitted",
                                    "wrap": true
                                }
                            ],
                            "width": "stretch"
                        },
                        {
                            "type": "Column",
                            "items": [
                                {
                                    "type": "TextBlock",
                                    "weight": "Bolder",
                                    "text": "@{variables('varProductsTotalSum')}"
                                }
                            ],
                            "width": "auto"
                        }
                    ]
                }
            ],
            "bleed": true
        },
        {
            "type": "Container",
            "items": [
                {
                    "type": "ActionSet",
                    "actions": [
                        {
                            "type": "Action.Submit",
                            "title": "Submit",
                            "style": "positive",
                            "data": {
                                "id": "{$root.id}",
                                "action": "approve"
                            }
                        }
                    ]
                }
            ]
        }
    ],
    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
    "version": "1.2",
    "fallbackText": "This card requires Adaptive Cards v1.2 support to be rendered properly."
}

 

2 REPLIES 2
Haris572
Frequent Visitor

Did you get solution for this? I'm having the same issue.

hey @Haris572 

Yes, I managed to find a work around in power automate using Apply to each, an Array variable and Compose. Though this solution was some time back (last year) so I'm not sure if binding is available for power automate adaptive cards in a Teams context these days. For now, you can ignore all the "$root" variables in my previous example - this will be replaced by your dynamic content.

 

Before I begin, I recommend using Designer | Adaptive Cards throughout to test out how your custom card will appear. I kept the card very simple, the FactSet object was enough for my needs. Otherwise, the site is a great resource for building custom Adaptive Cards.

 

My workaround below:

In the sample photo above of the actual card in Teams, the part I wanted repeated were the "products" (from SKU to Production Type)

In the adaptive card template it was the below bolded section of code that I repeated inside a ColumnSet "items" array:

                    "type": "ColumnSet",
                    "columns": [
                        {
                            "type": "Column",
                            "width": "stretch",
                            "items": [
                                {
                                    "type": "FactSet",
                                    "facts": [
                                        {
                                            "title": "SKU",
                                            "value": "dynamic content SKU"
                                        },
                                        {
                                            "title": "Description",
                                            "value": "dynamic content Description"
                                        },
                                        {
                                            "title": "Unit Price",
                                            "value": "dynamic content Unit Price"
                                        },
                                        {
                                            "title": "Quantity",
                                            "value": "dynamic content Quantity"
                                        },
                                        {
                                            "title": "Production Type",
                                            "value": "dynamic content Production Type"
                                        }
                                    ]
                                }
                            ]
                        }

Here, I would have a list of items I want to iterate through, initialize an array variable and appended each item inside an 'Apply to Each' to a group of "FactSet" JSON objects that I recompose back into the card later.
 
Here is a brief step-by-step with a very simple example:
 
1. Have items you want to iterate through to add into a custom adaptive card.
This is your list of items that will give you the dynamic content to work with
 
2. Initialize Array variable action
This will hold the items you iterate through later to compose into JSON that you add back into the custom adaptive card. leave blank.

3. Apply to each action - body/value from Step 1
Here you will iterate through your list of items
 
4. (Inside apply to each) Append to Array action - use variable from Step 2 
Inside the Apply to Each, we will append to this array variable the items as JSON content the adaptive card can render later. For this I used the adaptive cards "FactSet" object and replaced the values with dynamic content.

Just make sure that your value string content is encapsulated in double quotes.

Below is the 'append to array' action content with my dynamic content as the values

       {
            "type": "FactSet",
            "facts": [
                {
                    "title": "Fact 1",
                    "value": "Dynamic Content 1"
                },
                {
                    "title": "Fact 2",
                    "value": "Dynamic Content 2"
                }
            ]
        },

I added a comma in red there because this would repeat. If its your last item, you will need to remove that - this could potentially be done with a condition - otherwise it will mess up your JSON and error out on the flow.
 
As another option, I added a simple textblock later on in the adaptive card so that the text block was always the last item and I could repeat the fact set as much as I wanted without messing up the JSON.

example below (we will see this in context in later steps):
        {
            "type": "TextBlock",
            "text": "Random Text - Hello!",
            "wrap": true
        }
 
5. (Outside of Apply to Each) Compose action - Compose your Array variable
Your Compose content should just be the output of the variable. The Compose's output should look something like this (using my simple example in earlier steps):

       {
            "type": "FactSet",
            "facts": [
                {
                    "title": "Fact 1",
                    "value": "Dynamic Content 1"
                },
                {
                    "title": "Fact 2",
                    "value": "Dynamic Content 2"
                }
            ]
        },
       {
            "type": "FactSet",
            "facts": [
                {
                    "title": "Fact 1",
                    "value": "Dynamic Content 3"
                },
                {
                    "title": "Fact 2",
                    "value": "Dynamic Content 4"
                }
            ]
        },

6. (optional) Compose action - You can compose your cards JSON here before you add it to a "Post Adaptive card" action to troubleshoot or debug
Effectively this example is a simple "one-way" card sent to a user or channel. You can get more complex and collect responses with 'input' adaptive card objects but this was personally a bit harder to put together for me - see my other post here: Solved: Re: How to Select value from Object using value fr... - Power Platform Community (microsoft....

Otherwise, at this point you're composing the card in its entirety and will look like something like this (your composed array variable output from Step 5 will go where the red bolded content goes: 

{
    "type": "AdaptiveCard",
    "body": [
        {
            "type": "TextBlock",
            "size": "Medium",
            "weight": "Bolder",
            "text": "Sample"
        },
       [Output of Compose from Step 5 goes here]
        {
            "type": "TextBlock",
            "text": "Random Text - Hello!",
            "wrap": true
        }
    ],
    "version": "1.3"
}
I recommend at this point grabbing this current Compose actions output and copying it into Designer | Adaptive Cards payload editor to make sure it looks right.

Here is a quick image of the card as designed so far:

virakones_0-1666985094366.png


Code:

 

 

{
    "type": "AdaptiveCard",
    "body": [
        {
            "type": "TextBlock",
            "size": "Medium",
            "weight": "Bolder",
            "text": "Sample"
        },
        {
            "type": "FactSet",
            "facts": [
                {
                    "title": "Fact 1",
                    "value": "Dynamic Content 1"
                },
                {
                    "title": "Fact 2",
                    "value": "Dynamic Content 2"
                }
            ]
        },
        {
            "type": "FactSet",
            "facts": [
                {
                    "title": "Fact 1",
                    "value": "Dynamic Content 3"
                },
                {
                    "title": "Fact 2",
                    "value": "Dynamic Content 4"
                }
            ]
        },
        {
            "type": "TextBlock",
            "text": "Random Text - Hello!",
            "wrap": true
        }
    ],
    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
    "version": "1.3"
}

 

 

 
7. Post Adaptive Card action - whatever type you need (channel, chat, etc.)
Now your JSON is ready and you can simply take the output from Step 6 and place it in the adaptive card field.


I hope this is helpful enough to get you started - this was something simple I put together last year and is working out now with inputs, edits, etc. and helped me on my path to create more customized adaptive cards. highly recommend hanging out on the Schema Explorer | Adaptive Cards to understand what you can add, what version Teams supports, how to add cards into Outlook, etc. It's pretty cool!

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages