cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Advocate V
Advocate V

AdaptiveCard shows up blank for some users

Hello everybody,

 

I have an interesting case here.

I have configured a SharePoint Site Design to trigger a flow upon applying the design.

The purpose of the flow is to send an AdaptiveCard to a user that should enter a new site title.

 

I was testing this AdaptiveCard on my Global admin account, which has a E1 license assigned. All works fine, the AdaptiveCard displays in the e-mail message.

 

Planning to roll out this feature, I changed the TO address in the sending email action within the flow to another user.

He now reports that the form is not showing up in Outlook desktop, neither in Outlook Web App.

 

When I change back the email address, all is working fine again.

I am wondering, did I miss something resulting in this behavior?

 

Thanks for all help provided!

 

This is the JSON composed through workflow, and inserted in the Send an email action body:

<html>
<head>
  <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  <script type="application/adaptivecard+json">
{
"type": "AdaptiveCard",
"body": [
{
"type": "Container",
"spacing": "None",
"style": "emphasis",
"items": [
{
"type": "ColumnSet",
"columns": [
{
"type": "Column",
"items": [
{
"type": "TextBlock",
"text": "Tender mutatieformulier"
}
],
"width": "stretch",
"padding": "None"
},
{
"type": "Column",
"items": [
{
"type": "Image",
"id": "4b3986aa-ca62-8df9-f4c9-5d9bc8585978",
"url": "%%% LOGO URL %%%%",
"horizontalAlignment": "Right",
"height": "12px"
}
],
"width": "auto",
"verticalContentAlignment": "Center",
"padding": "None"
}
],
"padding": "None"
}
],
"padding": "Default"
},
{
"type": "Container",
"items": [
{
"type": "TextBlock",
"size": "Large",
"weight": "Bolder",
"text": "Gelieve dit formulier volledig en juist in te vullen.",
"wrap": true
},
{
"type": "TextBlock",
"id": "93dbe92e-d972-3b01-97be-d27372d5f202",
"text": "Dit formulier gebruikt u om aan een Tender site in SharePoint een nieuwe omschrijving en een nieuw unieke kenmerk te geven. Het is essentieel dat u in dit formulier geen typfouten maakt.",
"wrap": true
},
{
"type": "FactSet",
"id": "93760e6e-6519-aac3-e1ef-42a055dd0286",
"facts": [
{
"title": "Betreft Tender:",
"value": "Value"
}
]
}
],
"padding": "Default",
"spacing": "None",
"separator": true
},
{
"type": "Container",
"items": [
{
"type": "TextBlock",
"weight": "Bolder",
"text": "1\\. Geef de nieuwe projectomschrijving op",
"wrap": true
},
{
"type": "Input.Text",
"id": "Projectomschrijving",
"placeholder": "Voorbeeld: 19032 Nieuwbouw",
"isRequired": true
},
{
"type": "TextBlock",
"weight": "Bolder",
"text": "2\\. Geef het projectnummer op",
"wrap": true,
"spacing": "Large"
},
{
"type": "Input.Text",
"id": "Projectnummer",
"placeholder": "Voorbeeld: 20207",
"isRequired": true
},
{
"type": "ActionSet",
"actions": [
{
"type": "Action.Http",
"title": "Indienen",
"method": "POST",
"url": "%%%%%FLOW URL%%%%%",
"body": "{\"Projectomschrijving\": \"{{Projectomschrijving.value}}\", \"Projectnummer\":\"{{Projectnummer.value}}\"}",
"isPrimary": true,
"style": "positive",
"headers": [
{
"name": "Content-Type",
"value": "application/json"
},
{
"name": "Authorization",
"value": ""
}
]
}
]
}
],
"padding": {
"top": "Small",
"bottom": "Default",
"left": "Default",
"right": "Default"
},
"spacing": "None"
}
],
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
"version": "1.0",
"padding": "None"
}
</script>
</head>
<body>
Dit bericht is verstuurd vanuit een systeem mailbox. Gelieve niet op dit bericht te reageren.
</body>
</html>
1 ACCEPTED SOLUTION

Accepted Solutions

So it appeared that if I would have taken more time to find the answer I would have found the right direction.

I am using the following designer to build up my JSON: https://amdesigner.azurewebsites.net/

 

I thought that I hade included the originator ID in my JSON, but apparently i mistakenly removed it.

That was causing this behavior. I had to include it back in the payload.

 

I found this article that exactly described my issue: https://powerusers.microsoft.com/t5/Building-Flows/Actionable-Message-Blank/td-p/476730

 

So I did install the Actionable Message Debugger and it pointed me to the missing Originator ID.

View solution in original post

4 REPLIES 4
Super User II
Super User II

hi @jvdlinden  are you refering teams  AdaptiveCard? 



Did I answer your question? Please consider to Mark
my post as a solution! to guide others :winking_face:

Proud to be a Flownaut!


If you want you can follow me at www.christianabata.com Quieres contenido en español? Síguenos en Power Automate LA

Hi @ChristianAbata sorry I am referring to an AdaptiveCard designed for Outlook.

So it appeared that if I would have taken more time to find the answer I would have found the right direction.

I am using the following designer to build up my JSON: https://amdesigner.azurewebsites.net/

 

I thought that I hade included the originator ID in my JSON, but apparently i mistakenly removed it.

That was causing this behavior. I had to include it back in the payload.

 

I found this article that exactly described my issue: https://powerusers.microsoft.com/t5/Building-Flows/Actionable-Message-Blank/td-p/476730

 

So I did install the Actionable Message Debugger and it pointed me to the missing Originator ID.

View solution in original post

Hi,

 

It looks like you have figured out your issue here. I wanted to add in a bit of additional information here if you would like to learn more about this. https://www.appliedis.com/newly-released-json-function-for-powerapps/

 

Regards,

 

Alex

 

-------

 

Community Support Team _ Alex Rezac
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Helpful resources

Announcements
Microsoft Ignite

Microsoft Ignite

Join digitally, March 2–4, 2021 to explore new tech that's ready to implement. Experience the keynote in mixed reality through AltspaceVR!

New Super Users

Meet the Power Automate Super Users!

Many congratulations to the Season 1 2021 Flownaut Crew!

New Badges

New Solution Badges!

Check out our new profile badges recognizing authored solutions!

MPA Community Blog

Power Automate Community Blog

Check out the community blog page where you can find valuable learning material from community and product team members!

Users online (68,455)