I am attempting to mimic what has been reported as a working flow.
I have created a copy and am getting the following error specific to the json 'compose' action.
There is a 'compose' action in the example flow with tthe following code -
json(outputs('Send_an_HTTP_request_to_SharePoint')?['body']['d']['ImageColumn'Name])
In my version of the flow PA is kicking back the following error when I use the above with my column name included -
Unable to process template language expressions in action 'Compose' inputs at line '0' and column '0':
'The template language expression 'json(outputs('Send_an_HTTP_request_to_SharePoint')?['body']['d']['CompanyLogo'])' cannot be evaluated because property 'CompanyLogo' doesn't exist, available properties are 'results'.
When I change the compose language to the following -
json(outputs('Send_an_HTTP_request_to_SharePoint')?['body']['d']['result')
I get the following error. (when I enter "results" PA defaults it to the singular 'result' on update, which is why it reads as it does).
Compose Error:
Unable to process template language expressions in action 'Compose' inputs at line '0' and column '0': 'The template language expression 'json(outputs('Send_an_HTTP_request_to_SharePoint')?['body']['d']['result'])' cannot be evaluated because property 'result' doesn't exist, available properties are 'results'.
Compose Detail:
Solved! Go to Solution.
You likely need to convert the image to base64 encoding. See example below where I have an image in my library that I use when sending an email. It will be the same process when adding to your PDF.
Get file content gets the actual content of the image.
Compose builds up the URL including the base64 part. The expression used here is:
<img src="data:image/jpeg;base64,@{outputs('Get_file_content')?['body']?['$content']}" alt="My Image" />
It then sends an email using the output from the Compose.
The final result of the email in this instance is:
Where you've written the word outputs, you need to put the actual field name in there that contains the image URL.
Hey @Phineas
The line is saying available properties are results, result with an s. You have just written result.
Write this expression:
json(outputs('Send_an_HTTP_request_to_SharePoint')?['body']['d']['results'])
By writing the s you won't get the error now.
I finally got it to take. Tried all morning and it kept dropping the 's'.
Now the error is -
Unable to process template language expressions in action 'Compose' inputs at line '0' and column '0': 'The template language function 'json' expects its parameter to be a string or an XML. The provided value is of type 'Array'.
Send an HTTP Details -
If the Compose is just trying to get the results, then you shouldn't have it within a json expression as it's already in JSON format. You can just use the following expression:
outputs('Send_an_HTTP_request_to_SharePoint')?['body']['d']['results']
Edited Reply No. 2:
Went round and round and got it back to the following.
It's cleaned up from the original, however the original problem still exists - the 'Logo' does not appear at the top of the PDF file as an image as desired.
SharePoint Library:
PDF Conversion:
In your Compose 2 you aren't setting up the image tag correctly. See format below:
//You would replace CompanyLogo.jpg with your actual logo, etc.
<img src="CompanyLogo.jpg" alt="Company Logo" width="500" height="600">
I installed your recommendation exactly as you have provided.
It only made image the size called out in the code.
The image still does not appear.
You don't have to add the width and height - that was just an example of what an image tag is constructed.
You will need to add your actual Company Logo URL as you had before. At the moment you've just got the text CompanyLogo.jpg.
I took this link directly from the file in the SP Library.
This was the result -
You likely need to convert the image to base64 encoding. See example below where I have an image in my library that I use when sending an email. It will be the same process when adding to your PDF.
Get file content gets the actual content of the image.
Compose builds up the URL including the base64 part. The expression used here is:
<img src="data:image/jpeg;base64,@{outputs('Get_file_content')?['body']?['$content']}" alt="My Image" />
It then sends an email using the output from the Compose.
The final result of the email in this instance is:
Thank you for the reply.
I tried to mimic what you did. I didn't get 'Outputs' as an option and had to manually enter all the information in the 'compose' action.
Still no image in PDF.
Where you've written the word outputs, you need to put the actual field name in there that contains the image URL.
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!
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
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.
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